
From nobody Mon Dec  1 00:10:37 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C43E1A1A8D; Mon,  1 Dec 2014 00:10:22 -0800 (PST)
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] autolearn=ham
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 iPUPHXcXzZkH; Mon,  1 Dec 2014 00:10:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 19DEA1A1B1E; Mon,  1 Dec 2014 00:10:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: DraftTracker Mail System <iesg-secretary@ietf.org>
To: iesg@ietf.org, gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141201081017.17091.54167.idtracker@ietfa.amsl.com>
Date: Mon, 01 Dec 2014 00:10:17 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/uFFL0LYyHw4g2y26hPe05zd7Sv8
Cc: iesg-secretary@ietf.org
Subject: [tsvwg] Last Call Expired: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 08:10:22 -0000

Please DO NOT reply to this email.

I-D: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

IETF Last Call has ended, and the state has been changed to
Waiting for Writeup.


From nobody Mon Dec  1 06:47:25 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E16A61A0174; Mon,  1 Dec 2014 06:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fJaBkgFRAQOe; Mon,  1 Dec 2014 06:47:17 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92CFA1A1BF6; Mon,  1 Dec 2014 06:47:15 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB1ElC8J009246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Dec 2014 09:47:14 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com sB1ElC8J009246
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1417445234; bh=uStIu0mFVsXd9ZSzSrXAwQlh23M=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=stv0xgJd/PTAXn99Yx+UoUrZTgK+4gJiQttDaKtANkJxxX5L8qRcNTDfJx49XuFdS ALDqJ3FGZUQpbZg82MU8ggSZQwe2SXfM6VtXSo2pKVdjRY8lYOppTWPJ38PsRuREjX W9pqkyntN8evZ0oaRDchXt4ortNI4yoajvC9wS0Q=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com sB1ElC8J009246
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd04.lss.emc.com (RSA Interceptor); Mon, 1 Dec 2014 09:46:20 -0500
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB1Ekvm9016759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Dec 2014 09:46:57 -0500
Received: from MXHUB205.corp.emc.com (10.253.68.31) by mxhub26.corp.emc.com (10.254.110.182) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 1 Dec 2014 09:46:56 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.125]) by MXHUB205.corp.emc.com ([fe80::2b:c770:c6f4:ee06%12]) with mapi id 14.03.0195.001; Mon, 1 Dec 2014 09:46:56 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Randell Jesup - where are you?
Thread-Index: AdANdaZx097bFkFoT8SszkjA7R8APw==
Importance: high
X-Priority: 1
Date: Mon, 1 Dec 2014 14:46:55 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493627FFC3@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/0lEq037J6iiBKVfyGRy7cdAQvDk
Subject: [tsvwg] Randell Jesup - where are you?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 14:47:20 -0000

Having seen no response from Randell, I'm now adding both the tsvwg and
rtcweb lists.

If anyone is in touch w/Randell, would you please "encourage" him to get
back to us (tsvwg chairs), so that we can move the SCTP DTLS draft forward.

Thanks,
--David

-----Original Message-----
From: Black, David [mailto:david.black@emc.com]=20
Sent: Monday, November 17, 2014 5:38 PM
To: randell-ietf@jesup.org
Cc: tsvwg-chairs@tools.ietf.org; rtcweb-chairs@tools.ietf.org
Subject: FW: Author IPR info: draft-ietf-tsvwg-sctp-dtls-encaps-06
Importance: High

Randell,

Your response to the email below is the only thing currently delaying
the RFC Publication request for the SCTP DTLS draft - please respond
to the message below at your earliest convenience (and we do need you
to respond directly).

I've cc:'d the RTCWEB WG chairs in the hope that they can help move
this along (Ted - this is what we talked about briefly on Friday morning).

Thanks,
--David

-----Original Message-----
From: gorry@erg.abdn.ac.uk [mailto:gorry@erg.abdn.ac.uk]=20
Sent: Wednesday, November 12, 2014 5:30 AM
To: Randell Jesup
Cc: tsvwg-chairs@tools.ietf.org
Subject: Author IPR info: draft-ietf-tsvwg-sctp-dtls-encaps-06


Randell,

I don't recall seeing a reply for IPR information about the above draft
(if you sent, I'm sorry - but could you send me an email again?)

Can you confirm that any and all appropriate IPR disclosures required for
full conformance with the provisions of BCP 78 and BCP 79 have already
been filed. If not, explain why?

As an incentive - at this moment you are the only thing stopping me
submitting this to our AD for publication!

Gorry

https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-06


From nobody Mon Dec  1 09:39:29 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A551A8721 for <tsvwg@ietfa.amsl.com>; Mon,  1 Dec 2014 09:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 T0hbEJ65JReQ for <tsvwg@ietfa.amsl.com>; Mon,  1 Dec 2014 09:39:25 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFABD1A8706 for <tsvwg@ietf.org>; Mon,  1 Dec 2014 09:39:24 -0800 (PST)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB1HdNUm029467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 12:39:23 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sB1HdNUm029467
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1417455563; bh=ui4036N/XaJeuHetQ1P7LVMCxUM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=MZx4w+EkEYXgxjY1mn/O+3OhiQ15vxox1l3jii2AbmlH8pYenkg74A+DMfUn/j8i7 fXH7llJ69x19Qhfl8avQsP/1CHw7W3bWHG9J9UJlcmQcXiB0z5UqiJAtoFKjB8utBY qr1QyfMaO84PSqHbp9NSiNcc2l+iJL9+28xvYsWM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sB1HdNUm029467
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd56.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 12:38:34 -0500
Received: from mxhub39.corp.emc.com (mxhub39.corp.emc.com [128.222.70.106]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB1HdAC8023430 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 12:39:10 -0500
Received: from MXHUB204.corp.emc.com (10.253.68.30) by mxhub39.corp.emc.com (128.222.70.106) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 1 Dec 2014 12:39:09 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.125]) by MXHUB204.corp.emc.com ([fe80::ce7:65a1:5e89:81ab%12]) with mapi id 14.03.0195.001; Mon, 1 Dec 2014 12:39:09 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Final Honolulu tsvwg minutes
Thread-Index: AdANjbVYHEom9dH2RoKGWw8wGRW50g==
Date: Mon, 1 Dec 2014 17:39:08 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936280729@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/lJFYHMteMksrNB6QSZbqjd2Io3g
Subject: [tsvwg] Final Honolulu tsvwg minutes
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 17:39:27 -0000

Uploaded: http://www.ietf.org/proceedings/91/minutes/minutes-91-tsvwg

FYI,
--David


From nobody Mon Dec  1 16:34:01 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E82D31A1ABC for <tsvwg@ietfa.amsl.com>; Mon,  1 Dec 2014 16:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 L7K6ZZ8tOUqp for <tsvwg@ietfa.amsl.com>; Mon,  1 Dec 2014 16:33:55 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 991251A7032 for <tsvwg@ietf.org>; Mon,  1 Dec 2014 16:33:55 -0800 (PST)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB20Xr8x025209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 19:33:53 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sB20Xr8x025209
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1417480433; bh=8m8EgS6tCI6B/dgdAzCvPiKM/hs=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=VgOkFBiNejzynGvgKQ6jhiDPQhpuBCIx3EHaf+d6ZDrJ5Q2ZiJyZ8wylK1z+k0LuE DR8E+FZKY4PKd83PwxnCRFwNMCysDh7tclfu2mJOx9CbD7NcE9iF4OowD0YmTl3Yrn zEKz0n94sJ4rOWcdvT6Mfs8KdmQXM1Riv/q7NQnA=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sB20Xr8x025209
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd03.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 19:33:09 -0500
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sB20XcrE014895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <tsvwg@ietf.org>; Mon, 1 Dec 2014 19:33:39 -0500
Received: from MXHUB205.corp.emc.com (10.253.68.31) by mxhub02.corp.emc.com (10.254.141.104) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 1 Dec 2014 19:33:38 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.125]) by MXHUB205.corp.emc.com ([fe80::2b:c770:c6f4:ee06%12]) with mapi id 14.03.0195.001; Mon, 1 Dec 2014 19:33:38 -0500
From: "Black, David" <david.black@emc.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Adoption of diffserv-intercon and rfc5405bis drafts
Thread-Index: AdANx5qsJSxiLPMPQ+eThiY2QlVRxQ==
Date: Tue, 2 Dec 2014 00:33:37 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493628106A@MX104CL02.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.72]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/S1_78aMDA5RUD8CH6MVEQIvq1Yw
Subject: [tsvwg] Adoption of diffserv-intercon and rfc5405bis drafts
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 00:33:58 -0000

Having seen no further comment on this matter:

> 2) The sense of the room in Honolulu was to adopt the following two
> 	drafts as WG drafts:
>=20
>       DiffServ interconnection classes and practice
> 	draft-geib-tsvwg-diffserv-intercon
> http://datatracker.ietf.org/doc/draft-geib-tsvwg-diffserv-intercon/
>=20
>       UDP Usage Guidelines
>       draft-eggert-tsvwg-rfc5405bis
> http://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/
>=20
>       Absent objection on the list, these drafts will be adopted.
>       Please comment by November 30.

These drafts have been adopted by the tsvwg WG.  Would the authors
please submit -00 draft-ietf-tsvwg- versions with no change of text
from the latest individual submission version?

Thanks,
--David


> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Black, David
> Sent: Friday, November 14, 2014 10:48 PM
> To: tsvwg@ietf.org
> Cc: aqm@ietf.org
> Subject: [tsvwg] Draft Honolulu minutes posted
>=20
> ... before I get on the plane out of here!
>=20
> http://www.ietf.org/proceedings/91/minutes/minutes-91-tsvwg
>=20
> Many thanks to Aaron Falk and Joel Halpern for taking notes, as
> there were lively discussions in both sessions that were not easy
> to follow.  They captured everything important.
>=20
> Here are some important items that people should know about:
>=20
> 1) There are a number of expired WG drafts that need author attention:
> 	ECN Encapsulation Guidelines
> 	NAT Behavioral Requirements Updates
> 	RSVP Multiple Instance Object
> 	SCTP NAT Support
>=20
> 2) The sense of the room in Honolulu was to adopt the following two
> 	drafts as WG drafts:
>=20
>       DiffServ interconnection classes and practice
> 	draft-geib-tsvwg-diffserv-intercon
> http://datatracker.ietf.org/doc/draft-geib-tsvwg-diffserv-intercon/
>=20
>       UDP Usage Guidelines
>       draft-eggert-tsvwg-rfc5405bis
> http://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/
>=20
>       Absent objection on the list, these drafts will be adopted.
>       Please comment by November 30.
>=20
> 3) The meeting determined that there is no WG rough consensus
>       for requiring use of the full UDP checksum for GRE-in-UDP
>       with IPv6.  The design team will continue work on when
>       zero checksum is acceptable (as well as congestion
>       considerations).
>=20
> 4) See the minutes for the lengthy and interesting discussion of the
>       tunnel congestion feedback draft.  There is one important issue
> 	that needs to be followed up across the TSVWG and AQM WGs (aqm
>       list cc:'d for this reason):
>=20
>       OPEN ISSUE *1: Should ECN indications (CE) be treated as equivalent
>       to drops?  This also came  up in AQM.  This is primarily about
>       endpoint (or tunnel egress) reaction to CE.
>=20
> Enjoy,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From nobody Tue Dec  2 12:57:57 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087EF1A7013; Tue,  2 Dec 2014 12:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 z9_uWOrKIq1b; Tue,  2 Dec 2014 12:57:49 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A741A1DE1; Tue,  2 Dec 2014 12:57:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2KvmSG009944; Tue, 2 Dec 2014 12:57:48 -0800
Received: from XCH-PHX-211.sw.nos.boeing.com (xch-phx-211.sw.nos.boeing.com [130.247.25.140]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2KvfcK009441 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 12:57:42 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-211.sw.nos.boeing.com ([169.254.11.133]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 12:57:41 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvA==
Date: Tue, 2 Dec 2014 20:57:40 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/cMdT15OT0EeFKVu0zmRhmgfgfoE
Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 20:57:51 -0000

Hello,

I am replaying a message below that was originally posted on the routing-di=
scussion
list yesterday. Follow-up discussion was then posted in two additional mess=
ages. The
messages are here:

http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.ht=
ml
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.ht=
ml
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.ht=
ml

I am cross-posting to transport area and int area now, because there seems =
to be
an overlap of interests with respect to UDP tunneling that may transcend tr=
aditional
area boundaries. Original message appears below; please post comments to th=
e lists.

Thanks - Fred
fred.l.templin@boeing.com

---

Hello,

I am working on a spec for generic tunneling of any protocol over UDP, incl=
uding
MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:

  - an encapsulation format
  - a fragmentation and reassembly capability for MTU mitigation
  - a virtual link model
  - a control messaging mechanism
  - a routing and addressing system based on BGP

https://datatracker.ietf.org/doc/draft-templin-aerolink/

I understand that there have been discussions regarding protocol-specific
GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
as a protocol-independent way of accommodating UDP encapsulations. I
also believe the routing system and other aspects of AERO should be of
interest to the routing area.

This work is derived from an earlier experimental RFC (RFC6706) which was
originally briefed to the routing area several years ago and published as a=
n
AD-sponsored Individual Submission RFC. The current document can be
considered as a second edition of AERO, and the goal is to advance it to
standards track. Please send any comments or questions to the list.

Thanks - Fred
fred.l.templin@boeing.com =20


From nobody Tue Dec  2 14:26:56 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28FE61A1AAF; Tue,  2 Dec 2014 14:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 oBbEpsjODpUt; Tue,  2 Dec 2014 14:26:45 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.112]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770291A0030; Tue,  2 Dec 2014 14:26:44 -0800 (PST)
Received: from [193.109.255.147] by server-8.bemta-14.messagelabs.com id 4E/07-03148-2AC3E745; Tue, 02 Dec 2014 22:26:42 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1417559201!14232901!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.12.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17631 invoked from network); 2 Dec 2014 22:26:42 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 2 Dec 2014 22:26:42 -0000
Received: from EXHY011V.surrey.ac.uk (131.227.200.103) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Tue, 2 Dec 2014 22:26:41 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.200.4) by EXHY011v.surrey.ac.uk (131.227.200.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 2 Dec 2014 22:26:41 +0000
Received: from DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) by DB4PR06MB174.eurprd06.prod.outlook.com (10.242.155.148) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 22:26:41 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 22:26:39 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0026.003; Tue, 2 Dec 2014 22:26:39 +0000
From: <l.wood@surrey.ac.uk>
To: <Fred.L.Templin@boeing.com>, <tsvwg@ietf.org>, <int-area@ietf.org>, <routing-discussion@ietf.org>
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIUlvuyiTrTg+MXp53XC95kQAB0fjf
Date: Tue, 2 Dec 2014 22:26:39 +0000
Message-ID: <1417559198240.10209@surrey.ac.uk>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [122.200.59.254]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;UriScan:;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-forefront-prvs: 0413C9F1ED
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(585484001)(189002)(377454003)(19580405001)(19580395003)(117636001)(2656002)(15975445006)(74482002)(46102003)(101416001)(97736003)(2501002)(36756003)(99396003)(21056001)(1720100001)(15198665003)(62966003)(122556002)(4396001)(120916001)(87936001)(77156002)(40100003)(68736005)(20776003)(2201001)(64706001)(92566001)(66066001)(92726001)(15395725005)(15202345003)(86362001)(95666004)(105586002)(106356001)(107046002)(107886001)(31966008)(76176999)(77096005)(50986999)(54356999)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB458; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB458.eurprd06.prod.outlook.com
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB174;
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY011v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY011v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Zuf9n05yFOg6Y8T5pFINe4oBA84
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 22:26:48 -0000

Fred,=0A=
=0A=
I see Adrian mentioned checksums in his reply to you. To elaborate on his p=
oint:=0A=
=0A=
http://datatracker.ietf.org/doc/draft-templin-aerolink/=0A=
says:=0A=
=0A=
   The AERO interface=0A=
   also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])=0A=
   unless an integrity check is required (see: Section 3.12.2).=0A=
=0A=
This misses the more subtle implications of zero checksums. As RFC6936 says=
:=0A=
   The current recommendation=0A=
   is to use or fall back to using UDP with full checksum coverage.=0A=
=0A=
RFC6935 is written from the perspective of tunnelled traffic that can have =
its own checks, rather than from the larger perspective of what is good for=
 the network; the zero checksum was inconvenient for tunnellers, hence RFC6=
935. (While RFC6936 is rather academic and nuanced in its tone, as it steps=
 through the necessary safeguards that that use of zero checksums requires =
of everything else; sometimes 'don't do that, stupid!' is the clearer and s=
impler approach to both writing and engineering.)=0A=
=0A=
A zero UDP checksum means:=0A=
=0A=
- in IPv4, potential delivery to any port on the destination device if ther=
e is UDP header corruption. (the IPv4 header checksum can prevent host misd=
elivery). This is port pollution.=0A=
=0A=
- in IPv6, potential delivery to anywhere if there is IP/UDP header corrupt=
ion (as there is no IP header checksum, and using a zero UDP sum turns off =
the endhost pseudoheader check - and tunnels often terminate on routers tha=
t forward packets...). This is network pollution.=0A=
=0A=
So, use a zero UDP checksum, and the IPv6 traffic you generate can be poten=
tially injected anywhere to affect anything, modulo all the careful nuance =
in RFC6936 to start guarding against this - guards required by everything e=
lse. But your tunnel traffic can have its own checks and its own repeat/rep=
lay, so you're alright.=0A=
=0A=
(UDP-Lite provides a minimal interface to build on with necessary endhost p=
seudo-header check and low computation cost for application designers; sham=
e it's not more prevalent.)=0A=
=0A=
Analogies with nice clean factories pumping into dirty rivers fit nicely he=
re. It's a tragedy that people downstream were relying on the river water, =
but it's clearly not the factory designer's fault. As if. Those people just=
 didn't implement the safeguards in the small print. And environmental prot=
ection wasn't a design goal. Why care about the commons?=0A=
=0A=
My take here is that IPv6 was not well-designed in this regard. An IP heade=
r checksum across non-mutable fields, excluding QoS/TTL etc., that did not =
need to be recomputed, would have been preferable. A mandatory endhost pseu=
doheader check would have been preferable. Expecting protocol designers to =
do the right thing above IP and do the necessary pseudo-header check has be=
en repeatedly demonstrated to presume too much knowledge in those that foll=
ow. Hardly the only IPv6 mistake, but not one we should be compounding.=0A=
=0A=
Please fix AERO, and follow RFC6936's recommendation.=0A=
=0A=
Lloyd Wood=0A=
http://about.me/lloydwood=0A=
=0A=
you'll notice I'm not also asking you to fix the bundle protocol. Lost caus=
e.=0A=
________________________________________=0A=
From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L.T=
emplin@boeing.com>=0A=
Sent: Wednesday, 3 December 2014 7:57 AM=0A=
To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org=0A=
Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO=0A=
=0A=
Hello,=0A=
=0A=
I am replaying a message below that was originally posted on the routing-di=
scussion=0A=
list yesterday. Follow-up discussion was then posted in two additional mess=
ages. The=0A=
messages are here:=0A=
=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.ht=
ml=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.ht=
ml=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.ht=
ml=0A=
=0A=
I am cross-posting to transport area and int area now, because there seems =
to be=0A=
an overlap of interests with respect to UDP tunneling that may transcend tr=
aditional=0A=
area boundaries. Original message appears below; please post comments to th=
e lists.=0A=
=0A=
Thanks - Fred=0A=
fred.l.templin@boeing.com=0A=
=0A=
---=0A=
=0A=
Hello,=0A=
=0A=
I am working on a spec for generic tunneling of any protocol over UDP, incl=
uding=0A=
MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:=0A=
=0A=
  - an encapsulation format=0A=
  - a fragmentation and reassembly capability for MTU mitigation=0A=
  - a virtual link model=0A=
  - a control messaging mechanism=0A=
  - a routing and addressing system based on BGP=0A=
=0A=
https://datatracker.ietf.org/doc/draft-templin-aerolink/=0A=
=0A=
I understand that there have been discussions regarding protocol-specific=
=0A=
GRE and MPLS encapsulations within UDP, but I would like to offer up AERO=
=0A=
as a protocol-independent way of accommodating UDP encapsulations. I=0A=
also believe the routing system and other aspects of AERO should be of=0A=
interest to the routing area.=0A=
=0A=
This work is derived from an earlier experimental RFC (RFC6706) which was=
=0A=
originally briefed to the routing area several years ago and published as a=
n=0A=
AD-sponsored Individual Submission RFC. The current document can be=0A=
considered as a second edition of AERO, and the goal is to advance it to=0A=
standards track. Please send any comments or questions to the list.=0A=
=0A=
Thanks - Fred=0A=
fred.l.templin@boeing.com=0A=
=0A=


From nobody Tue Dec  2 14:40:08 2014
Return-Path: <therbert@google.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75CA1A1AD3 for <tsvwg@ietfa.amsl.com>; Tue,  2 Dec 2014 14:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 XlKFcm0IeW5q for <tsvwg@ietfa.amsl.com>; Tue,  2 Dec 2014 14:40:04 -0800 (PST)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C5F31A1AAF for <tsvwg@ietf.org>; Tue,  2 Dec 2014 14:40:04 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id rl12so12200585iec.5 for <tsvwg@ietf.org>; Tue, 02 Dec 2014 14:40:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WhTVd3EkwIcNR3Q2aYBZlSlgJl/dlxPsDdiSvy0Wjiw=; b=ersED/3R9XLT8uPuWuE+hAHQWLtyEZjesNHbMvexBC71wKwaeve96OdSogMxtqVtZ8 bCw0VdNiWigerd0p/NwXTLswoFjTw/aRSixtfug6gTvt+s9pTUwtg7agVm0V1NieionU C2gaDccLLZRnFm3W67B3B0B89Ttg3f750e+N9uaxl0/d96SVlDEQCxQfjvtx3YXfpKXc RR/aNDSw8cs3iSlGhIDWqbxcLFgNKRwk0DYIUsJuoE8fzL4bip4NiLMJwfkMASxqPCkd LE3pk2y395O52I/kFVStyui9ZRjGLGJdZrdSlkdF87HS96AZ3qzLP9/DfdOGwbqcDz/8 WIFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WhTVd3EkwIcNR3Q2aYBZlSlgJl/dlxPsDdiSvy0Wjiw=; b=k7Yh+0EAtJXNHQx3gdbQpnh1Kc/ue5MxXV4BzOE30bT7Be8p7teKLyqRDpimbe4YrO Gdxb+th+2IcaLXBEK8l25UvSFGdkinqF/5diM+RnDcT+rjg7CLR7+kGT4PnsyASDQrJU fb31eFiQ5mybPxo3gzTJrI+DGwHsRq5aAav2GDrvXG2EBRnfcJ1h7Y+yJflTeZCxuvEZ rMeWMiYwvdp+B9NSVijbXZ7f9Na+pYAIjRYRXqWn6MJwHdG6RQfnZ32gXrZUChcL4MHd C2fexGpitv9zmXCKRLWvvGZ/OhnRcN8rOTB22bzEh3gOlEq1vfbIPKCiRd4SDhnLm96t XXIw==
X-Gm-Message-State: ALoCoQnsyHiWCl7CvhyF7AIeRvZiO1vgRFQFZhuhYoL70dZt5+hfBnREyydk2f+173BaFwk6ss27
MIME-Version: 1.0
X-Received: by 10.42.255.72 with SMTP id nh8mr4650489icb.1.1417560003262; Tue, 02 Dec 2014 14:40:03 -0800 (PST)
Received: by 10.64.98.167 with HTTP; Tue, 2 Dec 2014 14:40:03 -0800 (PST)
In-Reply-To: <1417559198240.10209@surrey.ac.uk>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk>
Date: Tue, 2 Dec 2014 14:40:03 -0800
Message-ID: <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: l.wood@surrey.ac.uk
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/EPuuxj02qvpsGx_VeW4-Zy9-8yE
Cc: int-area@ietf.org, tsvwg@ietf.org, routing-discussion@ietf.org
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 22:40:07 -0000

On Tue, Dec 2, 2014 at 2:26 PM,  <l.wood@surrey.ac.uk> wrote:
> Fred,
>
> I see Adrian mentioned checksums in his reply to you. To elaborate on his=
 point:
>
> http://datatracker.ietf.org/doc/draft-templin-aerolink/
> says:
>
>    The AERO interface
>    also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])
>    unless an integrity check is required (see: Section 3.12.2).
>
> This misses the more subtle implications of zero checksums. As RFC6936 sa=
ys:
>    The current recommendation
>    is to use or fall back to using UDP with full checksum coverage.
>
> RFC6935 is written from the perspective of tunnelled traffic that can hav=
e its own checks, rather than from the larger perspective of what is good f=
or the network; the zero checksum was inconvenient for tunnellers, hence RF=
C6935. (While RFC6936 is rather academic and nuanced in its tone, as it ste=
ps through the necessary safeguards that that use of zero checksums require=
s of everything else; sometimes 'don't do that, stupid!' is the clearer and=
 simpler approach to both writing and engineering.)
>
> A zero UDP checksum means:
>
> - in IPv4, potential delivery to any port on the destination device if th=
ere is UDP header corruption. (the IPv4 header checksum can prevent host mi=
sdelivery). This is port pollution.
>
> - in IPv6, potential delivery to anywhere if there is IP/UDP header corru=
ption (as there is no IP header checksum, and using a zero UDP sum turns of=
f the endhost pseudoheader check - and tunnels often terminate on routers t=
hat forward packets...). This is network pollution.
>
> So, use a zero UDP checksum, and the IPv6 traffic you generate can be pot=
entially injected anywhere to affect anything, modulo all the careful nuanc=
e in RFC6936 to start guarding against this - guards required by everything=
 else. But your tunnel traffic can have its own checks and its own repeat/r=
eplay, so you're alright.
>
> (UDP-Lite provides a minimal interface to build on with necessary endhost=
 pseudo-header check and low computation cost for application designers; sh=
ame it's not more prevalent.)
>
> Analogies with nice clean factories pumping into dirty rivers fit nicely =
here. It's a tragedy that people downstream were relying on the river water=
, but it's clearly not the factory designer's fault. As if. Those people ju=
st didn't implement the safeguards in the small print. And environmental pr=
otection wasn't a design goal. Why care about the commons?
>
> My take here is that IPv6 was not well-designed in this regard. An IP hea=
der checksum across non-mutable fields, excluding QoS/TTL etc., that did no=
t need to be recomputed, would have been preferable. A mandatory endhost ps=
eudoheader check would have been preferable. Expecting protocol designers t=
o do the right thing above IP and do the necessary pseudo-header check has =
been repeatedly demonstrated to presume too much knowledge in those that fo=
llow. Hardly the only IPv6 mistake, but not one we should be compounding.
>
> Please fix AERO, and follow RFC6936's recommendation.
>
Another alternative might be to include a checksum in the
encapsulation header that includes a pseudo header covering ports and
addresses. This is what we intend to do in Generic UDP Encapsulation
(draft-herbert-guecsum-00).

> Lloyd Wood
> http://about.me/lloydwood
>
> you'll notice I'm not also asking you to fix the bundle protocol. Lost ca=
use.
> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L=
.Templin@boeing.com>
> Sent: Wednesday, 3 December 2014 7:57 AM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO
>
> Hello,
>
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
> ---
>
> Hello,
>
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>


From nobody Tue Dec  2 15:11:17 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 304951A1A90; Tue,  2 Dec 2014 15:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 pmQe7QcyqMiX; Tue,  2 Dec 2014 15:10:51 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1BB31A1A6B; Tue,  2 Dec 2014 15:10:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NAn75025685; Tue, 2 Dec 2014 17:10:49 -0600
Received: from XCH-PHX-113.sw.nos.boeing.com (xch-phx-113.sw.nos.boeing.com [130.247.25.136]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NAk6U025655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 17:10:47 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-113.sw.nos.boeing.com ([169.254.13.175]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:10:45 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvAAUSOmAAA9L6SA=
Date: Tue, 2 Dec 2014 23:10:45 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7DE4@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk>
In-Reply-To: <1417559198240.10209@surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7vy672wPSgziwgD5F3Q8glWw4AI
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:11:03 -0000

Hi Llloyd,

Thanks for the excellent analysis. I have had my head down on other aspects=
 of the
spec and not following the UDP checksum discussions. I will fix it.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]
> Sent: Tuesday, December 02, 2014 2:27 PM
> To: Templin, Fred L; tsvwg@ietf.org; int-area@ietf.org; routing-discussio=
n@ietf.org
> Subject: Re: Multiprotocol tunneling over UDP using AERO
>=20
> Fred,
>=20
> I see Adrian mentioned checksums in his reply to you. To elaborate on his=
 point:
>=20
> http://datatracker.ietf.org/doc/draft-templin-aerolink/
> says:
>=20
>    The AERO interface
>    also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])
>    unless an integrity check is required (see: Section 3.12.2).
>=20
> This misses the more subtle implications of zero checksums. As RFC6936 sa=
ys:
>    The current recommendation
>    is to use or fall back to using UDP with full checksum coverage.
>=20
> RFC6935 is written from the perspective of tunnelled traffic that can hav=
e its own checks, rather than from the larger perspective of
> what is good for the network; the zero checksum was inconvenient for tunn=
ellers, hence RFC6935. (While RFC6936 is rather academic
> and nuanced in its tone, as it steps through the necessary safeguards tha=
t that use of zero checksums requires of everything else;
> sometimes 'don't do that, stupid!' is the clearer and simpler approach to=
 both writing and engineering.)
>=20
> A zero UDP checksum means:
>=20
> - in IPv4, potential delivery to any port on the destination device if th=
ere is UDP header corruption. (the IPv4 header checksum can
> prevent host misdelivery). This is port pollution.
>=20
> - in IPv6, potential delivery to anywhere if there is IP/UDP header corru=
ption (as there is no IP header checksum, and using a zero UDP
> sum turns off the endhost pseudoheader check - and tunnels often terminat=
e on routers that forward packets...). This is network
> pollution.
>=20
> So, use a zero UDP checksum, and the IPv6 traffic you generate can be pot=
entially injected anywhere to affect anything, modulo all
> the careful nuance in RFC6936 to start guarding against this - guards req=
uired by everything else. But your tunnel traffic can have its
> own checks and its own repeat/replay, so you're alright.
>=20
> (UDP-Lite provides a minimal interface to build on with necessary endhost=
 pseudo-header check and low computation cost for
> application designers; shame it's not more prevalent.)
>=20
> Analogies with nice clean factories pumping into dirty rivers fit nicely =
here. It's a tragedy that people downstream were relying on the
> river water, but it's clearly not the factory designer's fault. As if. Th=
ose people just didn't implement the safeguards in the small print.
> And environmental protection wasn't a design goal. Why care about the com=
mons?
>=20
> My take here is that IPv6 was not well-designed in this regard. An IP hea=
der checksum across non-mutable fields, excluding QoS/TTL
> etc., that did not need to be recomputed, would have been preferable. A m=
andatory endhost pseudoheader check would have been
> preferable. Expecting protocol designers to do the right thing above IP a=
nd do the necessary pseudo-header check has been
> repeatedly demonstrated to presume too much knowledge in those that follo=
w. Hardly the only IPv6 mistake, but not one we should
> be compounding.
>=20
> Please fix AERO, and follow RFC6936's recommendation.
>=20
> Lloyd Wood
> http://about.me/lloydwood
>=20
> you'll notice I'm not also asking you to fix the bundle protocol. Lost ca=
use.
> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L=
.Templin@boeing.com>
> Sent: Wednesday, 3 December 2014 7:57 AM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO
>=20
> Hello,
>=20
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>=20
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>=20
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> ---
>=20
> Hello,
>=20
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>=20
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>=20
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>=20
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>=20
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com


From nobody Tue Dec  2 15:18:12 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E3F1A6F0A; Tue,  2 Dec 2014 15:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UoFWySaG6SP2; Tue,  2 Dec 2014 15:18:06 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C9D41A1BCA; Tue,  2 Dec 2014 15:18:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NI58R006778; Tue, 2 Dec 2014 15:18:05 -0800
Received: from XCH-PHX-410.sw.nos.boeing.com (xch-phx-410.sw.nos.boeing.com [10.57.37.41]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NHwNd006582 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 15:17:58 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-410.sw.nos.boeing.com ([169.254.10.179]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:17:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tom Herbert <therbert@google.com>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Thread-Topic: [tsvwg] Multiprotocol tunneling over UDP using AERO
Thread-Index: AQHQDoDvIrLJzf+uZkSV+8i05eS+EJx87W7Q
Date: Tue, 2 Dec 2014 23:17:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7E08@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk> <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
In-Reply-To: <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/5r8KZqfZeF-23D5m99XWPIlZIyM
Cc: "int-area@ietf.org" <int-area@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:18:08 -0000

SGkgVG9tLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFRvbSBIZXJi
ZXJ0IFttYWlsdG86dGhlcmJlcnRAZ29vZ2xlLmNvbV0NCj4gU2VudDogVHVlc2RheSwgRGVjZW1i
ZXIgMDIsIDIwMTQgMjo0MCBQTQ0KPiBUbzogbC53b29kQHN1cnJleS5hYy51aw0KPiBDYzogVGVt
cGxpbiwgRnJlZCBMOyB0c3Z3Z0BpZXRmLm9yZzsgaW50LWFyZWFAaWV0Zi5vcmc7IHJvdXRpbmct
ZGlzY3Vzc2lvbkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3RzdndnXSBNdWx0aXByb3RvY29s
IHR1bm5lbGluZyBvdmVyIFVEUCB1c2luZyBBRVJPDQo+IA0KPiBPbiBUdWUsIERlYyAyLCAyMDE0
IGF0IDI6MjYgUE0sICA8bC53b29kQHN1cnJleS5hYy51az4gd3JvdGU6DQo+ID4gRnJlZCwNCj4g
Pg0KPiA+IEkgc2VlIEFkcmlhbiBtZW50aW9uZWQgY2hlY2tzdW1zIGluIGhpcyByZXBseSB0byB5
b3UuIFRvIGVsYWJvcmF0ZSBvbiBoaXMgcG9pbnQ6DQo+ID4NCj4gPiBodHRwOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXRlbXBsaW4tYWVyb2xpbmsvDQo+ID4gc2F5czoNCj4gPg0K
PiA+ICAgIFRoZSBBRVJPIGludGVyZmFjZQ0KPiA+ICAgIGFsc28gc2V0cyB0aGUgVURQIGNoZWNr
c3VtIGZpZWxkIHRvIHplcm8gKHNlZTogW1JGQzY5MzVdW1JGQzY5MzZdKQ0KPiA+ICAgIHVubGVz
cyBhbiBpbnRlZ3JpdHkgY2hlY2sgaXMgcmVxdWlyZWQgKHNlZTogU2VjdGlvbiAzLjEyLjIpLg0K
PiA+DQo+ID4gVGhpcyBtaXNzZXMgdGhlIG1vcmUgc3VidGxlIGltcGxpY2F0aW9ucyBvZiB6ZXJv
IGNoZWNrc3Vtcy4gQXMgUkZDNjkzNiBzYXlzOg0KPiA+ICAgIFRoZSBjdXJyZW50IHJlY29tbWVu
ZGF0aW9uDQo+ID4gICAgaXMgdG8gdXNlIG9yIGZhbGwgYmFjayB0byB1c2luZyBVRFAgd2l0aCBm
dWxsIGNoZWNrc3VtIGNvdmVyYWdlLg0KPiA+DQo+ID4gUkZDNjkzNSBpcyB3cml0dGVuIGZyb20g
dGhlIHBlcnNwZWN0aXZlIG9mIHR1bm5lbGxlZCB0cmFmZmljIHRoYXQgY2FuIGhhdmUgaXRzIG93
biBjaGVja3MsIHJhdGhlciB0aGFuIGZyb20gdGhlIGxhcmdlciBwZXJzcGVjdGl2ZSBvZg0KPiB3
aGF0IGlzIGdvb2QgZm9yIHRoZSBuZXR3b3JrOyB0aGUgemVybyBjaGVja3N1bSB3YXMgaW5jb252
ZW5pZW50IGZvciB0dW5uZWxsZXJzLCBoZW5jZSBSRkM2OTM1LiAoV2hpbGUgUkZDNjkzNiBpcyBy
YXRoZXIgYWNhZGVtaWMNCj4gYW5kIG51YW5jZWQgaW4gaXRzIHRvbmUsIGFzIGl0IHN0ZXBzIHRo
cm91Z2ggdGhlIG5lY2Vzc2FyeSBzYWZlZ3VhcmRzIHRoYXQgdGhhdCB1c2Ugb2YgemVybyBjaGVj
a3N1bXMgcmVxdWlyZXMgb2YgZXZlcnl0aGluZyBlbHNlOw0KPiBzb21ldGltZXMgJ2Rvbid0IGRv
IHRoYXQsIHN0dXBpZCEnIGlzIHRoZSBjbGVhcmVyIGFuZCBzaW1wbGVyIGFwcHJvYWNoIHRvIGJv
dGggd3JpdGluZyBhbmQgZW5naW5lZXJpbmcuKQ0KPiA+DQo+ID4gQSB6ZXJvIFVEUCBjaGVja3N1
bSBtZWFuczoNCj4gPg0KPiA+IC0gaW4gSVB2NCwgcG90ZW50aWFsIGRlbGl2ZXJ5IHRvIGFueSBw
b3J0IG9uIHRoZSBkZXN0aW5hdGlvbiBkZXZpY2UgaWYgdGhlcmUgaXMgVURQIGhlYWRlciBjb3Jy
dXB0aW9uLiAodGhlIElQdjQgaGVhZGVyIGNoZWNrc3VtIGNhbg0KPiBwcmV2ZW50IGhvc3QgbWlz
ZGVsaXZlcnkpLiBUaGlzIGlzIHBvcnQgcG9sbHV0aW9uLg0KPiA+DQo+ID4gLSBpbiBJUHY2LCBw
b3RlbnRpYWwgZGVsaXZlcnkgdG8gYW55d2hlcmUgaWYgdGhlcmUgaXMgSVAvVURQIGhlYWRlciBj
b3JydXB0aW9uIChhcyB0aGVyZSBpcyBubyBJUCBoZWFkZXIgY2hlY2tzdW0sIGFuZCB1c2luZyBh
IHplcm8NCj4gVURQIHN1bSB0dXJucyBvZmYgdGhlIGVuZGhvc3QgcHNldWRvaGVhZGVyIGNoZWNr
IC0gYW5kIHR1bm5lbHMgb2Z0ZW4gdGVybWluYXRlIG9uIHJvdXRlcnMgdGhhdCBmb3J3YXJkIHBh
Y2tldHMuLi4pLiBUaGlzIGlzDQo+IG5ldHdvcmsgcG9sbHV0aW9uLg0KPiA+DQo+ID4gU28sIHVz
ZSBhIHplcm8gVURQIGNoZWNrc3VtLCBhbmQgdGhlIElQdjYgdHJhZmZpYyB5b3UgZ2VuZXJhdGUg
Y2FuIGJlIHBvdGVudGlhbGx5IGluamVjdGVkIGFueXdoZXJlIHRvIGFmZmVjdCBhbnl0aGluZywg
bW9kdWxvIGFsbA0KPiB0aGUgY2FyZWZ1bCBudWFuY2UgaW4gUkZDNjkzNiB0byBzdGFydCBndWFy
ZGluZyBhZ2FpbnN0IHRoaXMgLSBndWFyZHMgcmVxdWlyZWQgYnkgZXZlcnl0aGluZyBlbHNlLiBC
dXQgeW91ciB0dW5uZWwgdHJhZmZpYyBjYW4gaGF2ZSBpdHMNCj4gb3duIGNoZWNrcyBhbmQgaXRz
IG93biByZXBlYXQvcmVwbGF5LCBzbyB5b3UncmUgYWxyaWdodC4NCj4gPg0KPiA+IChVRFAtTGl0
ZSBwcm92aWRlcyBhIG1pbmltYWwgaW50ZXJmYWNlIHRvIGJ1aWxkIG9uIHdpdGggbmVjZXNzYXJ5
IGVuZGhvc3QgcHNldWRvLWhlYWRlciBjaGVjayBhbmQgbG93IGNvbXB1dGF0aW9uIGNvc3QgZm9y
DQo+IGFwcGxpY2F0aW9uIGRlc2lnbmVyczsgc2hhbWUgaXQncyBub3QgbW9yZSBwcmV2YWxlbnQu
KQ0KPiA+DQo+ID4gQW5hbG9naWVzIHdpdGggbmljZSBjbGVhbiBmYWN0b3JpZXMgcHVtcGluZyBp
bnRvIGRpcnR5IHJpdmVycyBmaXQgbmljZWx5IGhlcmUuIEl0J3MgYSB0cmFnZWR5IHRoYXQgcGVv
cGxlIGRvd25zdHJlYW0gd2VyZSByZWx5aW5nIG9uDQo+IHRoZSByaXZlciB3YXRlciwgYnV0IGl0
J3MgY2xlYXJseSBub3QgdGhlIGZhY3RvcnkgZGVzaWduZXIncyBmYXVsdC4gQXMgaWYuIFRob3Nl
IHBlb3BsZSBqdXN0IGRpZG4ndCBpbXBsZW1lbnQgdGhlIHNhZmVndWFyZHMgaW4gdGhlIHNtYWxs
DQo+IHByaW50LiBBbmQgZW52aXJvbm1lbnRhbCBwcm90ZWN0aW9uIHdhc24ndCBhIGRlc2lnbiBn
b2FsLiBXaHkgY2FyZSBhYm91dCB0aGUgY29tbW9ucz8NCj4gPg0KPiA+IE15IHRha2UgaGVyZSBp
cyB0aGF0IElQdjYgd2FzIG5vdCB3ZWxsLWRlc2lnbmVkIGluIHRoaXMgcmVnYXJkLiBBbiBJUCBo
ZWFkZXIgY2hlY2tzdW0gYWNyb3NzIG5vbi1tdXRhYmxlIGZpZWxkcywgZXhjbHVkaW5nIFFvUy9U
VEwNCj4gZXRjLiwgdGhhdCBkaWQgbm90IG5lZWQgdG8gYmUgcmVjb21wdXRlZCwgd291bGQgaGF2
ZSBiZWVuIHByZWZlcmFibGUuIEEgbWFuZGF0b3J5IGVuZGhvc3QgcHNldWRvaGVhZGVyIGNoZWNr
IHdvdWxkIGhhdmUgYmVlbg0KPiBwcmVmZXJhYmxlLiBFeHBlY3RpbmcgcHJvdG9jb2wgZGVzaWdu
ZXJzIHRvIGRvIHRoZSByaWdodCB0aGluZyBhYm92ZSBJUCBhbmQgZG8gdGhlIG5lY2Vzc2FyeSBw
c2V1ZG8taGVhZGVyIGNoZWNrIGhhcyBiZWVuDQo+IHJlcGVhdGVkbHkgZGVtb25zdHJhdGVkIHRv
IHByZXN1bWUgdG9vIG11Y2gga25vd2xlZGdlIGluIHRob3NlIHRoYXQgZm9sbG93LiBIYXJkbHkg
dGhlIG9ubHkgSVB2NiBtaXN0YWtlLCBidXQgbm90IG9uZSB3ZSBzaG91bGQNCj4gYmUgY29tcG91
bmRpbmcuDQo+ID4NCj4gPiBQbGVhc2UgZml4IEFFUk8sIGFuZCBmb2xsb3cgUkZDNjkzNidzIHJl
Y29tbWVuZGF0aW9uLg0KPiA+DQo+IEFub3RoZXIgYWx0ZXJuYXRpdmUgbWlnaHQgYmUgdG8gaW5j
bHVkZSBhIGNoZWNrc3VtIGluIHRoZQ0KPiBlbmNhcHN1bGF0aW9uIGhlYWRlciB0aGF0IGluY2x1
ZGVzIGEgcHNldWRvIGhlYWRlciBjb3ZlcmluZyBwb3J0cyBhbmQNCj4gYWRkcmVzc2VzLiBUaGlz
IGlzIHdoYXQgd2UgaW50ZW5kIHRvIGRvIGluIEdlbmVyaWMgVURQIEVuY2Fwc3VsYXRpb24NCj4g
KGRyYWZ0LWhlcmJlcnQtZ3VlY3N1bS0wMCkuDQoNClRoYW5rcyBmb3Igc3VwcGx5aW5nIHRoZSBm
aXguIFRoaXMgc2FtZSBhcHByb2FjaCBjYW4gYmUgYWRvcHRlZCBieSBBRVJPLCBidXQNCnBlcmhh
cHMgaXQgd291bGQgYmUgc3VmZmljaWVudCB0byBpbmNsdWRlIGp1c3QgdGhlIHBzZXVkb2hlYWRl
ciBjaGVja3N1bSBhbmQNCm5vdCB3b3JyeSBhYm91dCBzdXBwbHlpbmcgYSBjb3ZlcmFnZSBsZW5n
dGggdG8gY2hlY2sgYWRkaXRpb25hbCBieXRlcyBiZXlvbmQNCnRoZSBwc2V1ZG9oZWFkZXI/DQoN
CkFFUk8gaXMgYSBnZW5lcmljIFVEUCBlbmNhcHN1bGF0aW9uIGZvcm1hdCBmb3IgSVAtaW4tKGZv
byktaW4tVURQLWluLUlQDQplbmNhcHN1bGF0aW9uLiBUaGUgIihmb28pIiBjYW4gYmUgYW55dGhp
bmcsIGUuZy4sIEdSRSwgTVBMUywgRVNQLCBBSCwgZXRjLg0KSXMgdGhhdCB3aGF0IHlvdXIgYXJl
IHRyeWluZyB0byBkbywgdG9vPw0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBib2Vp
bmcuY29tDQoNCj4gPiBMbG95ZCBXb29kDQo+ID4gaHR0cDovL2Fib3V0Lm1lL2xsb3lkd29vZA0K
PiA+DQo+ID4geW91J2xsIG5vdGljZSBJJ20gbm90IGFsc28gYXNraW5nIHlvdSB0byBmaXggdGhl
IGJ1bmRsZSBwcm90b2NvbC4gTG9zdCBjYXVzZS4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+ID4gRnJvbTogdHN2d2cgPHRzdndnLWJvdW5jZXNAaWV0Zi5v
cmc+IG9uIGJlaGFsZiBvZiBUZW1wbGluLCBGcmVkIEwgPEZyZWQuTC5UZW1wbGluQGJvZWluZy5j
b20+DQo+ID4gU2VudDogV2VkbmVzZGF5LCAzIERlY2VtYmVyIDIwMTQgNzo1NyBBTQ0KPiA+IFRv
OiB0c3Z3Z0BpZXRmLm9yZzsgaW50LWFyZWFAaWV0Zi5vcmc7IHJvdXRpbmctZGlzY3Vzc2lvbkBp
ZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFt0c3Z3Z10gTXVsdGlwcm90b2NvbCB0dW5uZWxpbmcgb3Zl
ciBVRFAgdXNpbmcgQUVSTw0KPiA+DQo+ID4gSGVsbG8sDQo+ID4NCj4gPiBJIGFtIHJlcGxheWlu
ZyBhIG1lc3NhZ2UgYmVsb3cgdGhhdCB3YXMgb3JpZ2luYWxseSBwb3N0ZWQgb24gdGhlIHJvdXRp
bmctZGlzY3Vzc2lvbg0KPiA+IGxpc3QgeWVzdGVyZGF5LiBGb2xsb3ctdXAgZGlzY3Vzc2lvbiB3
YXMgdGhlbiBwb3N0ZWQgaW4gdHdvIGFkZGl0aW9uYWwgbWVzc2FnZXMuIFRoZQ0KPiA+IG1lc3Nh
Z2VzIGFyZSBoZXJlOg0KPiA+DQo+ID4gaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUv
d2ViL3JvdXRpbmctZGlzY3Vzc2lvbi9jdXJyZW50L21zZzAxOTQ5Lmh0bWwNCj4gPiBodHRwOi8v
d3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvcm91dGluZy1kaXNjdXNzaW9uL2N1cnJlbnQv
bXNnMDE5NTAuaHRtbA0KPiA+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9y
b3V0aW5nLWRpc2N1c3Npb24vY3VycmVudC9tc2cwMTk1MS5odG1sDQo+ID4NCj4gPiBJIGFtIGNy
b3NzLXBvc3RpbmcgdG8gdHJhbnNwb3J0IGFyZWEgYW5kIGludCBhcmVhIG5vdywgYmVjYXVzZSB0
aGVyZSBzZWVtcyB0byBiZQ0KPiA+IGFuIG92ZXJsYXAgb2YgaW50ZXJlc3RzIHdpdGggcmVzcGVj
dCB0byBVRFAgdHVubmVsaW5nIHRoYXQgbWF5IHRyYW5zY2VuZCB0cmFkaXRpb25hbA0KPiA+IGFy
ZWEgYm91bmRhcmllcy4gT3JpZ2luYWwgbWVzc2FnZSBhcHBlYXJzIGJlbG93OyBwbGVhc2UgcG9z
dCBjb21tZW50cyB0byB0aGUgbGlzdHMuDQo+ID4NCj4gPiBUaGFua3MgLSBGcmVkDQo+ID4gZnJl
ZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KPiA+DQo+ID4gLS0tDQo+ID4NCj4gPiBIZWxsbywNCj4g
Pg0KPiA+IEkgYW0gd29ya2luZyBvbiBhIHNwZWMgZm9yIGdlbmVyaWMgdHVubmVsaW5nIG9mIGFu
eSBwcm90b2NvbCBvdmVyIFVEUCwgaW5jbHVkaW5nDQo+ID4gTVBMUywgR1JFLCBJUHNlYywgZXRj
LiBUaGUgc3BlYyBpcyBjYWxsZWQgIkFFUk8iLCBhbmQgaXQgaW5jbHVkZXM6DQo+ID4NCj4gPiAg
IC0gYW4gZW5jYXBzdWxhdGlvbiBmb3JtYXQNCj4gPiAgIC0gYSBmcmFnbWVudGF0aW9uIGFuZCBy
ZWFzc2VtYmx5IGNhcGFiaWxpdHkgZm9yIE1UVSBtaXRpZ2F0aW9uDQo+ID4gICAtIGEgdmlydHVh
bCBsaW5rIG1vZGVsDQo+ID4gICAtIGEgY29udHJvbCBtZXNzYWdpbmcgbWVjaGFuaXNtDQo+ID4g
ICAtIGEgcm91dGluZyBhbmQgYWRkcmVzc2luZyBzeXN0ZW0gYmFzZWQgb24gQkdQDQo+ID4NCj4g
PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC10ZW1wbGluLWFlcm9saW5r
Lw0KPiA+DQo+ID4gSSB1bmRlcnN0YW5kIHRoYXQgdGhlcmUgaGF2ZSBiZWVuIGRpc2N1c3Npb25z
IHJlZ2FyZGluZyBwcm90b2NvbC1zcGVjaWZpYw0KPiA+IEdSRSBhbmQgTVBMUyBlbmNhcHN1bGF0
aW9ucyB3aXRoaW4gVURQLCBidXQgSSB3b3VsZCBsaWtlIHRvIG9mZmVyIHVwIEFFUk8NCj4gPiBh
cyBhIHByb3RvY29sLWluZGVwZW5kZW50IHdheSBvZiBhY2NvbW1vZGF0aW5nIFVEUCBlbmNhcHN1
bGF0aW9ucy4gSQ0KPiA+IGFsc28gYmVsaWV2ZSB0aGUgcm91dGluZyBzeXN0ZW0gYW5kIG90aGVy
IGFzcGVjdHMgb2YgQUVSTyBzaG91bGQgYmUgb2YNCj4gPiBpbnRlcmVzdCB0byB0aGUgcm91dGlu
ZyBhcmVhLg0KPiA+DQo+ID4gVGhpcyB3b3JrIGlzIGRlcml2ZWQgZnJvbSBhbiBlYXJsaWVyIGV4
cGVyaW1lbnRhbCBSRkMgKFJGQzY3MDYpIHdoaWNoIHdhcw0KPiA+IG9yaWdpbmFsbHkgYnJpZWZl
ZCB0byB0aGUgcm91dGluZyBhcmVhIHNldmVyYWwgeWVhcnMgYWdvIGFuZCBwdWJsaXNoZWQgYXMg
YW4NCj4gPiBBRC1zcG9uc29yZWQgSW5kaXZpZHVhbCBTdWJtaXNzaW9uIFJGQy4gVGhlIGN1cnJl
bnQgZG9jdW1lbnQgY2FuIGJlDQo+ID4gY29uc2lkZXJlZCBhcyBhIHNlY29uZCBlZGl0aW9uIG9m
IEFFUk8sIGFuZCB0aGUgZ29hbCBpcyB0byBhZHZhbmNlIGl0IHRvDQo+ID4gc3RhbmRhcmRzIHRy
YWNrLiBQbGVhc2Ugc2VuZCBhbnkgY29tbWVudHMgb3IgcXVlc3Rpb25zIHRvIHRoZSBsaXN0Lg0K
PiA+DQo+ID4gVGhhbmtzIC0gRnJlZA0KPiA+IGZyZWQubC50ZW1wbGluQGJvZWluZy5jb20NCj4g
Pg0KPiA+DQo=


From nobody Tue Dec  2 15:30:11 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4AB91A1BCA; Tue,  2 Dec 2014 15:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YJRbwo1BoRfL; Tue,  2 Dec 2014 15:30:00 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00C7A1A1AFC; Tue,  2 Dec 2014 15:29:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NTxQK008035; Tue, 2 Dec 2014 15:29:59 -0800
Received: from XCH-PHX-312.sw.nos.boeing.com (xch-phx-312.sw.nos.boeing.com [130.247.25.173]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NTpU9007038 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 15:29:51 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-312.sw.nos.boeing.com ([169.254.12.151]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:29:50 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvAAFowtA
Date: Tue, 2 Dec 2014 23:29:50 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7E7D@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/E50JefQj_aRvdPFLjLE8Es_l8to
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:30:02 -0000

Hi,

One other thing that may or may not be worth mentioning is that AERO alread=
y has an
IANA-assigned UDP port number:

aero               8060        udp    Asymmetric Extended Route    [IESG]  =
                                              [IETF_Chair]                 =
                                                       [RFC6706]
                                      Optimization (AERO)

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templin, F=
red L
> Sent: Tuesday, December 02, 2014 12:58 PM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [Int-area] Multiprotocol tunneling over UDP using AERO
>=20
> Hello,
>=20
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>=20
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>=20
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> ---
>=20
> Hello,
>=20
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>=20
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>=20
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>=20
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>=20
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Thu Dec  4 07:03:33 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 083EC1AD417; Thu,  4 Dec 2014 07:03:27 -0800 (PST)
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] autolearn=ham
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 ITLyP9ow97Om; Thu,  4 Dec 2014 07:03:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76CA81AD413; Thu,  4 Dec 2014 07:03:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141204150325.4521.92862.idtracker@ietfa.amsl.com>
Date: Thu, 04 Dec 2014 07:03:25 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/p3zjne2tt-Qqd6P75Yj0ggL5c1w
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-diffserv-intercon-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 15:03:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : DiffServ interconnection classes and practice
        Authors         : Ruediger Geib
                          David L. Black
	Filename        : draft-ietf-tsvwg-diffserv-intercon-00.txt
	Pages           : 22
	Date            : 2014-12-04

Abstract:
   This document proposes a limited and well defined set of DiffServ
   PHBs and codepoints to be applied at (inter)connections of two
   separately administered and operated networks.  Many network
   providers operate MPLS using Treatment Aggregates for traffic marked
   with different DiffServ PHBs, and use MPLS for interconnection with
   other networks.  This document offers a simple interconnection
   approach that may simplify operation of DiffServ for network
   interconnection among providers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-diffserv-intercon/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-diffserv-intercon-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Dec  6 01:12:16 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E761A0197 for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 01:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 F4rwdjMxlA73 for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 01:12:03 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 211411A0060 for <tsvwg@ietf.org>; Sat,  6 Dec 2014 01:12:03 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 05B802B44C5; Sat,  6 Dec 2014 09:12:01 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Sat, 6 Dec 2014 09:12:01 -0000
Message-ID: <b62d018438d7275677c3adfd91acd07b.squirrel@spey.erg.abdn.ac.uk>
Date: Sat, 6 Dec 2014 09:12:01 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/eyZnRtzT73m5R3bzv7W55WElDl8
Subject: [tsvwg] Publication has been requested for draft-ietf-tsvwg-sctp-dtls-encaps-06 as PS
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2014 09:12:06 -0000

Gorry Fairhurst as tsvwg co-chair  has requested publication of
draft-ietf-tsvwg-sctp-dtls-encaps-06 as Proposed Standard on behalf of the
TSVWG working group.

--------------------------------------------------------------------------

The writeup is:

As required by RFC4858, this is the current template for the Document
Shepherd Write-Up.
Changes are expected over time. This version is dated 24 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard, Internet
Standard, Informational, Experimental, or Historic)? Why is this the
proper type of RFC? Is this type of RFC indicated in the title page
header?

PS

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary:
The Stream Control Transmission Protocol (SCTP) is a transport protocol
originally defined to run on top of the network protocols IPv4 or IPv6.
This document specifies how SCTP can be used on top of the Datagram
Transport Layer Security (DTLS) protocol. Using encapsulation method
described in this document, SCTP is agnostic about the protocols being
used below DTLS, explicit IP addresses can not be used in the SCTP control
chunks.

Working Group Summary:
This document is being prepared at the request of the RTCweb/webRTC activity.

Document Quality:
The document is thought ready to publish. As far as the authors know, this
this is implemented in the Chrome, Firefox and Opera browser. PMTUD is not
yet implemented.

Personnel:

Who is the Document Shepherd?
G Fairhurst (TSVWG Co-Chair)

Who is the Responsible Area Director?
Spencer Dawkins (TSV AD)

(3) Briefly describe the review of this document that was performed by the
Document Shepherd. If this version of
the document is not ready for publication, please explain why the document
is being forwarded to the IESG.

The document was reviewed against related documents and is thought ready
to proceed. Security expertise was requested (Ekr) to help identify
requirements for using DTLS and  to recommend the appropriate version of
DTLS.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

No

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that took
place.

It should be reviewed by security experts.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the IESG
should be aware of? For example, perhaps he or she is uncomfortable with
certain parts of the document, or has concerns whether there really is a
need for it. In any event, if the WG has discussed those issues and has
indicated that it still wishes to advance the document, detail those
concerns here.

No.

(7) Has each author confirmed that any and all appropriate IPR disclosures
required for full conformance with the provisions of BCP 78 and BCP 79
have already been filed. If not, explain why?

M. Tuexen- Confirmed.
R. Stewart - Confirmed.
R. Jesup  - Confirmed.
S. Loreto - Confirmed.

(8) Has an IPR disclosure been filed that references this document? If so,
summarize any WG discussion and conclusion regarding the IPR disclosures.

None known.

(9) How solid is the WG consensus behind this document? Does it represent
the strong concurrence of a few individuals, with others being silent, or
does the WG as a whole understand and agree with it?

The document received support from 5 people within TSVWG plus the WG
chair. The work replayed to RTCweb requirements. Feedback was received
from RTCweb implementors during document development. A WGLC ended 28th
February 2014, with some reviews that resulted in an updated document.
Since then discussion has focussed on which version of DTLS to mandate.
This conclude in November 2014.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

No

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

None

(12) Describe how the document meets any required formal review criteria,
such as the MIB Doctor, media type, and URI type reviews.

None

(13) Have all references within this document been identified as either
normative or informative?

Yes

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

OK

(15) Are there downward normative references references (see RFC 3967)? If
so, list these downward references to support the Area Director in the
Last Call procedure.

No

(16) Will publication of this document change the status of any existing
RFCs? Are those RFCs listed on the title page header, listed in the
abstract, and discussed in the introduction? If the RFCs are not listed in
the Abstract and Introduction, explain why, and point to the part of the
document where the relationship of this document to the other RFCs is
discussed. If this information is not in the document, explain why the WG
considers it unnecessary.
No

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes are
associated with the appropriate reservations in IANA registries. Confirm
that any referenced IANA registries have been clearly identified. Confirm
that newly created IANA registries include a detailed specification of the
initial contents for the registry, that allocations procedures for future
registrations are defined, and a reasonable name for the new registry has
been suggested (see RFC 5226).
This document requires no actions from IANA

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find useful
in selecting the IANA Experts for these new registries.

None

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

None

--------------------------------------------------------------------------

You may verify the document's state at
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/


From nobody Sat Dec  6 01:14:44 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6321A1A25 for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 01:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 2IoTtZiHHYhP for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 01:14:37 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6591A0197 for <tsvwg@ietf.org>; Sat,  6 Dec 2014 01:14:37 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 10ACD2B44C5; Sat,  6 Dec 2014 09:14:37 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Sat, 6 Dec 2014 09:14:37 -0000
Message-ID: <34d68ad7e6ae4bda7d4daa5a50c3aefe.squirrel@spey.erg.abdn.ac.uk>
Date: Sat, 6 Dec 2014 09:14:37 -0000
From: gorry@erg.abdn.ac.uk
To: tsvwg@ietf.org
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/UjQp2u1IofREb4KsPep76grtbIo
Subject: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-06 as a PS (editorial comment)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2014 09:14:39 -0000

I've just requested the publication of the above ID, however I have one
editorial request that I would like to suggest when the document is being
revised,

 I think I it would be wise to change the introductory paragraph in
section 1 to also mention the relationship to different versions of DTLS.
I think the current introduction could be read as only defining support
for DTLS 1.0, which is not correct. Please consider this as an early
comment in the next stage of review.

OLD:
 This document specifies
   how SCTP is used on top of the Datagram Transport Layer Security
   (DTLS) protocol defined in [RFC4347].

SUGGESTED NEW:
 This document specifies
   how SCTP is used on top of the Datagram Transport Layer Security
   (DTLS) protocol. DTLS 1.0 is defined in [RFC4347] and the present
   latest version, DTLS 1.2, is defined in [RFC6347].

Best wishes,

Gorry


From nobody Sat Dec  6 03:35:50 2014
Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A94A21A9034 for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 03:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 AQy3y2XuPIHE for <tsvwg@ietfa.amsl.com>; Sat,  6 Dec 2014 03:35:48 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D904D1A9029 for <tsvwg@ietf.org>; Sat,  6 Dec 2014 03:35:47 -0800 (PST)
Received: from [192.168.1.200] (p508F21C8.dip0.t-ipconnect.de [80.143.33.200]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 2066C1C0B31AE; Sat,  6 Dec 2014 12:35:43 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset=iso-8859-1
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-Priority: 3 (Normal)
In-Reply-To: <34d68ad7e6ae4bda7d4daa5a50c3aefe.squirrel@spey.erg.abdn.ac.uk>
Date: Sat, 6 Dec 2014 12:35:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <042C4FCB-85E5-4D38-9946-1FB15A3E6103@lurchi.franken.de>
References: <34d68ad7e6ae4bda7d4daa5a50c3aefe.squirrel@spey.erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/XMeXuQHrUhX3W3iDaXOQQ7F3AHQ
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] draft-ietf-tsvwg-sctp-dtls-encaps-06 as a PS (editorial comment)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Dec 2014 11:35:49 -0000

On 06 Dec 2014, at 10:14, gorry@erg.abdn.ac.uk wrote:

> I've just requested the publication of the above ID, however I have =
one
> editorial request that I would like to suggest when the document is =
being
> revised,
>=20
> I think I it would be wise to change the introductory paragraph in
> section 1 to also mention the relationship to different versions of =
DTLS.
> I think the current introduction could be read as only defining =
support
> for DTLS 1.0, which is not correct. Please consider this as an early
> comment in the next stage of review.
>=20
> OLD:
> This document specifies
>   how SCTP is used on top of the Datagram Transport Layer Security
>   (DTLS) protocol defined in [RFC4347].
>=20
> SUGGESTED NEW:
> This document specifies
>   how SCTP is used on top of the Datagram Transport Layer Security
>   (DTLS) protocol. DTLS 1.0 is defined in [RFC4347] and the present
>   latest version, DTLS 1.2, is defined in [RFC6347].
OK. I've committed the change to CVS. It will be include in the next =
revision.

Best regards
Michael
>=20
> Best wishes,
>=20
> Gorry
>=20
>=20


From nobody Mon Dec  8 13:57:22 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F27E1ACFE7 for <tsvwg@ietfa.amsl.com>; Mon,  8 Dec 2014 13:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ZSejL-qlx07S for <tsvwg@ietfa.amsl.com>; Mon,  8 Dec 2014 13:57:17 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCEC31ACFDE for <tsvwg@ietf.org>; Mon,  8 Dec 2014 13:57:16 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id u10so4386825lbd.20 for <tsvwg@ietf.org>; Mon, 08 Dec 2014 13:57:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H9Q740bouoasI47gq+89ppA7V9LC5CkaVi3Js7Fe2pw=; b=vD1bKa7IjcQ9cbtAW+agG+x48RWuxQGnzYAHbBvLMooPNsjlQXUH9NpQNKX/Tvhv1D lXSo9ss61VHt+afU/HgguaY0MMZAc6vsFd3TM2Fkz6W6PtWtlRg2yfUV1z5ZCXU9+4zE UQgIQM9B8x62etlWsTPXK0lkg9D+4XxLudfReCiW+WET8UPZK4LVlDfO0t1tUJxYfRYM xGLl+Gi91hWyVmvIAnuP0nvJnxpixBsA0Nu/cR/qOuRuzdPD4rEcSUc0V0BSXLCr4FYp yQElJhDOYGNATtkVOcPhaF8BV5oB1HJxDha7BvkaIy1NXijHOthWrB7Typug1Z8fZx/I P3Dw==
MIME-Version: 1.0
X-Received: by 10.152.25.168 with SMTP id d8mr18681407lag.41.1418075835369; Mon, 08 Dec 2014 13:57:15 -0800 (PST)
Received: by 10.152.28.229 with HTTP; Mon, 8 Dec 2014 13:57:15 -0800 (PST)
In-Reply-To: <20141201081017.17091.54167.idtracker@ietfa.amsl.com>
References: <20141201081017.17091.54167.idtracker@ietfa.amsl.com>
Date: Mon, 8 Dec 2014 15:57:15 -0600
Message-ID: <CAKKJt-chWfT8FpS3AG-ZG3s88MBzWPWERf1_POPSTYNFUaS9FA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org
Content-Type: multipart/alternative; boundary=089e0160a5d46e8e4c0509bb8265
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/MImxnTnbyu5S0ArGTEUmLi37ado
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call Expired: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 21:57:19 -0000

--089e0160a5d46e8e4c0509bb8265
Content-Type: text/plain; charset=UTF-8

Dear Authors,

The Last Call has ended, and I've seen directorate reviews back from Dan
(OPS) and Joe (SEC).

Could you let me know when I should expect responses?

If I've missed responses, I apologize, of course!

Thanks,

Spencer

On Mon, Dec 1, 2014 at 2:10 AM, DraftTracker Mail System <
iesg-secretary@ietf.org> wrote:

>
> Please DO NOT reply to this email.
>
> I-D: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
> ID Tracker URL:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
>
> IETF Last Call has ended, and the state has been changed to
> Waiting for Writeup.
>
>

--089e0160a5d46e8e4c0509bb8265
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear Authors,<div><br></div><div>The Last Call has ended, =
and I&#39;ve seen directorate reviews back from Dan (OPS) and Joe (SEC).=C2=
=A0</div><div><br></div><div>Could you let me know when I should expect res=
ponses?</div><div><br></div><div>If I&#39;ve missed responses, I apologize,=
 of course!</div><div><br></div><div>Thanks,</div><div><br></div><div>Spenc=
er</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Mon, Dec 1, 2014 at 2:10 AM, DraftTracker Mail System <span dir=3D"ltr">&lt=
;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretar=
y@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Please DO NOT reply to this email.<br>
<br>
I-D: &lt;draft-ietf-tsvwg-sctp-prpolicies-05.txt&gt;<br>
ID Tracker URL: <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-tsvwg=
-sctp-prpolicies/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-=
ietf-tsvwg-sctp-prpolicies/</a><br>
<br>
IETF Last Call has ended, and the state has been changed to<br>
Waiting for Writeup.<br>
<br>
</blockquote></div><br></div>

--089e0160a5d46e8e4c0509bb8265--


From nobody Mon Dec  8 15:56:29 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB701A0392; Mon,  8 Dec 2014 15:56:21 -0800 (PST)
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] autolearn=ham
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 KKPIqtcWIvlF; Mon,  8 Dec 2014 15:56:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8D71A0062; Mon,  8 Dec 2014 15:56:19 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141208235619.4442.37821.idtracker@ietfa.amsl.com>
Date: Mon, 08 Dec 2014 15:56:19 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/gVJ0yFbPt7wgmZJBB3UbKfXufNg
Cc: tsvwg@ietf.org
Subject: [tsvwg] Last Call: <draft-ietf-tsvwg-port-use-06.txt> (Recommendations for Transport Port Number Uses) to Best Current Practice
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 23:56:21 -0000

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'Recommendations for Transport Port Number Uses'
  <draft-ietf-tsvwg-port-use-06.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-12-22. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document provides recommendations to application and service
   designers on how to use the transport protocol port number space. IT
   complements (but does not update) RFC6335, which focuses on IANA
   process.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-port-use/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Tue Dec  9 04:16:58 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708D31A0174 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 04:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 wWpDgI3F9RGJ for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 04:16:52 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605CD1A00F0 for <tsvwg@ietf.org>; Tue,  9 Dec 2014 04:16:51 -0800 (PST)
Received: from [192.168.1.200] (p508F2D39.dip0.t-ipconnect.de [80.143.45.57]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 4EDDD1C104D8E; Tue,  9 Dec 2014 13:16:48 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAKKJt-chWfT8FpS3AG-ZG3s88MBzWPWERf1_POPSTYNFUaS9FA@mail.gmail.com>
Date: Tue, 9 Dec 2014 13:16:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECFB05D1-CE89-42E4-8615-729EFA046E6E@fh-muenster.de>
References: <20141201081017.17091.54167.idtracker@ietfa.amsl.com> <CAKKJt-chWfT8FpS3AG-ZG3s88MBzWPWERf1_POPSTYNFUaS9FA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/xpKs2Z6DlAGQlv6vpu1r4ohOue8
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call Expired: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 12:16:54 -0000

On 08 Dec 2014, at 22:57, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:

> Dear Authors,
>=20
> The Last Call has ended, and I've seen directorate reviews back from =
Dan (OPS) and Joe (SEC).=20
Regarding the comments from Joe: I discussed with him a text change =
addressing his comment
and this text change will be in the next revision. The discussion =
happened on December 1st.
Look for "Re: secdir review of draft-ietf-tsvwg-sctp-prpolicies-05" in =
your inbox...

Regarding the comments from Dan: Let me try to address them later today =
or tomorrow. I need
to figure out what he really wants. Some of the stuff he's asking for is =
normally not dealt
with: He's asking for installation instructions, but usually we don't =
deal with "How to install an OS"
or "How to install an App if it includes a transport stack"...
I'll go through the questions and we can see what changes he want.
>=20
> Could you let me know when I should expect responses?
>=20
> If I've missed responses, I apologize, of course!
Do you want the document to be resubmitted with the changes required to =
address the issues
brought up by Dan and Joe?

Best regards
Michael
>=20
> Thanks,
>=20
> Spencer
>=20
> On Mon, Dec 1, 2014 at 2:10 AM, DraftTracker Mail System =
<iesg-secretary@ietf.org> wrote:
>=20
> Please DO NOT reply to this email.
>=20
> I-D: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
> ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
>=20
> IETF Last Call has ended, and the state has been changed to
> Waiting for Writeup.
>=20
>=20


From nobody Tue Dec  9 07:27:44 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9B01A19F7 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 07:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 QUfkKTbszB1E for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 07:27:40 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B68111A0673 for <tsvwg@ietf.org>; Tue,  9 Dec 2014 07:27:39 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id l4so671964lbv.25 for <tsvwg@ietf.org>; Tue, 09 Dec 2014 07:27:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QIgGU9juMFW+rWEi8EkNgTALBa4XWXWLaFl12+zZHOc=; b=QxsSXHJv04OSqsz//VJga4+mz5zQIxyejIzW9RAVlCkJOStVDucq2EjW7FGs+1iR35 35llFOK+tes8fkfXp8yTpR+grX1cGtfzEnXBSlCTRGZXDOt35tGW3AiHjSRAITFfOVQ4 lnmDo6AiO/UpA+6TSMxotczP8HTJnwYlWIHxhvu1DTBCBV5mOEWHuwrOJiU4mV+gRM0K bHWYmugty6USHFs57t29H9VTpNZGI+o6sR/r5A226n63uXOyeTFNTD9hF9mJJbQjfz2y SOlntXWZTBEDOOPlYru4KJtAHgEXT3VkzDZ9cLRuSZQlCT/7Zj6VFs/a+qYBhtoK1J7S ztSQ==
MIME-Version: 1.0
X-Received: by 10.152.21.66 with SMTP id t2mr22019823lae.27.1418138858187; Tue, 09 Dec 2014 07:27:38 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Tue, 9 Dec 2014 07:27:38 -0800 (PST)
In-Reply-To: <ECFB05D1-CE89-42E4-8615-729EFA046E6E@fh-muenster.de>
References: <20141201081017.17091.54167.idtracker@ietfa.amsl.com> <CAKKJt-chWfT8FpS3AG-ZG3s88MBzWPWERf1_POPSTYNFUaS9FA@mail.gmail.com> <ECFB05D1-CE89-42E4-8615-729EFA046E6E@fh-muenster.de>
Date: Tue, 9 Dec 2014 09:27:38 -0600
Message-ID: <CAKKJt-cThANKcUvoDPxsjLwxssdjXwQStK5Uc7_178+JT2t3CQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=089e0141a05ee2737b0509ca2e2a
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_2prMgE-HnHUM8psl1PvgHd580I
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg-chairs@tools.ietf.org" <tsvwg-chairs@tools.ietf.org>, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] Last Call Expired: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 15:27:42 -0000

--089e0141a05ee2737b0509ca2e2a
Content-Type: text/plain; charset=UTF-8

Hi, Michael,

On Tue, Dec 9, 2014 at 6:16 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> On 08 Dec 2014, at 22:57, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
> > Dear Authors,
> >
> > The Last Call has ended, and I've seen directorate reviews back from Dan
> (OPS) and Joe (SEC).
> Regarding the comments from Joe: I discussed with him a text change
> addressing his comment
> and this text change will be in the next revision. The discussion happened
> on December 1st.
> Look for "Re: secdir review of draft-ietf-tsvwg-sctp-prpolicies-05" in
> your inbox...
>

I thought I remembered seeing that, but it didn't pop out at me, even after
it ended up in the right mail folder. Thanks for the pointer, and it looks
like you're fine there.

You should probably suggest to Nomcom that they need to think about how
well TSV ADs can see :-)


> Regarding the comments from Dan: Let me try to address them later today or
> tomorrow. I need
> to figure out what he really wants. Some of the stuff he's asking for is
> normally not dealt
> with: He's asking for installation instructions, but usually we don't deal
> with "How to install an OS"
> or "How to install an App if it includes a transport stack"...
> I'll go through the questions and we can see what changes he want.
>

I agree - he's going down a checklist for pretty much any protocol, and
you're doing an extension of an older protocol, so I'm not surprised that a
lot of the items on the checklist don't fit. It would be great if we
thought about that checklist more often for future work, but you're
reacting the way I'd expect, and support.

Both OPS and SEC have ADs who carefully watch what happens in response to
their directorate reviews, so making sure your replies go to the same
audience as the reviews did, is a good thing. I'm just mentioning that, as
you're starting your chat with Dan.


> >
> > Could you let me know when I should expect responses?
> >
> > If I've missed responses, I apologize, of course!
> Do you want the document to be resubmitted with the changes required to
> address the issues
> brought up by Dan and Joe?


That would be great!

Spencer


> Best regards
> Michael
> >
> > Thanks,
> >
> > Spencer
> >
> > On Mon, Dec 1, 2014 at 2:10 AM, DraftTracker Mail System <
> iesg-secretary@ietf.org> wrote:
> >
> > Please DO NOT reply to this email.
> >
> > I-D: <draft-ietf-tsvwg-sctp-prpolicies-05.txt>
> > ID Tracker URL:
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/
> >
> > IETF Last Call has ended, and the state has been changed to
> > Waiting for Writeup.
> >
> >
>
>

--089e0141a05ee2737b0509ca2e2a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Michael,<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Dec 9, 2014 at 6:16 AM, Michael Tuexen <span dir=
=3D"ltr">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_blank">tue=
xen@fh-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-colo=
r:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=3D=
"">On 08 Dec 2014, at 22:57, Spencer Dawkins at IETF &lt;<a href=3D"mailto:=
spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt; wrote:=
<br>
<br>
&gt; Dear Authors,<br>
&gt;<br>
&gt; The Last Call has ended, and I&#39;ve seen directorate reviews back fr=
om Dan (OPS) and Joe (SEC).<br>
</span>Regarding the comments from Joe: I discussed with him a text change =
addressing his comment<br>
and this text change will be in the next revision. The discussion happened =
on December 1st.<br>
Look for &quot;Re: secdir review of draft-ietf-tsvwg-sctp-prpolicies-05&quo=
t; in your inbox...<br></blockquote><div><br></div><div>I thought I remembe=
red seeing that, but it didn&#39;t pop out at me, even after it ended up in=
 the right mail folder. Thanks for the pointer, and it looks like you&#39;r=
e fine there.<br><br>You should probably suggest to Nomcom that they need t=
o think about how well TSV ADs can see :-)</div><div>=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width=
:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-lef=
t:1ex">Regarding the comments from Dan: Let me try to address them later to=
day or tomorrow. I need<br>
to figure out what he really wants. Some of the stuff he&#39;s asking for i=
s normally not dealt<br>
with: He&#39;s asking for installation instructions, but usually we don&#39=
;t deal with &quot;How to install an OS&quot;<br>
or &quot;How to install an App if it includes a transport stack&quot;...<br=
>
I&#39;ll go through the questions and we can see what changes he want.<br><=
/blockquote><div><br></div><div>I agree - he&#39;s going down a checklist f=
or pretty much any protocol, and you&#39;re doing an extension of an older =
protocol, so I&#39;m not surprised that a lot of the items on the checklist=
 don&#39;t fit. It would be great if we thought about that checklist more o=
ften for future work, but you&#39;re reacting the way I&#39;d expect, and s=
upport.</div><div><br></div><div>Both OPS and SEC have ADs who carefully wa=
tch what happens in response to their directorate reviews, so making sure y=
our replies go to the same audience as the reviews did, is a good thing. I&=
#39;m just mentioning that, as you&#39;re starting your chat with Dan.<br><=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bor=
der-left-style:solid;padding-left:1ex">
<span class=3D"">&gt;<br>
&gt; Could you let me know when I should expect responses?<br>
&gt;<br>
&gt; If I&#39;ve missed responses, I apologize, of course!<br>
</span>Do you want the document to be resubmitted with the changes required=
 to address the issues<br>
brought up by Dan and Joe?</blockquote><div><br></div><div>That would be gr=
eat!=C2=A0<br></div><div><br></div><div>Spencer</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-=
width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddin=
g-left:1ex">Best regards<br>
<span class=3D""><font color=3D"#888888">Michael<br>
</font></span><div class=3D""><div class=3D"h5">&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; On Mon, Dec 1, 2014 at 2:10 AM, DraftTracker Mail System &lt;<a href=
=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<=
br>
&gt;<br>
&gt; Please DO NOT reply to this email.<br>
&gt;<br>
&gt; I-D: &lt;draft-ietf-tsvwg-sctp-prpolicies-05.txt&gt;<br>
&gt; ID Tracker URL: <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-=
tsvwg-sctp-prpolicies/" target=3D"_blank">http://datatracker.ietf.org/doc/d=
raft-ietf-tsvwg-sctp-prpolicies/</a><br>
&gt;<br>
&gt; IETF Last Call has ended, and the state has been changed to<br>
&gt; Waiting for Writeup.<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--089e0141a05ee2737b0509ca2e2a--


From nobody Tue Dec  9 08:48:11 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338DD1A8960 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 08:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 ePc1FX_Z0hfP for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 08:48:05 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2EE61A877A for <tsvwg@ietf.org>; Tue,  9 Dec 2014 08:48:04 -0800 (PST)
Received: from [10.225.7.42] (unknown [194.95.73.101]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 1F3901C104FC1; Tue,  9 Dec 2014 17:48:03 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com>
Date: Tue, 9 Dec 2014 17:48:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com>
To: Spencer Dawkins <spencerdawkins@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/nIARpG8hqrvNkMGRpfNSBuM4IDA
Cc: draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 16:48:07 -0000

On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com> =
wrote:

> Dear Authors,
>=20
> I had a small number of comments, mostly but not entirely at nit =
level, on this draft. I suspect that you would see them again from other =
ADs and from review teams.=20
Hi Spencer,

thanks for the comments. See my replies inline.
>=20
> Would you like to respin before Last Call?
Sure. This makes things simple, I think and will make Gorry happy, who =
suggested already
a text change...

Best regards
Michael
>=20
> Spencer
>=20
> -- my notes
>=20
> In this text:
>=20
> 3.  Encapsulation and Decapsulation Procedure
>=20
>    When an SCTP packet is provided to the DTLS layer, the complete =
SCTP
>    packet, consisting of the SCTP common header and a number of SCTP
>    chunks, MUST be handled as the payload of the application layer
>    protocol of DTLS.  When the DTLS layer has processed a DTLS record
>    containing a message of the application layer protocol, the payload
>    MUST be given up to the SCTP layer.  The SCTP layer expects an SCTP
>    common header followed by a number of SCTP chunks.
>   =20
> I don't read the MUSTs as 2119 MUSTs. You're just describing =
functionality. "is handled" and "is given up to" (which I might suggest =
saying as "is passed to") are probably more appropriate.
OK, changed. I think there was a comment requesting some normative =
language in the part
of the document describing the actual encap/decaps, that is why the MUST =
went in. But
if you think this is not necessary, I take them out.
>   =20
>    In this text:
>=20
> 5.  DTLS Considerations
>=20
>    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
>    as the network layer protocol, the DTLS implementation SHOULD allow
>    the DTLS user to enforce that the corresponding IPv4 packet is sent
>    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
>    not possible, for example due to implementation restrictions, a =
safe
>    value for the path MTU has to be used by the SCTP stack.  It is
>    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
>                         ^^^^ is this "safe"?
This is what the WG thinks is save. We discussed this also with members
of the RTCWeb WG. Do you think that we should use a different value? If =
yes,
which one? The motivation was based on the value for IPv6, and then =
taking
into account some more bytes for headers... and we ended up with 1200.
>   =20
>    note that [RFC1122] only requires end hosts to be able to =
reassemble
>    fragmented IP packets of reassembled size of 576 bytes.
>   =20
> In this text:
>=20
> 5.  DTLS Considerations
>=20
>    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
>    as the network layer protocol, the DTLS implementation SHOULD allow
>    the DTLS user to enforce that the corresponding IPv4 packet is sent
>    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
>    not possible, for example due to implementation restrictions, a =
safe
>    value for the path MTU has to be used by the SCTP stack.  It is
>    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
>    note that [RFC1122] only requires end hosts to be able to =
reassemble
>    fragmented IP packets of reassembled size of 576 bytes.
>                             ^^^^^^^^^^^^^^^^^^^
> I'm not sure you need to say "reassembled size of", but if you don't =
just delete this text, I'd suggest "able to reassemble fragmented IP =
packets up to 576 bytes in length".
Taken.
>=20
> In this text:
>=20
> 6.5.  Partial Reliability Extension
>=20
>    Partial reliability as defined in [RFC3758] can be used in
>    combination with DTLS encapsulation.  It is also possible to use
>                                             ^^^^^^^^^^^^^^^^
>    additional PR-SCTP policies.
>   =20
> Is there a reference you could provide for implementers? Perhaps to =
draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but =
please note my use of future tense in 6.7 comment ...
Changed to
It is also possible to use
additional PR-SCTP policies, for example the ones defined in
<xref target=3D'I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
>   =20
> In this text:
>=20
> 6.7.  Interleaving of Large User Messages
>=20
>    SCTP as defined in [RFC4960] does not support the interleaving of
>    large user messages that need to be fragmented and reassembled by =
the
>    SCTP layer.  The protocol extension defined in
>    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be =
used
>    with DTLS encapsulation.
>   =20
> I think I understand why you have =
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as =
Informational, but it feels like it's on the edge of being Normative, or =
at least implementers are encouraged to support this extension now. Is =
this important enough to need to be said in this specification? If so, =
would it be correct to say this?
>=20
>    The protocol extension being defined in
>    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and =
could be used
>    with DTLS encapsulation.
I just want to say that the extension defined in =
I-D.ietf-tsvwg-sctp-ndata (whatever RFC it will be)
can be used with DTLS encaps. For RTCWeb it will be used (it is =
mandatory to implement), but there
might be other use cases where this extension is not necessary.
Since I'm not sure I got the point you want to make, please let me know =
if my intention is now
clearer and which text you prefer to express this.

Best regards
Michael


From nobody Tue Dec  9 09:02:59 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16DC31A8979 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 09:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 W49-wZPmKEUK for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 09:02:38 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE8D31A894F for <tsvwg@ietf.org>; Tue,  9 Dec 2014 09:02:34 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id f15so937489lbj.13 for <tsvwg@ietf.org>; Tue, 09 Dec 2014 09:02:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cqR0V77lwtLObwmvQMu3JzsTwA6wtDvvovzt2cFDwjA=; b=yCwPY360qisOTPNxx4aHkJQg0znLMml1u/HMD6DW4gpv61P2WjY7OAIPo+Wv5V39mn oUktn2DzjLNUbUje+wJDHwPY833Wrsb11pwqfrSBDpslAGEwJC0anwNajUILGz5Nqfq/ jGaBElbmM+hi/u6h4RqC23Uu5VEZJFawDG0scjr1oo0ak+quqQCvlI6wfrZw1IepscRQ 1NQtBpJn+uM3TvNcW9KGusyUFsls+QSULtiIemuAIbgrrb1zXfpwRYbZbnvsQhueUiIu fuLNTxZ6yEk7UU9lAsUROhBrq0abo5rWlz0DbsoVycqadeloOdTfwvn/ORQ/v8lDG8QV uBKA==
MIME-Version: 1.0
X-Received: by 10.112.93.231 with SMTP id cx7mr22379709lbb.89.1418144553320; Tue, 09 Dec 2014 09:02:33 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Tue, 9 Dec 2014 09:02:33 -0800 (PST)
In-Reply-To: <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de>
Date: Tue, 9 Dec 2014 11:02:33 -0600
Message-ID: <CAKKJt-c162EB7A6TkmPv11rJ2phe6ek+JYOFQRnfc8e7rTxNXA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=001a11348be85747d80509cb823b
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/LHnj6j0ma49omSLhSyLLVLSLzxo
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 17:02:50 -0000

--001a11348be85747d80509cb823b
Content-Type: text/plain; charset=UTF-8

I'm on a telechat now, but on one point - I'm not asking about 1200, I'm
asking whether the word "save" is supposed to be "safe"!

Spencer

On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com>
> wrote:
>
> > Dear Authors,
> >
> > I had a small number of comments, mostly but not entirely at nit level,
> on this draft. I suspect that you would see them again from other ADs and
> from review teams.
> Hi Spencer,
>
> thanks for the comments. See my replies inline.
> >
> > Would you like to respin before Last Call?
> Sure. This makes things simple, I think and will make Gorry happy, who
> suggested already
> a text change...
>
> Best regards
> Michael
> >
> > Spencer
> >
> > -- my notes
> >
> > In this text:
> >
> > 3.  Encapsulation and Decapsulation Procedure
> >
> >    When an SCTP packet is provided to the DTLS layer, the complete SCTP
> >    packet, consisting of the SCTP common header and a number of SCTP
> >    chunks, MUST be handled as the payload of the application layer
> >    protocol of DTLS.  When the DTLS layer has processed a DTLS record
> >    containing a message of the application layer protocol, the payload
> >    MUST be given up to the SCTP layer.  The SCTP layer expects an SCTP
> >    common header followed by a number of SCTP chunks.
> >
> > I don't read the MUSTs as 2119 MUSTs. You're just describing
> functionality. "is handled" and "is given up to" (which I might suggest
> saying as "is passed to") are probably more appropriate.
> OK, changed. I think there was a comment requesting some normative
> language in the part
> of the document describing the actual encap/decaps, that is why the MUST
> went in. But
> if you think this is not necessary, I take them out.
> >
> >    In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is used
> >    as the network layer protocol, the DTLS implementation SHOULD allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> >    not possible, for example due to implementation restrictions, a safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> >                         ^^^^ is this "safe"?
> This is what the WG thinks is save. We discussed this also with members
> of the RTCWeb WG. Do you think that we should use a different value? If
> yes,
> which one? The motivation was based on the value for IPv6, and then taking
> into account some more bytes for headers... and we ended up with 1200.
> >
> >    note that [RFC1122] only requires end hosts to be able to reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >
> > In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is used
> >    as the network layer protocol, the DTLS implementation SHOULD allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> >    not possible, for example due to implementation restrictions, a safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> >    note that [RFC1122] only requires end hosts to be able to reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >                             ^^^^^^^^^^^^^^^^^^^
> > I'm not sure you need to say "reassembled size of", but if you don't
> just delete this text, I'd suggest "able to reassemble fragmented IP
> packets up to 576 bytes in length".
> Taken.
> >
> > In this text:
> >
> > 6.5.  Partial Reliability Extension
> >
> >    Partial reliability as defined in [RFC3758] can be used in
> >    combination with DTLS encapsulation.  It is also possible to use
> >                                             ^^^^^^^^^^^^^^^^
> >    additional PR-SCTP policies.
> >
> > Is there a reference you could provide for implementers? Perhaps to
> draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but
> please note my use of future tense in 6.7 comment ...
> Changed to
> It is also possible to use
> additional PR-SCTP policies, for example the ones defined in
> <xref target='I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
> >
> > In this text:
> >
> > 6.7.  Interleaving of Large User Messages
> >
> >    SCTP as defined in [RFC4960] does not support the interleaving of
> >    large user messages that need to be fragmented and reassembled by the
> >    SCTP layer.  The protocol extension defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be used
> >    with DTLS encapsulation.
> >
> > I think I understand why you have
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as
> Informational, but it feels like it's on the edge of being Normative, or at
> least implementers are encouraged to support this extension now. Is this
> important enough to need to be said in this specification? If so, would it
> be correct to say this?
> >
> >    The protocol extension being defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and could
> be used
> >    with DTLS encapsulation.
> I just want to say that the extension defined in I-D.ietf-tsvwg-sctp-ndata
> (whatever RFC it will be)
> can be used with DTLS encaps. For RTCWeb it will be used (it is mandatory
> to implement), but there
> might be other use cases where this extension is not necessary.
> Since I'm not sure I got the point you want to make, please let me know if
> my intention is now
> clearer and which text you prefer to express this.
>
> Best regards
> Michael
>
>

--001a11348be85747d80509cb823b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m on a telechat now, but on one point - I&#39;m not =
asking about 1200, I&#39;m asking whether the word &quot;save&quot; is supp=
osed to be &quot;safe&quot;!<div><br></div><div>Spencer</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Dec 9, 2014 at 10=
:48 AM, Michael Tuexen <span dir=3D"ltr">&lt;<a href=3D"mailto:tuexen@fh-mu=
enster.de" target=3D"_blank">tuexen@fh-muenster.de</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">On 08 Dec 2014, at 22:44, =
Spencer Dawkins &lt;<a href=3D"mailto:spencerdawkins@gmail.com">spencerdawk=
ins@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Dear Authors,<br>
&gt;<br>
&gt; I had a small number of comments, mostly but not entirely at nit level=
, on this draft. I suspect that you would see them again from other ADs and=
 from review teams.<br>
</span>Hi Spencer,<br>
<br>
thanks for the comments. See my replies inline.<br>
<span class=3D"">&gt;<br>
&gt; Would you like to respin before Last Call?<br>
</span>Sure. This makes things simple, I think and will make Gorry happy, w=
ho suggested already<br>
a text change...<br>
<br>
Best regards<br>
Michael<br>
<span class=3D"">&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; -- my notes<br>
&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 3.=C2=A0 Encapsulation and Decapsulation Procedure<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 When an SCTP packet is provided to the DTLS layer, the co=
mplete SCTP<br>
&gt;=C2=A0 =C2=A0 packet, consisting of the SCTP common header and a number=
 of SCTP<br>
&gt;=C2=A0 =C2=A0 chunks, MUST be handled as the payload of the application=
 layer<br>
&gt;=C2=A0 =C2=A0 protocol of DTLS.=C2=A0 When the DTLS layer has processed=
 a DTLS record<br>
&gt;=C2=A0 =C2=A0 containing a message of the application layer protocol, t=
he payload<br>
&gt;=C2=A0 =C2=A0 MUST be given up to the SCTP layer.=C2=A0 The SCTP layer =
expects an SCTP<br>
&gt;=C2=A0 =C2=A0 common header followed by a number of SCTP chunks.<br>
&gt;<br>
&gt; I don&#39;t read the MUSTs as 2119 MUSTs. You&#39;re just describing f=
unctionality. &quot;is handled&quot; and &quot;is given up to&quot; (which =
I might suggest saying as &quot;is passed to&quot;) are probably more appro=
priate.<br>
</span>OK, changed. I think there was a comment requesting some normative l=
anguage in the part<br>
of the document describing the actual encap/decaps, that is why the MUST we=
nt in. But<br>
if you think this is not necessary, I take them out.<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 In this text:<br>
&gt;<br>
&gt; 5.=C2=A0 DTLS Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer and =
IPv4 is used<br>
&gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementation SH=
OULD allow<br>
&gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4 pack=
et is sent<br>
&gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If contro=
lling the DF bit is<br>
&gt;=C2=A0 =C2=A0 not possible, for example due to implementation restricti=
ons, a safe<br>
&gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP stack.=
=C2=A0 It is<br>
&gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200 byte=
s.=C2=A0 Please<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0^^^^ is this &quot;safe&quot;?<br>
</span>This is what the WG thinks is save. We discussed this also with memb=
ers<br>
of the RTCWeb WG. Do you think that we should use a different value? If yes=
,<br>
which one? The motivation was based on the value for IPv6, and then taking<=
br>
into account some more bytes for headers... and we ended up with 1200.<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be able to=
 reassemble<br>
&gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 bytes.<b=
r>
&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 5.=C2=A0 DTLS Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer and =
IPv4 is used<br>
&gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementation SH=
OULD allow<br>
&gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4 pack=
et is sent<br>
&gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If contro=
lling the DF bit is<br>
&gt;=C2=A0 =C2=A0 not possible, for example due to implementation restricti=
ons, a safe<br>
&gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP stack.=
=C2=A0 It is<br>
&gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200 byte=
s.=C2=A0 Please<br>
&gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be able to=
 reassemble<br>
&gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 bytes.<b=
r>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^^^^<br>
&gt; I&#39;m not sure you need to say &quot;reassembled size of&quot;, but =
if you don&#39;t just delete this text, I&#39;d suggest &quot;able to reass=
emble fragmented IP packets up to 576 bytes in length&quot;.<br>
</span>Taken.<br>
<span class=3D"">&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 6.5.=C2=A0 Partial Reliability Extension<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Partial reliability as defined in [RFC3758] can be used i=
n<br>
&gt;=C2=A0 =C2=A0 combination with DTLS encapsulation.=C2=A0 It is also pos=
sible to use<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^<br>
&gt;=C2=A0 =C2=A0 additional PR-SCTP policies.<br>
&gt;<br>
&gt; Is there a reference you could provide for implementers? Perhaps to dr=
aft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but please =
note my use of future tense in 6.7 comment ...<br>
</span>Changed to<br>
<span class=3D"">It is also possible to use<br>
</span>additional PR-SCTP policies, for example the ones defined in<br>
&lt;xref target=3D&#39;I-D.ietf-tsvwg-sctp-prpolicies&#39;/&gt;.&lt;/t&gt;<=
br>
<span class=3D"">&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 6.7.=C2=A0 Interleaving of Large User Messages<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 SCTP as defined in [RFC4960] does not support the interle=
aving of<br>
&gt;=C2=A0 =C2=A0 large user messages that need to be fragmented and reasse=
mbled by the<br>
&gt;=C2=A0 =C2=A0 SCTP layer.=C2=A0 The protocol extension defined in<br>
&gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and=
 can be used<br>
&gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
&gt;<br>
&gt; I think I understand why you have <a href=3D"https://datatracker.ietf.=
org/doc/draft-ietf-tsvwg-sctp-ndata/" target=3D"_blank">https://datatracker=
.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/</a> listed as Informational, but=
 it feels like it&#39;s on the edge of being Normative, or at least impleme=
nters are encouraged to support this extension now. Is this important enoug=
h to need to be said in this specification? If so, would it be correct to s=
ay this?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The protocol extension being defined in<br>
&gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitatio=
n and could be used<br>
&gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
</span>I just want to say that the extension defined in I-D.ietf-tsvwg-sctp=
-ndata (whatever RFC it will be)<br>
can be used with DTLS encaps. For RTCWeb it will be used (it is mandatory t=
o implement), but there<br>
might be other use cases where this extension is not necessary.<br>
Since I&#39;m not sure I got the point you want to make, please let me know=
 if my intention is now<br>
clearer and which text you prefer to express this.<br>
<br>
Best regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Michael<br>
<br>
</font></span></blockquote></div><br></div>

--001a11348be85747d80509cb823b--


From nobody Tue Dec  9 10:17:16 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8408E1A1A39 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 10:17:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 0gija5qZCMDf for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 10:17:12 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68EAF1A07BD for <tsvwg@ietf.org>; Tue,  9 Dec 2014 10:17:12 -0800 (PST)
Received: from [10.225.7.42] (unknown [194.95.73.101]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BD4F71C0B4606; Tue,  9 Dec 2014 19:17:10 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAKKJt-c162EB7A6TkmPv11rJ2phe6ek+JYOFQRnfc8e7rTxNXA@mail.gmail.com>
Date: Tue, 9 Dec 2014 19:17:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <12DD1850-5914-4CA5-B155-58E543AEC743@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de> <CAKKJt-c162EB7A6TkmPv11rJ2phe6ek+JYOFQRnfc8e7rTxNXA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_uE_00OjPNw59xvanRT3UVzg3nY
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 18:17:14 -0000

On 09 Dec 2014, at 18:02, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:

> I'm on a telechat now, but on one point - I'm not asking about 1200, =
I'm asking whether the word "save" is supposed to be "safe"!
Got it. It is "safe". My typo.

Best regards
Michael
>=20
> Spencer
>=20
> On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com> =
wrote:
>=20
> > Dear Authors,
> >
> > I had a small number of comments, mostly but not entirely at nit =
level, on this draft. I suspect that you would see them again from other =
ADs and from review teams.
> Hi Spencer,
>=20
> thanks for the comments. See my replies inline.
> >
> > Would you like to respin before Last Call?
> Sure. This makes things simple, I think and will make Gorry happy, who =
suggested already
> a text change...
>=20
> Best regards
> Michael
> >
> > Spencer
> >
> > -- my notes
> >
> > In this text:
> >
> > 3.  Encapsulation and Decapsulation Procedure
> >
> >    When an SCTP packet is provided to the DTLS layer, the complete =
SCTP
> >    packet, consisting of the SCTP common header and a number of SCTP
> >    chunks, MUST be handled as the payload of the application layer
> >    protocol of DTLS.  When the DTLS layer has processed a DTLS =
record
> >    containing a message of the application layer protocol, the =
payload
> >    MUST be given up to the SCTP layer.  The SCTP layer expects an =
SCTP
> >    common header followed by a number of SCTP chunks.
> >
> > I don't read the MUSTs as 2119 MUSTs. You're just describing =
functionality. "is handled" and "is given up to" (which I might suggest =
saying as "is passed to") are probably more appropriate.
> OK, changed. I think there was a comment requesting some normative =
language in the part
> of the document describing the actual encap/decaps, that is why the =
MUST went in. But
> if you think this is not necessary, I take them out.
> >
> >    In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
> >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit =
is
> >    not possible, for example due to implementation restrictions, a =
safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> >                         ^^^^ is this "safe"?
> This is what the WG thinks is save. We discussed this also with =
members
> of the RTCWeb WG. Do you think that we should use a different value? =
If yes,
> which one? The motivation was based on the value for IPv6, and then =
taking
> into account some more bytes for headers... and we ended up with 1200.
> >
> >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >
> > In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
> >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit =
is
> >    not possible, for example due to implementation restrictions, a =
safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >                             ^^^^^^^^^^^^^^^^^^^
> > I'm not sure you need to say "reassembled size of", but if you don't =
just delete this text, I'd suggest "able to reassemble fragmented IP =
packets up to 576 bytes in length".
> Taken.
> >
> > In this text:
> >
> > 6.5.  Partial Reliability Extension
> >
> >    Partial reliability as defined in [RFC3758] can be used in
> >    combination with DTLS encapsulation.  It is also possible to use
> >                                             ^^^^^^^^^^^^^^^^
> >    additional PR-SCTP policies.
> >
> > Is there a reference you could provide for implementers? Perhaps to =
draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but =
please note my use of future tense in 6.7 comment ...
> Changed to
> It is also possible to use
> additional PR-SCTP policies, for example the ones defined in
> <xref target=3D'I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
> >
> > In this text:
> >
> > 6.7.  Interleaving of Large User Messages
> >
> >    SCTP as defined in [RFC4960] does not support the interleaving of
> >    large user messages that need to be fragmented and reassembled by =
the
> >    SCTP layer.  The protocol extension defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be =
used
> >    with DTLS encapsulation.
> >
> > I think I understand why you have =
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as =
Informational, but it feels like it's on the edge of being Normative, or =
at least implementers are encouraged to support this extension now. Is =
this important enough to need to be said in this specification? If so, =
would it be correct to say this?
> >
> >    The protocol extension being defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and =
could be used
> >    with DTLS encapsulation.
> I just want to say that the extension defined in =
I-D.ietf-tsvwg-sctp-ndata (whatever RFC it will be)
> can be used with DTLS encaps. For RTCWeb it will be used (it is =
mandatory to implement), but there
> might be other use cases where this extension is not necessary.
> Since I'm not sure I got the point you want to make, please let me =
know if my intention is now
> clearer and which text you prefer to express this.
>=20
> Best regards
> Michael
>=20
>=20


From nobody Tue Dec  9 15:01:56 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B5F1A8863; Tue,  9 Dec 2014 15:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 4zkmicQ5-kOG; Tue,  9 Dec 2014 15:01:49 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 248551A0074; Tue,  9 Dec 2014 15:01:48 -0800 (PST)
Received: from [192.168.1.200] (p508F26DA.dip0.t-ipconnect.de [80.143.38.218]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 350B01C103E7D; Wed, 10 Dec 2014 00:01:46 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 10 Dec 2014 00:01:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/GS3ixsCxee8k-9u9PwmrE-behKc
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 23:01:51 -0000

On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com> =
wrote:

> I have reviewed this document as part of the Operational directorate's =
ongoing effort to review all IETF documents being processed by the IESG. =
 These comments  were written primarily for the benefit of the =
operational area directors.  Document editors and WG chairs should treat =
these comments just like any other last call comments.
Hi Dan,

thank you very much for your review. Please see my questions and =
comments in-line.

Best regards
Michael
>=20
> =20
> Summary: Ready with issues
> =20
> Document Ready, but Operational and Management considerations missing.
> =20
> As the Abstract says:
> =20
>    This document defines two additional policies for the Partial
>    Reliability Extension of the Stream Control Transmission Protocol
>    (PR-SCTP) allowing to limit the number of retransmissions or to
>    prioritize user messages for more efficient send buffer usage.
> Although this document defines an extension of an existing protocol, =
there are no explicit considerations about operations and management. =
The OPS and Transport ADs should decide whether this is an issue to be =
addressed before the document is approved.
> =20
> Specifically, following the checklists in RFC 5707, Appendix A:
> =20
> -       Deployment is not discussed, although there is text that says =
that the Limited Retransmissions Policy can be used with data channels =
in the WebRTC protocol stack, and that the Priority Policy can be used =
in the IPFIX protocol stack
The introduction says, that "The decision to abandon a user message is =
sender side only". So for
deploying the additional policies you need to implement it at the sender =
side.
> -       Installation and initial setup is not discussed
We normally don't discuss the installation of the OS (assuming that the =
SCTP stack is part
of the kernel, which is the case for Linux, FreeBSD and Solaris) or how =
to install applications
(assuming that the transport stack is part of the application, which is =
the case for
browsers like Firefox, Chrome and Opera).
> -       Migration Path does not seem to apply
Migrating from what? You can just use an implementation at the sender =
side and you can
operate with every receiver implemening RFC 3758.
> -       There is information about RFC 3758 being mandatory to =
implement in order to implement these extensions
> -       The impact on the network operation is not discussed =
explicitly
In the security considerations section we say that the SCTP association =
using this extension
is not more aggressive than one not using the extension.
> -       There are no explicit suggestions about verifying correct =
operations, although one can understand that the socket options =
described in sections 4.3, 4.4, 4.5 are useful to determine stream =
specific status, association specific status, and to get and set the =
PR-SCTP support
Are you suggesting to specify test cases? At least this is not common =
right now in transport area
although it would make sense in my opinion...
> -       Interoperability does not seem to apply excepting the =
requirement to implement RFC 3758
And that is all what is needed...
> -       There is no information about faults or threshold conditions =
to be reported
Not sure what you are expecting here.
> -       Configuration is not discussed, it may not apply, but it would =
be good to state this
Well, configuration is described in detail in the socket API section. =
This is how you
configure the transport stack.
> -       There are no manageability considerations of any kind
Isn't the socket API what you use to manage the transport stack? Or are =
you referring to MIB stuff?
> =20
> One terminology issue is worth being considered: The document speaks =
about two additional policies for PR-SCTP. However, the RFC defining =
PR-SCTP (RFC 3758) does not use the term policy at all. Timed =
Reliability which in this document is called a =91policy=92 is described =
in RFC 3758 as a =91service to upper layer=92. It would be good to =
either align terminology, or to explain that the term policy used here =
corresponds to the =91service=92 described in RFC 3758.
That is a good catch. Terminology has evolved over time.

I changed in the introduction

The decision to abandon a user message
is sender side only and the exact condition is called a PR-SCTP policy.

to

The decision to abandon a user message
is sender side only and the exact condition is called a PR-SCTP policy
(<xref target=3D'RFC3758'/> refers to them as 'PR-SCTP Services').
> =20
> Regards,
> =20
> Dan


From nobody Tue Dec  9 19:51:38 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB8D41A1EF6 for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 19:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 s3aFi_9Uhhqz for <tsvwg@ietfa.amsl.com>; Tue,  9 Dec 2014 19:51:34 -0800 (PST)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77D2F1A895A for <tsvwg@ietf.org>; Tue,  9 Dec 2014 19:51:33 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id 10so1651053lbg.29 for <tsvwg@ietf.org>; Tue, 09 Dec 2014 19:51:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=L4pU0/i2IQyiL/zfPzprUXt3hXR1Lc3N04E1xAhJXPM=; b=mmiUhmz/02YyxormRAr5l4rIKBA16BSCtWcHgAWz35IaL2V4rWeCq1iJvTuwW+xLwA nxAOdmKBpsGBOeP5hrtWZDKi7Mq1d5uUEKHb/tmW0jm0RsvfZI60ksDlyHSPauAF0r8P CMxkQSLnDRoTbNaF6jy9gEYzmJja9GZQoHA4vhxNyBhlfbghUVUUih13fbum/ZeFc2tg BS+f6L2YtgOOXnp2OwPC3sa+sKX8VZqzkJ59+bEaMf9Xzq6N8NOKVRZlN3fAg7Z7VZMY m6CntRAfWsW8a0NPV++AJcD657Mj9BwTc2oB2o8MoEfosl2UzLXEbm9Mm2mFjyNuHxY9 0UaQ==
MIME-Version: 1.0
X-Received: by 10.152.115.172 with SMTP id jp12mr1727670lab.33.1418183491717;  Tue, 09 Dec 2014 19:51:31 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Tue, 9 Dec 2014 19:51:31 -0800 (PST)
In-Reply-To: <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de>
Date: Tue, 9 Dec 2014 21:51:31 -0600
Message-ID: <CAKKJt-ft8jzCju1ZfSfURrm7QD6xecobUUUDQtavgOtaQrcsCw@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=001a11c3547e400dae0509d493c8
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/LdyafdGgrDU62y7a_oB9gpbIoyw
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 03:51:38 -0000

--001a11c3547e400dae0509d493c8
Content-Type: text/plain; charset=UTF-8

Now that the telechat is settling down ...

On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com>
> wrote:
>
> > Dear Authors,
> >
> > I had a small number of comments, mostly but not entirely at nit level,
> on this draft. I suspect that you would see them again from other ADs and
> from review teams.
> Hi Spencer,
>
> thanks for the comments. See my replies inline.
> >
> > Would you like to respin before Last Call?
> Sure. This makes things simple, I think and will make Gorry happy, who
> suggested already
> a text change...
>
> Best regards
> Michael
> >
> > Spencer
> >
> > -- my notes
> >
> > In this text:
> >
> > 3.  Encapsulation and Decapsulation Procedure
> >
> >    When an SCTP packet is provided to the DTLS layer, the complete SCTP
> >    packet, consisting of the SCTP common header and a number of SCTP
> >    chunks, MUST be handled as the payload of the application layer
> >    protocol of DTLS.  When the DTLS layer has processed a DTLS record
> >    containing a message of the application layer protocol, the payload
> >    MUST be given up to the SCTP layer.  The SCTP layer expects an SCTP
> >    common header followed by a number of SCTP chunks.
> >
> > I don't read the MUSTs as 2119 MUSTs. You're just describing
> functionality. "is handled" and "is given up to" (which I might suggest
> saying as "is passed to") are probably more appropriate.
> OK, changed. I think there was a comment requesting some normative
> language in the part
> of the document describing the actual encap/decaps, that is why the MUST
> went in. But
> if you think this is not necessary, I take them out.
>

I think they are probably attractive nuisances that would get at least
Comments if not Discusses from a couple of other ADs (names on request).


> >
> >    In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is used
> >    as the network layer protocol, the DTLS implementation SHOULD allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> >    not possible, for example due to implementation restrictions, a safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> >                         ^^^^ is this "safe"?
>

We talked about this one :-)


> This is what the WG thinks is save. We discussed this also with members
> of the RTCWeb WG. Do you think that we should use a different value? If
> yes,
> which one? The motivation was based on the value for IPv6, and then taking
> into account some more bytes for headers... and we ended up with 1200.
> >
> >    note that [RFC1122] only requires end hosts to be able to reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >
> > In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is used
> >    as the network layer protocol, the DTLS implementation SHOULD allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> >    not possible, for example due to implementation restrictions, a safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> >    note that [RFC1122] only requires end hosts to be able to reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >                             ^^^^^^^^^^^^^^^^^^^
> > I'm not sure you need to say "reassembled size of", but if you don't
> just delete this text, I'd suggest "able to reassemble fragmented IP
> packets up to 576 bytes in length".
> Taken.
> >
> > In this text:
> >
> > 6.5.  Partial Reliability Extension
> >
> >    Partial reliability as defined in [RFC3758] can be used in
> >    combination with DTLS encapsulation.  It is also possible to use
> >                                             ^^^^^^^^^^^^^^^^
> >    additional PR-SCTP policies.
> >
> > Is there a reference you could provide for implementers? Perhaps to
> draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but
> please note my use of future tense in 6.7 comment ...
> Changed to
> It is also possible to use
> additional PR-SCTP policies, for example the ones defined in
> <xref target='I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
>

Sounds perfect. And that pushes me to get the write-up done for that draft
:-)


> >
> > In this text:
> >
> > 6.7.  Interleaving of Large User Messages
> >
> >    SCTP as defined in [RFC4960] does not support the interleaving of
> >    large user messages that need to be fragmented and reassembled by the
> >    SCTP layer.  The protocol extension defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be used
> >    with DTLS encapsulation.
> >
> > I think I understand why you have
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as
> Informational, but it feels like it's on the edge of being Normative, or at
> least implementers are encouraged to support this extension now. Is this
> important enough to need to be said in this specification? If so, would it
> be correct to say this?
> >
> >    The protocol extension being defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and could
> be used
> >    with DTLS encapsulation.
> I just want to say that the extension defined in I-D.ietf-tsvwg-sctp-ndata
> (whatever RFC it will be)
> can be used with DTLS encaps. For RTCWeb it will be used (it is mandatory
> to implement), but there
> might be other use cases where this extension is not necessary.
> Since I'm not sure I got the point you want to make, please let me know if
> my intention is now
> clearer and which text you prefer to express this.


I'm mostly wondering if other ADs will think this reference is normative -
if it is, you'd be REF-HOLD on a draft that's still "draft exists".

If saying that is important enough to hold this draft, please do the right
thing.

I was attempting to provide text that didn't tie as closely to this
specific draft.

There's at least a 70-percent chance that no one will push on this - as I
said, if it's normative, it's barely normative. You can leave it this way,
just be thinking about what your response will be if someone asks.

But please, do the right thing ;-)


> Best regards
> Michael
>

Thanks for your quick responses on this. It's always a pleasure to work on
stuff that's still in short-term memory ...

Spencer

--001a11c3547e400dae0509d493c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Now that the telechat is settling down ...<div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Tue, Dec 9, 2014 at 10:48 AM, =
Michael Tuexen <span dir=3D"ltr">&lt;<a href=3D"mailto:tuexen@fh-muenster.d=
e" target=3D"_blank">tuexen@fh-muenster.de</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><span class=3D"">On 08 Dec 2014, at 22:44, Spencer =
Dawkins &lt;<a href=3D"mailto:spencerdawkins@gmail.com">spencerdawkins@gmai=
l.com</a>&gt; wrote:<br>
<br>
&gt; Dear Authors,<br>
&gt;<br>
&gt; I had a small number of comments, mostly but not entirely at nit level=
, on this draft. I suspect that you would see them again from other ADs and=
 from review teams.<br>
</span>Hi Spencer,<br>
<br>
thanks for the comments. See my replies inline.<br>
<span class=3D"">&gt;<br>
&gt; Would you like to respin before Last Call?<br>
</span>Sure. This makes things simple, I think and will make Gorry happy, w=
ho suggested already<br>
a text change...<br>
<br>
Best regards<br>
Michael<br>
<span class=3D"">&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; -- my notes<br>
&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 3.=C2=A0 Encapsulation and Decapsulation Procedure<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 When an SCTP packet is provided to the DTLS layer, the co=
mplete SCTP<br>
&gt;=C2=A0 =C2=A0 packet, consisting of the SCTP common header and a number=
 of SCTP<br>
&gt;=C2=A0 =C2=A0 chunks, MUST be handled as the payload of the application=
 layer<br>
&gt;=C2=A0 =C2=A0 protocol of DTLS.=C2=A0 When the DTLS layer has processed=
 a DTLS record<br>
&gt;=C2=A0 =C2=A0 containing a message of the application layer protocol, t=
he payload<br>
&gt;=C2=A0 =C2=A0 MUST be given up to the SCTP layer.=C2=A0 The SCTP layer =
expects an SCTP<br>
&gt;=C2=A0 =C2=A0 common header followed by a number of SCTP chunks.<br>
&gt;<br>
&gt; I don&#39;t read the MUSTs as 2119 MUSTs. You&#39;re just describing f=
unctionality. &quot;is handled&quot; and &quot;is given up to&quot; (which =
I might suggest saying as &quot;is passed to&quot;) are probably more appro=
priate.<br>
</span>OK, changed. I think there was a comment requesting some normative l=
anguage in the part<br>
of the document describing the actual encap/decaps, that is why the MUST we=
nt in. But<br>
if you think this is not necessary, I take them out.<br></blockquote><div><=
br></div><div>I think they are probably attractive nuisances that would get=
 at least Comments if not Discusses from a couple of other ADs (names on re=
quest).=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 In this text:<br>
&gt;<br>
&gt; 5.=C2=A0 DTLS Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer and =
IPv4 is used<br>
&gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementation SH=
OULD allow<br>
&gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4 pack=
et is sent<br>
&gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If contro=
lling the DF bit is<br>
&gt;=C2=A0 =C2=A0 not possible, for example due to implementation restricti=
ons, a safe<br>
&gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP stack.=
=C2=A0 It is<br>
&gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200 byte=
s.=C2=A0 Please<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0^^^^ is this &quot;safe&quot;?<br></span></blockquote><=
div><br></div><div>We talked about this one :-)</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><span class=3D"">
</span>This is what the WG thinks is save. We discussed this also with memb=
ers<br>
of the RTCWeb WG. Do you think that we should use a different value? If yes=
,<br>
which one? The motivation was based on the value for IPv6, and then taking<=
br>
into account some more bytes for headers... and we ended up with 1200.<br>
<span class=3D"">&gt;<br>
&gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be able to=
 reassemble<br>
&gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 bytes.<b=
r>
&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 5.=C2=A0 DTLS Considerations<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer and =
IPv4 is used<br>
&gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementation SH=
OULD allow<br>
&gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4 pack=
et is sent<br>
&gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If contro=
lling the DF bit is<br>
&gt;=C2=A0 =C2=A0 not possible, for example due to implementation restricti=
ons, a safe<br>
&gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP stack.=
=C2=A0 It is<br>
&gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200 byte=
s.=C2=A0 Please<br>
&gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be able to=
 reassemble<br>
&gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 bytes.<b=
r>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^^^^<br>
&gt; I&#39;m not sure you need to say &quot;reassembled size of&quot;, but =
if you don&#39;t just delete this text, I&#39;d suggest &quot;able to reass=
emble fragmented IP packets up to 576 bytes in length&quot;.<br>
</span>Taken.<br>
<span class=3D"">&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 6.5.=C2=A0 Partial Reliability Extension<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Partial reliability as defined in [RFC3758] can be used i=
n<br>
&gt;=C2=A0 =C2=A0 combination with DTLS encapsulation.=C2=A0 It is also pos=
sible to use<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^<br>
&gt;=C2=A0 =C2=A0 additional PR-SCTP policies.<br>
&gt;<br>
&gt; Is there a reference you could provide for implementers? Perhaps to dr=
aft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but please =
note my use of future tense in 6.7 comment ...<br>
</span>Changed to<br>
<span class=3D"">It is also possible to use<br>
</span>additional PR-SCTP policies, for example the ones defined in<br>
&lt;xref target=3D&#39;I-D.ietf-tsvwg-sctp-prpolicies&#39;/&gt;.&lt;/t&gt;<=
br></blockquote><div><br></div><div>Sounds perfect. And that pushes me to g=
et the write-up done for that draft :-)</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<span class=3D"">&gt;<br>
&gt; In this text:<br>
&gt;<br>
&gt; 6.7.=C2=A0 Interleaving of Large User Messages<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 SCTP as defined in [RFC4960] does not support the interle=
aving of<br>
&gt;=C2=A0 =C2=A0 large user messages that need to be fragmented and reasse=
mbled by the<br>
&gt;=C2=A0 =C2=A0 SCTP layer.=C2=A0 The protocol extension defined in<br>
&gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and=
 can be used<br>
&gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
&gt;<br>
&gt; I think I understand why you have <a href=3D"https://datatracker.ietf.=
org/doc/draft-ietf-tsvwg-sctp-ndata/" target=3D"_blank">https://datatracker=
.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/</a> listed as Informational, but=
 it feels like it&#39;s on the edge of being Normative, or at least impleme=
nters are encouraged to support this extension now. Is this important enoug=
h to need to be said in this specification? If so, would it be correct to s=
ay this?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 The protocol extension being defined in<br>
&gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitatio=
n and could be used<br>
&gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
</span>I just want to say that the extension defined in I-D.ietf-tsvwg-sctp=
-ndata (whatever RFC it will be)<br>
can be used with DTLS encaps. For RTCWeb it will be used (it is mandatory t=
o implement), but there<br>
might be other use cases where this extension is not necessary.<br>
Since I&#39;m not sure I got the point you want to make, please let me know=
 if my intention is now<br>
clearer and which text you prefer to express this.</blockquote><div><br></d=
iv><div>I&#39;m mostly wondering if other ADs will think this reference is =
normative - if it is, you&#39;d be REF-HOLD on a draft that&#39;s still &qu=
ot;draft exists&quot;.=C2=A0<br><br>If saying that is important enough to h=
old this draft, please do the right thing.</div><div><br></div><div>I was a=
ttempting to provide text that didn&#39;t tie as closely to this specific d=
raft.</div><div><br></div><div>There&#39;s at least a 70-percent chance tha=
t no one will push on this - as I said, if it&#39;s normative, it&#39;s bar=
ely normative. You can leave it this way, just be thinking about what your =
response will be if someone asks.</div><div><br></div><div>But please, do t=
he right thing ;-)</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Bes=
t regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Michael<br></font></span></b=
lockquote><div><br></div><div>Thanks for your quick responses on this. It&#=
39;s always a pleasure to work on stuff that&#39;s still in short-term memo=
ry ...</div><div><br></div><div>Spencer=C2=A0</div></div></div></div>

--001a11c3547e400dae0509d493c8--


From nobody Wed Dec 10 01:33:07 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18AF1A1B80 for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 01:33:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 Hm8LxdRMasVy for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 01:32:58 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 790B31A1B5F for <tsvwg@ietf.org>; Wed, 10 Dec 2014 01:32:56 -0800 (PST)
Received: from [192.168.1.200] (p508F26DA.dip0.t-ipconnect.de [80.143.38.218]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id A54A81C104818; Wed, 10 Dec 2014 10:32:53 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAKKJt-ft8jzCju1ZfSfURrm7QD6xecobUUUDQtavgOtaQrcsCw@mail.gmail.com>
Date: Wed, 10 Dec 2014 10:32:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <537B8880-8D15-4A2D-B67E-7A4470821CD2@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de> <CAKKJt-ft8jzCju1ZfSfURrm7QD6xecobUUUDQtavgOtaQrcsCw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/4ODym6x3lD4ToVpogQhtH7XDRc8
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 09:33:04 -0000

On 10 Dec 2014, at 04:51, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:

> Now that the telechat is settling down ...
>=20
> On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com> =
wrote:
>=20
> > Dear Authors,
> >
> > I had a small number of comments, mostly but not entirely at nit =
level, on this draft. I suspect that you would see them again from other =
ADs and from review teams.
> Hi Spencer,
>=20
> thanks for the comments. See my replies inline.
> >
> > Would you like to respin before Last Call?
> Sure. This makes things simple, I think and will make Gorry happy, who =
suggested already
> a text change...
>=20
> Best regards
> Michael
> >
> > Spencer
> >
> > -- my notes
> >
> > In this text:
> >
> > 3.  Encapsulation and Decapsulation Procedure
> >
> >    When an SCTP packet is provided to the DTLS layer, the complete =
SCTP
> >    packet, consisting of the SCTP common header and a number of SCTP
> >    chunks, MUST be handled as the payload of the application layer
> >    protocol of DTLS.  When the DTLS layer has processed a DTLS =
record
> >    containing a message of the application layer protocol, the =
payload
> >    MUST be given up to the SCTP layer.  The SCTP layer expects an =
SCTP
> >    common header followed by a number of SCTP chunks.
> >
> > I don't read the MUSTs as 2119 MUSTs. You're just describing =
functionality. "is handled" and "is given up to" (which I might suggest =
saying as "is passed to") are probably more appropriate.
> OK, changed. I think there was a comment requesting some normative =
language in the part
> of the document describing the actual encap/decaps, that is why the =
MUST went in. But
> if you think this is not necessary, I take them out.
>=20
> I think they are probably attractive nuisances that would get at least =
Comments if not Discusses from a couple of other ADs (names on request).=20=

OK. Text changed as suggested.
> =20
> >
> >    In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
> >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit =
is
> >    not possible, for example due to implementation restrictions, a =
safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> >                         ^^^^ is this "safe"?
>=20
> We talked about this one :-)
> =20
> This is what the WG thinks is save. We discussed this also with =
members
> of the RTCWeb WG. Do you think that we should use a different value? =
If yes,
> which one? The motivation was based on the value for IPv6, and then =
taking
> into account some more bytes for headers... and we ended up with 1200.
> >
> >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >
> > In this text:
> >
> > 5.  DTLS Considerations
> >
> >    If path MTU discovery is performed by the SCTP layer and IPv4 is =
used
> >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> >    with the Don't Fragment (DF) bit set.  If controlling the DF bit =
is
> >    not possible, for example due to implementation restrictions, a =
safe
> >    value for the path MTU has to be used by the SCTP stack.  It is
> >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> >    fragmented IP packets of reassembled size of 576 bytes.
> >                             ^^^^^^^^^^^^^^^^^^^
> > I'm not sure you need to say "reassembled size of", but if you don't =
just delete this text, I'd suggest "able to reassemble fragmented IP =
packets up to 576 bytes in length".
> Taken.
> >
> > In this text:
> >
> > 6.5.  Partial Reliability Extension
> >
> >    Partial reliability as defined in [RFC3758] can be used in
> >    combination with DTLS encapsulation.  It is also possible to use
> >                                             ^^^^^^^^^^^^^^^^
> >    additional PR-SCTP policies.
> >
> > Is there a reference you could provide for implementers? Perhaps to =
draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but =
please note my use of future tense in 6.7 comment ...
> Changed to
> It is also possible to use
> additional PR-SCTP policies, for example the ones defined in
> <xref target=3D'I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
>=20
> Sounds perfect. And that pushes me to get the write-up done for that =
draft :-)
> =20
> >
> > In this text:
> >
> > 6.7.  Interleaving of Large User Messages
> >
> >    SCTP as defined in [RFC4960] does not support the interleaving of
> >    large user messages that need to be fragmented and reassembled by =
the
> >    SCTP layer.  The protocol extension defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be =
used
> >    with DTLS encapsulation.
> >
> > I think I understand why you have =
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as =
Informational, but it feels like it's on the edge of being Normative, or =
at least implementers are encouraged to support this extension now. Is =
this important enough to need to be said in this specification? If so, =
would it be correct to say this?
> >
> >    The protocol extension being defined in
> >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and =
could be used
> >    with DTLS encapsulation.
> I just want to say that the extension defined in =
I-D.ietf-tsvwg-sctp-ndata (whatever RFC it will be)
> can be used with DTLS encaps. For RTCWeb it will be used (it is =
mandatory to implement), but there
> might be other use cases where this extension is not necessary.
> Since I'm not sure I got the point you want to make, please let me =
know if my intention is now
> clearer and which text you prefer to express this.
>=20
> I'm mostly wondering if other ADs will think this reference is =
normative - if it is, you'd be REF-HOLD on a draft that's still "draft =
exists".=20
It is OK for me to be REF-HOLD on that ID. The same applies to the other =
documents in the reference
section.
>=20
> If saying that is important enough to hold this draft, please do the =
right thing.
OK. Let me try.
If we are ref-hold on I-D.ietf-tsvwg-sctp-ndata, everything will be fine =
after that ID turns into an RFC.
If we are not ref-hold on I-D.ietf-tsvwg-sctp-ndata, the reference will =
be to an particular version
of the ID, which is not what is intended. It is intended to refer to the =
corresponding RFC eventually.

This mean:
We either
use your language and are not REF-HOLD on I-D.ietf-tsvwg-sctp-ndata
or
keep the current wording but make sure that we are REF-HOLD on =
I-D.ietf-tsvwg-sctp-ndata.

I don't know how I can make sure that the document is REF-HOLD on =
I-D.ietf-tsvwg-sctp-ndata. I can live
with both options. Which one do you suggest?
>=20
> I was attempting to provide text that didn't tie as closely to this =
specific draft.
I think we need to be consistent. All extensions discussed in section =
6.1 to 6.7 are
referenced using non normative references. They should all handled the =
same way. So if
you want to make one normative, please do so for the others. However, =
based on the discussion
on the WG it was decided that using non-normative references is the best =
way.
>=20
> There's at least a 70-percent chance that no one will push on this - =
as I said, if it's normative, it's barely normative. You can leave it =
this way, just be thinking about what your response will be if someone =
asks.
>=20
> But please, do the right thing ;-)
> =20
> Best regards
> Michael
>=20
> Thanks for your quick responses on this. It's always a pleasure to =
work on stuff that's still in short-term memory ...
>=20
> Spencer=20


From nobody Wed Dec 10 04:23:51 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DE51A8714; Wed, 10 Dec 2014 04:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EPte9Hz7EqGG; Wed, 10 Dec 2014 04:23:41 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E31D1A1B71; Wed, 10 Dec 2014 04:23:41 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYGAHk6iFSHCzIm/2dsb2JhbABZgmQigS6zMgEBAQEBAQaYNwKBFhYBAQEBAQF8hAIBAQEBAgESKD8MBAIBCA0EBAEBAQoUCQcyFAkIAgQOBQgaiA4IAbU6ogEBAQEBAQUBAQEBAQEBAQEZhg2JHgEVETEHBoMbgRUFjCyBVoU8hEGCXIImh22DX4NubgGBAgEBHiJ+AQEB
X-IronPort-AV: E=Sophos;i="5.07,552,1413259200"; d="scan'208";a="95739328"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Dec 2014 07:23:40 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 10 Dec 2014 07:23:39 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Wed, 10 Dec 2014 13:23:38 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Thread-Topic: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
Thread-Index: AQHQFAQfYnsa0fyMxkuTKo1O1asdxJyIvJOg
Date: Wed, 10 Dec 2014 12:23:38 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de>
In-Reply-To: <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/xmgY_Eg34zexyKXvlpoZ9ws0wZY
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 12:23:48 -0000

Hi Michael,

Thank you for addressing the issues raised in the OPS-DIR review.=20

First, please see the disclaimer that I put in my review:=20

> > Although this document defines an extension of an existing protocol, th=
ere
> are no explicit considerations about operations and management. The OPS
> and Transport ADs should decide whether this is an issue to be addressed
> before the document is approved.

The OPS-DIR reviews are written to help the OPS ADs with a reading of the I=
-Ds in review from the perspective of the operators using the and deploying=
 the new protocols or extensions defined by the document. We - the reviewer=
s - believe that the operational and manageability issues are important, bu=
t it's up to the ADs to decide whether they are important enough to require=
 changes in the document, and what these changes should be.=20

More in-line.=20

Regards,

Dan


> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Wednesday, December 10, 2014 1:02 AM
> To: Romascanu, Dan (Dan)
> Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
> prpolicies.all@tools.ietf.org
> Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
>=20
> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com>
> wrote:
>=20
> > I have reviewed this document as part of the Operational directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> These comments  were written primarily for the benefit of the operational
> area directors.  Document editors and WG chairs should treat these
> comments just like any other last call comments.
> Hi Dan,
>=20
> thank you very much for your review. Please see my questions and
> comments in-line.
>=20
> Best regards
> Michael
> >
> >
> > Summary: Ready with issues
> >
> > Document Ready, but Operational and Management considerations
> missing.
> >
> > As the Abstract says:
> >
> >    This document defines two additional policies for the Partial
> >    Reliability Extension of the Stream Control Transmission Protocol
> >    (PR-SCTP) allowing to limit the number of retransmissions or to
> >    prioritize user messages for more efficient send buffer usage.
> > Although this document defines an extension of an existing protocol, th=
ere
> are no explicit considerations about operations and management. The OPS
> and Transport ADs should decide whether this is an issue to be addressed
> before the document is approved.
> >
> > Specifically, following the checklists in RFC 5707, Appendix A:
> >
> > -       Deployment is not discussed, although there is text that says t=
hat the
> Limited Retransmissions Policy can be used with data channels in the
> WebRTC protocol stack, and that the Priority Policy can be used in the IP=
FIX
> protocol stack
> The introduction says, that "The decision to abandon a user message is
> sender side only". So for deploying the additional policies you need to
> implement it at the sender side.

This is not exactly what I meant by deployment. My understanding is that th=
e policies defined in this document come to answer some specific needs of p=
rotocols like IPFIX and WebRTC. Am I correct? If I am, I would expect the p=
olicies to be deployed where these protocols run.=20

> > -       Installation and initial setup is not discussed
> We normally don't discuss the installation of the OS (assuming that the S=
CTP
> stack is part of the kernel, which is the case for Linux, FreeBSD and Sol=
aris) or
> how to install applications (assuming that the transport stack is part of=
 the
> application, which is the case for browsers like Firefox, Chrome and Oper=
a).

Thank you for the clarification. Maybe it would help writing just this - th=
e installation of the new capabilities will be part of OS upgrades.=20

> > -       Migration Path does not seem to apply
> Migrating from what? You can just use an implementation at the sender sid=
e
> and you can operate with every receiver implemening RFC 3758.

This is OK - that's what I had in mind when I said 'does not apply' - so no=
 need to do anything.=20

> > -       There is information about RFC 3758 being mandatory to implemen=
t in
> order to implement these extensions
> > -       The impact on the network operation is not discussed explicitly
> In the security considerations section we say that the SCTP association u=
sing
> this extension is not more aggressive than one not using the extension.

OK.=20

> > -       There are no explicit suggestions about verifying correct opera=
tions,
> although one can understand that the socket options described in sections
> 4.3, 4.4, 4.5 are useful to determine stream specific status, association
> specific status, and to get and set the PR-SCTP support
> Are you suggesting to specify test cases? At least this is not common rig=
ht
> now in transport area although it would make sense in my opinion...

OK

> > -       Interoperability does not seem to apply excepting the requireme=
nt to
> implement RFC 3758
> And that is all what is needed...

OK

> > -       There is no information about faults or threshold conditions to=
 be
> reported
> Not sure what you are expecting here.

Nothing - this is a point in the 5707 list which does not seem to apply.

> > -       Configuration is not discussed, it may not apply, but it would =
be good
> to state this
> Well, configuration is described in detail in the socket API section. Thi=
s is how
> you configure the transport stack.

OK

> > -       There are no manageability considerations of any kind
> Isn't the socket API what you use to manage the transport stack? Or are y=
ou
> referring to MIB stuff?

Whatever is used by operators to perform and verify installation, check beh=
avior, and troubleshoot problems.=20

> >
> > One terminology issue is worth being considered: The document speaks
> about two additional policies for PR-SCTP. However, the RFC defining PR-
> SCTP (RFC 3758) does not use the term policy at all. Timed Reliability wh=
ich in
> this document is called a 'policy' is described in RFC 3758 as a 'service=
 to
> upper layer'. It would be good to either align terminology, or to explain=
 that
> the term policy used here corresponds to the 'service' described in RFC 3=
758.
> That is a good catch. Terminology has evolved over time.
>=20
> I changed in the introduction
>=20
> The decision to abandon a user message
> is sender side only and the exact condition is called a PR-SCTP policy.
>=20
> to
>=20
> The decision to abandon a user message
> is sender side only and the exact condition is called a PR-SCTP policy (<=
xref
> target=3D'RFC3758'/> refers to them as 'PR-SCTP Services').

OK=20

> >
> > Regards,
> >
> > Dan


From nobody Wed Dec 10 04:44:03 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FC61A88C0 for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 04:44:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 HSZPBn2YpC0w for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 04:43:57 -0800 (PST)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4252E1A88D3 for <tsvwg@ietf.org>; Wed, 10 Dec 2014 04:43:57 -0800 (PST)
Received: by mail-la0-f51.google.com with SMTP id ms9so2303764lab.38 for <tsvwg@ietf.org>; Wed, 10 Dec 2014 04:43:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i6cCSxap5zLYxo3usFW2I1LdOKXVcL0u3IujW97AY7c=; b=qhYJDGyPyAu3PJb65U7hpVI3ayst2JIsQxYX52ZABJg4Cs9G1fSpGm4suGtzZUk4z6 C1UmGkikxwoR2V6JaapiFhBT8TKFgwMUT2XBVlNFbjgPScDqoi7yqfm1ub12WREeI/Ai wOw3yoiT8l5ObfXjr+/aZNiO5G2u5FTJiEIBKNUyGNoK5oSQL3gLEq0SNc6zVcHhJ2r2 SQJTpnGBilY3kmi3GTR4hvqD3UH1fKlotlOuWOCDvpJLUcQtmMcrTfO1Ru5lPKecpBeR Gd64jXvn84+kVBhbS3L017FXayoyqohxLwyXybyeJ+mrzfqnj4jA0fiLsKaZTdoM0+rD hWqQ==
MIME-Version: 1.0
X-Received: by 10.112.180.198 with SMTP id dq6mr3857010lbc.56.1418215435521; Wed, 10 Dec 2014 04:43:55 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Wed, 10 Dec 2014 04:43:55 -0800 (PST)
In-Reply-To: <537B8880-8D15-4A2D-B67E-7A4470821CD2@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de> <CAKKJt-ft8jzCju1ZfSfURrm7QD6xecobUUUDQtavgOtaQrcsCw@mail.gmail.com> <537B8880-8D15-4A2D-B67E-7A4470821CD2@fh-muenster.de>
Date: Wed, 10 Dec 2014 06:43:55 -0600
Message-ID: <CAKKJt-cfjoyQ4CLA760sHi=MiZhyu9DPxqryVuwuYTjS1JNKgw@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=001a11c26b423ff9c20509dc0336
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/2QPLwZDVH68g2PmjiOVcc9LJ_VA
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 12:44:01 -0000

--001a11c26b423ff9c20509dc0336
Content-Type: text/plain; charset=UTF-8

Hi, Michael,

On Wed, Dec 10, 2014 at 3:32 AM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> On 10 Dec 2014, at 04:51, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
> > Now that the telechat is settling down ...
> >
> > On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen <tuexen@fh-muenster.de>
> wrote:
> > On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com>
> wrote:
> >
> > > Dear Authors,
> > >
> > > I had a small number of comments, mostly but not entirely at nit
> level, on this draft. I suspect that you would see them again from other
> ADs and from review teams.
> > Hi Spencer,
> >
> > thanks for the comments. See my replies inline.
> > >
> > > Would you like to respin before Last Call?
> > Sure. This makes things simple, I think and will make Gorry happy, who
> suggested already
> > a text change...
> >
> > Best regards
> > Michael
> > >
> > > Spencer
> > >
> > > -- my notes
> > >
> > > In this text:
> > >
> > > 3.  Encapsulation and Decapsulation Procedure
> > >
> > >    When an SCTP packet is provided to the DTLS layer, the complete SCTP
> > >    packet, consisting of the SCTP common header and a number of SCTP
> > >    chunks, MUST be handled as the payload of the application layer
> > >    protocol of DTLS.  When the DTLS layer has processed a DTLS record
> > >    containing a message of the application layer protocol, the payload
> > >    MUST be given up to the SCTP layer.  The SCTP layer expects an SCTP
> > >    common header followed by a number of SCTP chunks.
> > >
> > > I don't read the MUSTs as 2119 MUSTs. You're just describing
> functionality. "is handled" and "is given up to" (which I might suggest
> saying as "is passed to") are probably more appropriate.
> > OK, changed. I think there was a comment requesting some normative
> language in the part
> > of the document describing the actual encap/decaps, that is why the MUST
> went in. But
> > if you think this is not necessary, I take them out.
> >
> > I think they are probably attractive nuisances that would get at least
> Comments if not Discusses from a couple of other ADs (names on request).
> OK. Text changed as suggested.
> >
> > >
> > >    In this text:
> > >
> > > 5.  DTLS Considerations
> > >
> > >    If path MTU discovery is performed by the SCTP layer and IPv4 is
> used
> > >    as the network layer protocol, the DTLS implementation SHOULD allow
> > >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> > >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> > >    not possible, for example due to implementation restrictions, a safe
> > >    value for the path MTU has to be used by the SCTP stack.  It is
> > >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> > >                         ^^^^ is this "safe"?
> >
> > We talked about this one :-)
> >
> > This is what the WG thinks is save. We discussed this also with members
> > of the RTCWeb WG. Do you think that we should use a different value? If
> yes,
> > which one? The motivation was based on the value for IPv6, and then
> taking
> > into account some more bytes for headers... and we ended up with 1200.
> > >
> > >    note that [RFC1122] only requires end hosts to be able to reassemble
> > >    fragmented IP packets of reassembled size of 576 bytes.
> > >
> > > In this text:
> > >
> > > 5.  DTLS Considerations
> > >
> > >    If path MTU discovery is performed by the SCTP layer and IPv4 is
> used
> > >    as the network layer protocol, the DTLS implementation SHOULD allow
> > >    the DTLS user to enforce that the corresponding IPv4 packet is sent
> > >    with the Don't Fragment (DF) bit set.  If controlling the DF bit is
> > >    not possible, for example due to implementation restrictions, a safe
> > >    value for the path MTU has to be used by the SCTP stack.  It is
> > >    RECOMMENDED that the save value does not exceed 1200 bytes.  Please
> > >    note that [RFC1122] only requires end hosts to be able to reassemble
> > >    fragmented IP packets of reassembled size of 576 bytes.
> > >                             ^^^^^^^^^^^^^^^^^^^
> > > I'm not sure you need to say "reassembled size of", but if you don't
> just delete this text, I'd suggest "able to reassemble fragmented IP
> packets up to 576 bytes in length".
> > Taken.
> > >
> > > In this text:
> > >
> > > 6.5.  Partial Reliability Extension
> > >
> > >    Partial reliability as defined in [RFC3758] can be used in
> > >    combination with DTLS encapsulation.  It is also possible to use
> > >                                             ^^^^^^^^^^^^^^^^
> > >    additional PR-SCTP policies.
> > >
> > > Is there a reference you could provide for implementers? Perhaps to
> draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but
> please note my use of future tense in 6.7 comment ...
> > Changed to
> > It is also possible to use
> > additional PR-SCTP policies, for example the ones defined in
> > <xref target='I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
> >
> > Sounds perfect. And that pushes me to get the write-up done for that
> draft :-)
> >
> > >
> > > In this text:
> > >
> > > 6.7.  Interleaving of Large User Messages
> > >
> > >    SCTP as defined in [RFC4960] does not support the interleaving of
> > >    large user messages that need to be fragmented and reassembled by
> the
> > >    SCTP layer.  The protocol extension defined in
> > >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can be
> used
> > >    with DTLS encapsulation.
> > >
> > > I think I understand why you have
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as
> Informational, but it feels like it's on the edge of being Normative, or at
> least implementers are encouraged to support this extension now. Is this
> important enough to need to be said in this specification? If so, would it
> be correct to say this?
> > >
> > >    The protocol extension being defined in
> > >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and
> could be used
> > >    with DTLS encapsulation.
> > I just want to say that the extension defined in
> I-D.ietf-tsvwg-sctp-ndata (whatever RFC it will be)
> > can be used with DTLS encaps. For RTCWeb it will be used (it is
> mandatory to implement), but there
> > might be other use cases where this extension is not necessary.
> > Since I'm not sure I got the point you want to make, please let me know
> if my intention is now
> > clearer and which text you prefer to express this.
> >
> > I'm mostly wondering if other ADs will think this reference is normative
> - if it is, you'd be REF-HOLD on a draft that's still "draft exists".
> It is OK for me to be REF-HOLD on that ID. The same applies to the other
> documents in the reference
> section.
> >
> > If saying that is important enough to hold this draft, please do the
> right thing.
> OK. Let me try.
> If we are ref-hold on I-D.ietf-tsvwg-sctp-ndata, everything will be fine
> after that ID turns into an RFC.
> If we are not ref-hold on I-D.ietf-tsvwg-sctp-ndata, the reference will be
> to an particular version
> of the ID, which is not what is intended. It is intended to refer to the
> corresponding RFC eventually.


If you are fine with REF-HOLD, there's no change required. My suggestion
would be to put in a section that's a Note to the RFC Editor, saying that
although the reference is Informative, the document should be held until
I-D.ietf-tsvwg-sctp-ndata has been approved.

I COULD include that as an RFC Editor Note in the datatracker, but putting
it in the document will make it harder to miss during approval and
publication.

I think that's all the questions we had for each other. When you submit the
next revision, I'll request Last Call for it.

And thanks for your continued good work on SCTP!

Spencer


> This mean:
> We either
> use your language and are not REF-HOLD on I-D.ietf-tsvwg-sctp-ndata
> or
> keep the current wording but make sure that we are REF-HOLD on
> I-D.ietf-tsvwg-sctp-ndata.
>
> I don't know how I can make sure that the document is REF-HOLD on
> I-D.ietf-tsvwg-sctp-ndata. I can live
> with both options. Which one do you suggest?
> >
> > I was attempting to provide text that didn't tie as closely to this
> specific draft.
> I think we need to be consistent. All extensions discussed in section 6.1
> to 6.7 are
> referenced using non normative references. They should all handled the
> same way. So if
> you want to make one normative, please do so for the others. However,
> based on the discussion
> on the WG it was decided that using non-normative references is the best
> way.
> >
> > There's at least a 70-percent chance that no one will push on this - as
> I said, if it's normative, it's barely normative. You can leave it this
> way, just be thinking about what your response will be if someone asks.
> >
> > But please, do the right thing ;-)
> >
> > Best regards
> > Michael
> >
> > Thanks for your quick responses on this. It's always a pleasure to work
> on stuff that's still in short-term memory ...
> >
> > Spencer
>
>

--001a11c26b423ff9c20509dc0336
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Michael,<div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, Dec 10, 2014 at 3:32 AM, Michael Tuexen <span dir=3D"lt=
r">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_blank">tuexen@fh=
-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(=
204,204,204);border-left-style:solid;padding-left:1ex"><div class=3D""><div=
 class=3D"h5">On 10 Dec 2014, at 04:51, Spencer Dawkins at IETF &lt;<a href=
=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a>=
&gt; wrote:<br>
<br>
&gt; Now that the telechat is settling down ...<br>
&gt;<br>
&gt; On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen &lt;<a href=3D"mailto:=
tuexen@fh-muenster.de">tuexen@fh-muenster.de</a>&gt; wrote:<br>
&gt; On 08 Dec 2014, at 22:44, Spencer Dawkins &lt;<a href=3D"mailto:spence=
rdawkins@gmail.com">spencerdawkins@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Dear Authors,<br>
&gt; &gt;<br>
&gt; &gt; I had a small number of comments, mostly but not entirely at nit =
level, on this draft. I suspect that you would see them again from other AD=
s and from review teams.<br>
&gt; Hi Spencer,<br>
&gt;<br>
&gt; thanks for the comments. See my replies inline.<br>
&gt; &gt;<br>
&gt; &gt; Would you like to respin before Last Call?<br>
&gt; Sure. This makes things simple, I think and will make Gorry happy, who=
 suggested already<br>
&gt; a text change...<br>
&gt;<br>
&gt; Best regards<br>
&gt; Michael<br>
&gt; &gt;<br>
&gt; &gt; Spencer<br>
&gt; &gt;<br>
&gt; &gt; -- my notes<br>
&gt; &gt;<br>
&gt; &gt; In this text:<br>
&gt; &gt;<br>
&gt; &gt; 3.=C2=A0 Encapsulation and Decapsulation Procedure<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 When an SCTP packet is provided to the DTLS layer, t=
he complete SCTP<br>
&gt; &gt;=C2=A0 =C2=A0 packet, consisting of the SCTP common header and a n=
umber of SCTP<br>
&gt; &gt;=C2=A0 =C2=A0 chunks, MUST be handled as the payload of the applic=
ation layer<br>
&gt; &gt;=C2=A0 =C2=A0 protocol of DTLS.=C2=A0 When the DTLS layer has proc=
essed a DTLS record<br>
&gt; &gt;=C2=A0 =C2=A0 containing a message of the application layer protoc=
ol, the payload<br>
&gt; &gt;=C2=A0 =C2=A0 MUST be given up to the SCTP layer.=C2=A0 The SCTP l=
ayer expects an SCTP<br>
&gt; &gt;=C2=A0 =C2=A0 common header followed by a number of SCTP chunks.<b=
r>
&gt; &gt;<br>
&gt; &gt; I don&#39;t read the MUSTs as 2119 MUSTs. You&#39;re just describ=
ing functionality. &quot;is handled&quot; and &quot;is given up to&quot; (w=
hich I might suggest saying as &quot;is passed to&quot;) are probably more =
appropriate.<br>
&gt; OK, changed. I think there was a comment requesting some normative lan=
guage in the part<br>
&gt; of the document describing the actual encap/decaps, that is why the MU=
ST went in. But<br>
&gt; if you think this is not necessary, I take them out.<br>
&gt;<br>
&gt; I think they are probably attractive nuisances that would get at least=
 Comments if not Discusses from a couple of other ADs (names on request).<b=
r>
</div></div>OK. Text changed as suggested.<br>
<div><div class=3D"h5">&gt;<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 In this text:<br>
&gt; &gt;<br>
&gt; &gt; 5.=C2=A0 DTLS Considerations<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer=
 and IPv4 is used<br>
&gt; &gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementati=
on SHOULD allow<br>
&gt; &gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4=
 packet is sent<br>
&gt; &gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If c=
ontrolling the DF bit is<br>
&gt; &gt;=C2=A0 =C2=A0 not possible, for example due to implementation rest=
rictions, a safe<br>
&gt; &gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP st=
ack.=C2=A0 It is<br>
&gt; &gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200=
 bytes.=C2=A0 Please<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0^^^^ is this &quot;safe&quot;?<br>
&gt;<br>
&gt; We talked about this one :-)<br>
&gt;<br>
&gt; This is what the WG thinks is save. We discussed this also with member=
s<br>
&gt; of the RTCWeb WG. Do you think that we should use a different value? I=
f yes,<br>
&gt; which one? The motivation was based on the value for IPv6, and then ta=
king<br>
&gt; into account some more bytes for headers... and we ended up with 1200.=
<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be ab=
le to reassemble<br>
&gt; &gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 byt=
es.<br>
&gt; &gt;<br>
&gt; &gt; In this text:<br>
&gt; &gt;<br>
&gt; &gt; 5.=C2=A0 DTLS Considerations<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 If path MTU discovery is performed by the SCTP layer=
 and IPv4 is used<br>
&gt; &gt;=C2=A0 =C2=A0 as the network layer protocol, the DTLS implementati=
on SHOULD allow<br>
&gt; &gt;=C2=A0 =C2=A0 the DTLS user to enforce that the corresponding IPv4=
 packet is sent<br>
&gt; &gt;=C2=A0 =C2=A0 with the Don&#39;t Fragment (DF) bit set.=C2=A0 If c=
ontrolling the DF bit is<br>
&gt; &gt;=C2=A0 =C2=A0 not possible, for example due to implementation rest=
rictions, a safe<br>
&gt; &gt;=C2=A0 =C2=A0 value for the path MTU has to be used by the SCTP st=
ack.=C2=A0 It is<br>
&gt; &gt;=C2=A0 =C2=A0 RECOMMENDED that the save value does not exceed 1200=
 bytes.=C2=A0 Please<br>
&gt; &gt;=C2=A0 =C2=A0 note that [RFC1122] only requires end hosts to be ab=
le to reassemble<br>
&gt; &gt;=C2=A0 =C2=A0 fragmented IP packets of reassembled size of 576 byt=
es.<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^^^^<br>
&gt; &gt; I&#39;m not sure you need to say &quot;reassembled size of&quot;,=
 but if you don&#39;t just delete this text, I&#39;d suggest &quot;able to =
reassemble fragmented IP packets up to 576 bytes in length&quot;.<br>
&gt; Taken.<br>
&gt; &gt;<br>
&gt; &gt; In this text:<br>
&gt; &gt;<br>
&gt; &gt; 6.5.=C2=A0 Partial Reliability Extension<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 Partial reliability as defined in [RFC3758] can be u=
sed in<br>
&gt; &gt;=C2=A0 =C2=A0 combination with DTLS encapsulation.=C2=A0 It is als=
o possible to use<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0^^^^^^^^^^^^^^^^<br>
&gt; &gt;=C2=A0 =C2=A0 additional PR-SCTP policies.<br>
&gt; &gt;<br>
&gt; &gt; Is there a reference you could provide for implementers? Perhaps =
to draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but pl=
ease note my use of future tense in 6.7 comment ...<br>
&gt; Changed to<br>
&gt; It is also possible to use<br>
&gt; additional PR-SCTP policies, for example the ones defined in<br>
&gt; &lt;xref target=3D&#39;I-D.ietf-tsvwg-sctp-prpolicies&#39;/&gt;.&lt;/t=
&gt;<br>
&gt;<br>
&gt; Sounds perfect. And that pushes me to get the write-up done for that d=
raft :-)<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; In this text:<br>
&gt; &gt;<br>
&gt; &gt; 6.7.=C2=A0 Interleaving of Large User Messages<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 SCTP as defined in [RFC4960] does not support the in=
terleaving of<br>
&gt; &gt;=C2=A0 =C2=A0 large user messages that need to be fragmented and r=
eassembled by the<br>
&gt; &gt;=C2=A0 =C2=A0 SCTP layer.=C2=A0 The protocol extension defined in<=
br>
&gt; &gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitatio=
n and can be used<br>
&gt; &gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
&gt; &gt;<br>
&gt; &gt; I think I understand why you have <a href=3D"https://datatracker.=
ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/" target=3D"_blank">https://datatr=
acker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/</a> listed as Informational=
, but it feels like it&#39;s on the edge of being Normative, or at least im=
plementers are encouraged to support this extension now. Is this important =
enough to need to be said in this specification? If so, would it be correct=
 to say this?<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 The protocol extension being defined in<br>
&gt; &gt;=C2=A0 =C2=A0 [I-D.ietf-tsvwg-sctp-ndata] would overcome this limi=
tation and could be used<br>
&gt; &gt;=C2=A0 =C2=A0 with DTLS encapsulation.<br>
&gt; I just want to say that the extension defined in I-D.ietf-tsvwg-sctp-n=
data (whatever RFC it will be)<br>
&gt; can be used with DTLS encaps. For RTCWeb it will be used (it is mandat=
ory to implement), but there<br>
&gt; might be other use cases where this extension is not necessary.<br>
&gt; Since I&#39;m not sure I got the point you want to make, please let me=
 know if my intention is now<br>
&gt; clearer and which text you prefer to express this.<br>
&gt;<br>
&gt; I&#39;m mostly wondering if other ADs will think this reference is nor=
mative - if it is, you&#39;d be REF-HOLD on a draft that&#39;s still &quot;=
draft exists&quot;.<br>
</div></div>It is OK for me to be REF-HOLD on that ID. The same applies to =
the other documents in the reference<br>
section.<br>
<span class=3D"">&gt;<br>
&gt; If saying that is important enough to hold this draft, please do the r=
ight thing.<br>
</span>OK. Let me try.<br>
If we are ref-hold on I-D.ietf-tsvwg-sctp-ndata, everything will be fine af=
ter that ID turns into an RFC.<br>
If we are not ref-hold on I-D.ietf-tsvwg-sctp-ndata, the reference will be =
to an particular version<br>
of the ID, which is not what is intended. It is intended to refer to the co=
rresponding RFC eventually.</blockquote><div><br></div><div>If you are fine=
 with REF-HOLD, there&#39;s no change required. My suggestion would be to p=
ut in a section that&#39;s a Note to the RFC Editor, saying that although t=
he reference is Informative, the document should be held until I-D.ietf-tsv=
wg-sctp-ndata has been approved.</div><div><br></div><div>I COULD include t=
hat as an RFC Editor Note in the datatracker, but putting it in the documen=
t will make it harder to miss during approval and publication.</div><div><b=
r></div><div>I think that&#39;s all the questions we had for each other. Wh=
en you submit the next revision, I&#39;ll request Last Call for it.</div><d=
iv><br></div><div>And thanks for your continued good work on SCTP!</div><di=
v><br></div><div>Spencer</div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-c=
olor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">This mean:<=
br>
We either<br>
use your language and are not REF-HOLD on I-D.ietf-tsvwg-sctp-ndata<br>
or<br>
keep the current wording but make sure that we are REF-HOLD on I-D.ietf-tsv=
wg-sctp-ndata.<br>
<br>
I don&#39;t know how I can make sure that the document is REF-HOLD on I-D.i=
etf-tsvwg-sctp-ndata. I can live<br>
with both options. Which one do you suggest?<br>
<span class=3D"">&gt;<br>
&gt; I was attempting to provide text that didn&#39;t tie as closely to thi=
s specific draft.<br>
</span>I think we need to be consistent. All extensions discussed in sectio=
n 6.1 to 6.7 are<br>
referenced using non normative references. They should all handled the same=
 way. So if<br>
you want to make one normative, please do so for the others. However, based=
 on the discussion<br>
on the WG it was decided that using non-normative references is the best wa=
y.<br>
<div class=3D""><div class=3D"h5">&gt;<br>
&gt; There&#39;s at least a 70-percent chance that no one will push on this=
 - as I said, if it&#39;s normative, it&#39;s barely normative. You can lea=
ve it this way, just be thinking about what your response will be if someon=
e asks.<br>
&gt;<br>
&gt; But please, do the right thing ;-)<br>
&gt;<br>
&gt; Best regards<br>
&gt; Michael<br>
&gt;<br>
&gt; Thanks for your quick responses on this. It&#39;s always a pleasure to=
 work on stuff that&#39;s still in short-term memory ...<br>
&gt;<br>
&gt; Spencer<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a11c26b423ff9c20509dc0336--


From nobody Wed Dec 10 04:57:39 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA751A8998; Wed, 10 Dec 2014 04:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 KixNs0hyQ3PD; Wed, 10 Dec 2014 04:57:34 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50A961A8978; Wed, 10 Dec 2014 04:57:33 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id gq15so2364553lab.18 for <multiple recipients>; Wed, 10 Dec 2014 04:57:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O1svPA50Miod4jp8tmVRcQ+h7URuZuJVzBqsYvDGCOs=; b=am6ZcpWupWLdPQvfUieIv/DwDbg4OsYxCypkV4H/gz9l1dA8UH4D+v+Ljzk2caWKRc 8aSqLNjNiUXw1tRL4A9SioGAPwbvTDAU3RRv3d5N5P/+34/j44nYSy6k7s20Zbd4GY4B nAiSuLWec0VE57StBORdqqzRXinIuvNiS7z5iXr/IOIebGlCc6HIyHY00HMu5AAg4NZh pemwYMSV/01T+Quj4Ii3sjlIg6HZrY4TLco5uAlOzerGzCEgPt8fKFLBMYpvY6zsnUnU +ufdtTNAH0D6aVvtNxHFGs70S6SnNN8+h0xrl1pLmlfYCEOVB7MA3AJcyAQg88psPfQV i5dw==
MIME-Version: 1.0
X-Received: by 10.112.180.198 with SMTP id dq6mr3916740lbc.56.1418216251780; Wed, 10 Dec 2014 04:57:31 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Wed, 10 Dec 2014 04:57:31 -0800 (PST)
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 10 Dec 2014 06:57:31 -0600
Message-ID: <CAKKJt-ee4eOQL64WyaGqaNmcNJ5-aV9r4z6CdGop3KFbqeO6_Q@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: multipart/alternative; boundary=001a11c26b42e6f6450509dc33f0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/JXJ3xUVDpkUmXvvceDJd4zE5nPw
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, Michael Tuexen <tuexen@fh-muenster.de>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 12:57:37 -0000

--001a11c26b42e6f6450509dc33f0
Content-Type: text/plain; charset=UTF-8

Hi, Dan,

On Wed, Dec 10, 2014 at 6:23 AM, Romascanu, Dan (Dan) <dromasca@avaya.com>
wrote:

> Hi Michael,
>
> Thank you for addressing the issues raised in the OPS-DIR review.
>
> First, please see the disclaimer that I put in my review:
>
> > > Although this document defines an extension of an existing protocol,
> there
> > are no explicit considerations about operations and management. The OPS
> > and Transport ADs should decide whether this is an issue to be addressed
> > before the document is approved.
>
> The OPS-DIR reviews are written to help the OPS ADs with a reading of the
> I-Ds in review from the perspective of the operators using the and
> deploying the new protocols or extensions defined by the document. We - the
> reviewers - believe that the operational and manageability issues are
> important, but it's up to the ADs to decide whether they are important
> enough to require changes in the document, and what these changes should be.


I should explicitly thank you for walking this doc through the OPS
checklist. I don't think I've processed a draft where that's happened, as
an AD (for whatever reason), so that's helpful. I'll follow up with the TSV
chairs, calling their attention to that - while much of the checklist
doesn't apply as much transport protocols, some of it does, and that
shouldn't startle authors, shepherds and working group chairs when an OPS
directorate reviewer notices that.

On the point you and Michael are chatting about ...


> More in-line.
>
> Regards,
>
> Dan
>
>
> > -----Original Message-----
> > From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> > Sent: Wednesday, December 10, 2014 1:02 AM
> > To: Romascanu, Dan (Dan)
> > Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
> > prpolicies.all@tools.ietf.org
> > Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
> >
> > On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com>
> > wrote:
> >
> > > I have reviewed this document as part of the Operational directorate's
> > ongoing effort to review all IETF documents being processed by the IESG.
> > These comments  were written primarily for the benefit of the operational
> > area directors.  Document editors and WG chairs should treat these
> > comments just like any other last call comments.
> > Hi Dan,
> >
> > thank you very much for your review. Please see my questions and
> > comments in-line.
> >
> > Best regards
> > Michael
> > >
> > >
> > > Summary: Ready with issues
> > >
> > > Document Ready, but Operational and Management considerations
> > missing.
> > >
> > > As the Abstract says:
> > >
> > >    This document defines two additional policies for the Partial
> > >    Reliability Extension of the Stream Control Transmission Protocol
> > >    (PR-SCTP) allowing to limit the number of retransmissions or to
> > >    prioritize user messages for more efficient send buffer usage.
> > > Although this document defines an extension of an existing protocol,
> there
> > are no explicit considerations about operations and management. The OPS
> > and Transport ADs should decide whether this is an issue to be addressed
> > before the document is approved.
> > >
> > > Specifically, following the checklists in RFC 5707, Appendix A:
> > >
> > > -       Deployment is not discussed, although there is text that says
> that the
> > Limited Retransmissions Policy can be used with data channels in the
> > WebRTC protocol stack, and that the Priority Policy can be used in the
> IPFIX
> > protocol stack
> > The introduction says, that "The decision to abandon a user message is
> > sender side only". So for deploying the additional policies you need to
> > implement it at the sender side.
>
> This is not exactly what I meant by deployment. My understanding is that
> the policies defined in this document come to answer some specific needs of
> protocols like IPFIX and WebRTC. Am I correct? If I am, I would expect the
> policies to be deployed where these protocols run.


IIUC, this is a general-purpose capability, but I'd be fine with a sentence
or two that pointed out specific needs that motivated these policies, if
the authors/shepherd/chairs agreed.


> > > -       Installation and initial setup is not discussed
> > We normally don't discuss the installation of the OS (assuming that the
> SCTP
> > stack is part of the kernel, which is the case for Linux, FreeBSD and
> Solaris) or
> > how to install applications (assuming that the transport stack is part
> of the
> > application, which is the case for browsers like Firefox, Chrome and
> Opera).
>
> Thank you for the clarification. Maybe it would help writing just this -
> the installation of the new capabilities will be part of OS upgrades.


IIUC, OS and browser upgrades (because we're seeing increasing interest in
user-space implementations of SCTP), but that could be a reasonable thing
to point out for a broader audience.

Thanks,

Spencer


> > > -       Migration Path does not seem to apply
> > Migrating from what? You can just use an implementation at the sender
> side
> > and you can operate with every receiver implemening RFC 3758.
>
> This is OK - that's what I had in mind when I said 'does not apply' - so
> no need to do anything.
>
> > > -       There is information about RFC 3758 being mandatory to
> implement in
> > order to implement these extensions
> > > -       The impact on the network operation is not discussed explicitly
> > In the security considerations section we say that the SCTP association
> using
> > this extension is not more aggressive than one not using the extension.
>
> OK.
>
> > > -       There are no explicit suggestions about verifying correct
> operations,
> > although one can understand that the socket options described in sections
> > 4.3, 4.4, 4.5 are useful to determine stream specific status, association
> > specific status, and to get and set the PR-SCTP support
> > Are you suggesting to specify test cases? At least this is not common
> right
> > now in transport area although it would make sense in my opinion...
>
> OK
>
> > > -       Interoperability does not seem to apply excepting the
> requirement to
> > implement RFC 3758
> > And that is all what is needed...
>
> OK
>
> > > -       There is no information about faults or threshold conditions
> to be
> > reported
> > Not sure what you are expecting here.
>
> Nothing - this is a point in the 5707 list which does not seem to apply.
>
> > > -       Configuration is not discussed, it may not apply, but it would
> be good
> > to state this
> > Well, configuration is described in detail in the socket API section.
> This is how
> > you configure the transport stack.
>
> OK
>
> > > -       There are no manageability considerations of any kind
> > Isn't the socket API what you use to manage the transport stack? Or are
> you
> > referring to MIB stuff?
>
> Whatever is used by operators to perform and verify installation, check
> behavior, and troubleshoot problems.
>
> > >
> > > One terminology issue is worth being considered: The document speaks
> > about two additional policies for PR-SCTP. However, the RFC defining PR-
> > SCTP (RFC 3758) does not use the term policy at all. Timed Reliability
> which in
> > this document is called a 'policy' is described in RFC 3758 as a
> 'service to
> > upper layer'. It would be good to either align terminology, or to
> explain that
> > the term policy used here corresponds to the 'service' described in RFC
> 3758.
> > That is a good catch. Terminology has evolved over time.
> >
> > I changed in the introduction
> >
> > The decision to abandon a user message
> > is sender side only and the exact condition is called a PR-SCTP policy.
> >
> > to
> >
> > The decision to abandon a user message
> > is sender side only and the exact condition is called a PR-SCTP policy
> (<xref
> > target='RFC3758'/> refers to them as 'PR-SCTP Services').
>
> OK
>
> > >
> > > Regards,
> > >
> > > Dan
>
>

--001a11c26b42e6f6450509dc33f0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Dan,<div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Wed, Dec 10, 2014 at 6:23 AM, Romascanu, Dan (Dan) <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dromasca@avaya.com" target=3D"_blank">dromasca@a=
vaya.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Micha=
el,<br>
<br>
Thank you for addressing the issues raised in the OPS-DIR review.<br>
<br>
First, please see the disclaimer that I put in my review:<br>
<span class=3D""><br>
&gt; &gt; Although this document defines an extension of an existing protoc=
ol, there<br>
&gt; are no explicit considerations about operations and management. The OP=
S<br>
&gt; and Transport ADs should decide whether this is an issue to be address=
ed<br>
&gt; before the document is approved.<br>
<br>
</span>The OPS-DIR reviews are written to help the OPS ADs with a reading o=
f the I-Ds in review from the perspective of the operators using the and de=
ploying the new protocols or extensions defined by the document. We - the r=
eviewers - believe that the operational and manageability issues are import=
ant, but it&#39;s up to the ADs to decide whether they are important enough=
 to require changes in the document, and what these changes should be.</blo=
ckquote><div><br></div><div>I should explicitly thank you for walking this =
doc through the OPS checklist. I don&#39;t think I&#39;ve processed a draft=
 where that&#39;s happened, as an AD (for whatever reason), so that&#39;s h=
elpful. I&#39;ll follow up with the TSV chairs, calling their attention to =
that - while much of the checklist doesn&#39;t apply as much transport prot=
ocols, some of it does, and that shouldn&#39;t startle authors, shepherds a=
nd working group chairs when an OPS directorate reviewer notices that.</div=
><div><br></div><div>On the point you and Michael are chatting about ...</d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">More in-line.<br>
<span class=3D""><br>
Regards,<br>
<br>
Dan<br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Michael Tuexen [mailto:<a href=3D"mailto:tuexen@fh-muenster.de">=
tuexen@fh-muenster.de</a>]<br>
</span><span class=3D"">&gt; Sent: Wednesday, December 10, 2014 1:02 AM<br>
&gt; To: Romascanu, Dan (Dan)<br>
&gt; Cc: <a href=3D"mailto:ops-dir@ietf.org">ops-dir@ietf.org</a>; <a href=
=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; draft-ietf-tsvwg-sctp-<br>
&gt; <a href=3D"mailto:prpolicies.all@tools.ietf.org">prpolicies.all@tools.=
ietf.org</a><br>
&gt; Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt=
<br>
&gt;<br>
</span><div><div class=3D"h5">&gt; On 26 Nov 2014, at 13:33, Romascanu, Dan=
 (Dan) &lt;<a href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt;=
<br>
&gt; wrote:<br>
&gt;<br>
&gt; &gt; I have reviewed this document as part of the Operational director=
ate&#39;s<br>
&gt; ongoing effort to review all IETF documents being processed by the IES=
G.<br>
&gt; These comments=C2=A0 were written primarily for the benefit of the ope=
rational<br>
&gt; area directors.=C2=A0 Document editors and WG chairs should treat thes=
e<br>
&gt; comments just like any other last call comments.<br>
&gt; Hi Dan,<br>
&gt;<br>
&gt; thank you very much for your review. Please see my questions and<br>
&gt; comments in-line.<br>
&gt;<br>
&gt; Best regards<br>
&gt; Michael<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Summary: Ready with issues<br>
&gt; &gt;<br>
&gt; &gt; Document Ready, but Operational and Management considerations<br>
&gt; missing.<br>
&gt; &gt;<br>
&gt; &gt; As the Abstract says:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 This document defines two additional policies for th=
e Partial<br>
&gt; &gt;=C2=A0 =C2=A0 Reliability Extension of the Stream Control Transmis=
sion Protocol<br>
&gt; &gt;=C2=A0 =C2=A0 (PR-SCTP) allowing to limit the number of retransmis=
sions or to<br>
&gt; &gt;=C2=A0 =C2=A0 prioritize user messages for more efficient send buf=
fer usage.<br>
&gt; &gt; Although this document defines an extension of an existing protoc=
ol, there<br>
&gt; are no explicit considerations about operations and management. The OP=
S<br>
&gt; and Transport ADs should decide whether this is an issue to be address=
ed<br>
&gt; before the document is approved.<br>
&gt; &gt;<br>
&gt; &gt; Specifically, following the checklists in RFC 5707, Appendix A:<b=
r>
&gt; &gt;<br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Deployment is not discussed, although=
 there is text that says that the<br>
&gt; Limited Retransmissions Policy can be used with data channels in the<b=
r>
&gt; WebRTC protocol stack, and that the Priority Policy can be used in the=
 IPFIX<br>
&gt; protocol stack<br>
&gt; The introduction says, that &quot;The decision to abandon a user messa=
ge is<br>
&gt; sender side only&quot;. So for deploying the additional policies you n=
eed to<br>
&gt; implement it at the sender side.<br>
<br>
</div></div>This is not exactly what I meant by deployment. My understandin=
g is that the policies defined in this document come to answer some specifi=
c needs of protocols like IPFIX and WebRTC. Am I correct? If I am, I would =
expect the policies to be deployed where these protocols run.</blockquote><=
div><br></div><div>IIUC, this is a general-purpose capability, but I&#39;d =
be fine with a sentence or two that pointed out specific needs that motivat=
ed these policies, if the authors/shepherd/chairs agreed.</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; &gt; -=C2=A0 =C2=
=A0 =C2=A0 =C2=A0Installation and initial setup is not discussed<br>
&gt; We normally don&#39;t discuss the installation of the OS (assuming tha=
t the SCTP<br>
&gt; stack is part of the kernel, which is the case for Linux, FreeBSD and =
Solaris) or<br>
&gt; how to install applications (assuming that the transport stack is part=
 of the<br>
&gt; application, which is the case for browsers like Firefox, Chrome and O=
pera).<br>
<br>
</span>Thank you for the clarification. Maybe it would help writing just th=
is - the installation of the new capabilities will be part of OS upgrades.<=
/blockquote><div><br></div><div>IIUC, OS and browser upgrades (because we&#=
39;re seeing increasing interest in user-space implementations of SCTP), bu=
t that could be a reasonable thing to point out for a broader audience.</di=
v><div><br></div><div>Thanks,</div><div><br></div><div>Spencer</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; &gt; -=C2=
=A0 =C2=A0 =C2=A0 =C2=A0Migration Path does not seem to apply<br>
&gt; Migrating from what? You can just use an implementation at the sender =
side<br>
&gt; and you can operate with every receiver implemening RFC 3758.<br>
<br>
</span>This is OK - that&#39;s what I had in mind when I said &#39;does not=
 apply&#39; - so no need to do anything.<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There is information about RFC 3758 b=
eing mandatory to implement in<br>
&gt; order to implement these extensions<br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0The impact on the network operation i=
s not discussed explicitly<br>
&gt; In the security considerations section we say that the SCTP associatio=
n using<br>
&gt; this extension is not more aggressive than one not using the extension=
.<br>
<br>
</span>OK.<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There are no explicit suggestions abo=
ut verifying correct operations,<br>
&gt; although one can understand that the socket options described in secti=
ons<br>
&gt; 4.3, 4.4, 4.5 are useful to determine stream specific status, associat=
ion<br>
&gt; specific status, and to get and set the PR-SCTP support<br>
&gt; Are you suggesting to specify test cases? At least this is not common =
right<br>
&gt; now in transport area although it would make sense in my opinion...<br=
>
<br>
</span>OK<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Interoperability does not seem to app=
ly excepting the requirement to<br>
&gt; implement RFC 3758<br>
&gt; And that is all what is needed...<br>
<br>
</span>OK<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There is no information about faults =
or threshold conditions to be<br>
&gt; reported<br>
&gt; Not sure what you are expecting here.<br>
<br>
</span>Nothing - this is a point in the 5707 list which does not seem to ap=
ply.<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Configuration is not discussed, it ma=
y not apply, but it would be good<br>
&gt; to state this<br>
&gt; Well, configuration is described in detail in the socket API section. =
This is how<br>
&gt; you configure the transport stack.<br>
<br>
</span>OK<br>
<span class=3D""><br>
&gt; &gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There are no manageability considerat=
ions of any kind<br>
&gt; Isn&#39;t the socket API what you use to manage the transport stack? O=
r are you<br>
&gt; referring to MIB stuff?<br>
<br>
</span>Whatever is used by operators to perform and verify installation, ch=
eck behavior, and troubleshoot problems.<br>
<span class=3D""><br>
&gt; &gt;<br>
&gt; &gt; One terminology issue is worth being considered: The document spe=
aks<br>
&gt; about two additional policies for PR-SCTP. However, the RFC defining P=
R-<br>
&gt; SCTP (RFC 3758) does not use the term policy at all. Timed Reliability=
 which in<br>
&gt; this document is called a &#39;policy&#39; is described in RFC 3758 as=
 a &#39;service to<br>
&gt; upper layer&#39;. It would be good to either align terminology, or to =
explain that<br>
&gt; the term policy used here corresponds to the &#39;service&#39; describ=
ed in RFC 3758.<br>
&gt; That is a good catch. Terminology has evolved over time.<br>
&gt;<br>
&gt; I changed in the introduction<br>
&gt;<br>
&gt; The decision to abandon a user message<br>
&gt; is sender side only and the exact condition is called a PR-SCTP policy=
.<br>
&gt;<br>
&gt; to<br>
&gt;<br>
&gt; The decision to abandon a user message<br>
&gt; is sender side only and the exact condition is called a PR-SCTP policy=
 (&lt;xref<br>
&gt; target=3D&#39;RFC3758&#39;/&gt; refers to them as &#39;PR-SCTP Service=
s&#39;).<br>
<br>
</span>OK<br>
<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt;<br>
&gt; &gt; Dan<br>
<br>
</blockquote></div><br></div></div>

--001a11c26b42e6f6450509dc33f0--


From nobody Wed Dec 10 06:00:26 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2820C1A9008; Wed, 10 Dec 2014 06:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0Soi20SDRa3S; Wed, 10 Dec 2014 06:00:19 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61E9E1A9007; Wed, 10 Dec 2014 06:00:19 -0800 (PST)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sBADxoNO015695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Dec 2014 08:59:54 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sBADxoNO015695
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1418219994; bh=Al6dPjGrMKq2PLitxauRndXCPpk=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=P13xNw1Mp6MBGgYrCYY21u0I9U/zYmtjKAN0g9p0mzncsfA+O+69nxTqe/kLbtZhW KZHgpZcdxxhp+WRZ7LBudEZMJRG86jvWX0HRV70Rl5H9M5WRdSS//AGYwJBE8q6uI7 6F8lZLDp5x5yRSKzIXrNDtG/1Wt7O/kiUcicL7sA=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com sBADxoNO015695
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd02.lss.emc.com (RSA Interceptor); Wed, 10 Dec 2014 08:59:32 -0500
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sBADxWKs015060 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 10 Dec 2014 08:59:33 -0500
Received: from MXHUB102.corp.emc.com (10.253.58.15) by mxhub10.corp.emc.com (10.254.92.105) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 10 Dec 2014 08:59:32 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB102.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Wed, 10 Dec 2014 08:59:32 -0500
From: "Black, David" <david.black@emc.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Michael Tuexen <tuexen@fh-muenster.de>
Thread-Topic: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
Thread-Index: AQHQFHQxpTlE2VOl00+EQk2b2XR4O5yI1QxQ
Date: Wed, 10 Dec 2014 13:59:31 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362B15DE@MX104CL02.corp.emc.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.76]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/MYdzx8Dys-HRrmewo-4tX3nXzaY
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 14:00:24 -0000

As both an OPS-Dir reviewer and one of the TSVWG chairs, I appreciate this =
review
and the discussion.  As Dan observes:

> > > Although this document defines an extension of an existing protocol, =
there
> > are no explicit considerations about operations and management. The OPS
> > and Transport ADs should decide whether this is an issue to be addresse=
d
> > before the document is approved.

As part of that AD consideration, the following recent addition to the IESG
Discuss criteria (https://www.ietf.org/iesg/statement/discuss-criteria.html=
)
on protocol extensions is relevant:

   When an extension or minor update is made to an existing protocol that
   has unaddressed issues, it would not be appropriate to hold a DISCUSS
   on that document demanding that the problem in the base protocol
   specification be addressed; rather, the way to address problems of this
   sort is to update the base protocol specification. For example, a lack
   of consideration for pervasive monitoring in an existing specification
   would not justify holding a DISCUSS on the extension or minor update.

This draft is an extension to SCTP-PR, which in turn is part of SCTP.
So, concerns that apply to SCTP-PR regardless of policy or to SCTP overall
are probably out of scope for this draft.  Installation appears to be an
example, as it applies to SCTP overall, as indicated by Michael's comment:

> > > -       Installation and initial setup is not discussed
> > We normally don't discuss the installation of the OS (assuming that the=
 SCTP
> > stack is part of the kernel, which is the case for Linux, FreeBSD and S=
olaris) or
> > how to install applications (assuming that the transport stack is part =
of the
> > application, which is the case for browsers like Firefox, Chrome and Op=
era).

General SCTP installation and setup are better dealt with elsewhere, althou=
gh
I have no problem w/Spencer's suggestion of a single sentence that could no=
te
that these additional SCTP-PR policies are part of SCTP implementations tha=
t
are deployed, installed, setup and configured as part of operating systems
or browsers.

Thanks,
--David

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> Sent: Wednesday, December 10, 2014 7:24 AM
> To: Michael Tuexen
> Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
> prpolicies.all@tools.ietf.org
> Subject: RE: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
>=20
> Hi Michael,
>=20
> Thank you for addressing the issues raised in the OPS-DIR review.
>=20
> First, please see the disclaimer that I put in my review:
>=20
> > > Although this document defines an extension of an existing protocol, =
there
> > are no explicit considerations about operations and management. The OPS
> > and Transport ADs should decide whether this is an issue to be addresse=
d
> > before the document is approved.
>=20
> The OPS-DIR reviews are written to help the OPS ADs with a reading of the=
 I-Ds
> in review from the perspective of the operators using the and deploying t=
he
> new protocols or extensions defined by the document. We - the reviewers -
> believe that the operational and manageability issues are important, but =
it's
> up to the ADs to decide whether they are important enough to require chan=
ges
> in the document, and what these changes should be.
>=20
> More in-line.
>=20
> Regards,
>=20
> Dan
>=20
>=20
> > -----Original Message-----
> > From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> > Sent: Wednesday, December 10, 2014 1:02 AM
> > To: Romascanu, Dan (Dan)
> > Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
> > prpolicies.all@tools.ietf.org
> > Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
> >
> > On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com>
> > wrote:
> >
> > > I have reviewed this document as part of the Operational directorate'=
s
> > ongoing effort to review all IETF documents being processed by the IESG=
.
> > These comments  were written primarily for the benefit of the operation=
al
> > area directors.  Document editors and WG chairs should treat these
> > comments just like any other last call comments.
> > Hi Dan,
> >
> > thank you very much for your review. Please see my questions and
> > comments in-line.
> >
> > Best regards
> > Michael
> > >
> > >
> > > Summary: Ready with issues
> > >
> > > Document Ready, but Operational and Management considerations
> > missing.
> > >
> > > As the Abstract says:
> > >
> > >    This document defines two additional policies for the Partial
> > >    Reliability Extension of the Stream Control Transmission Protocol
> > >    (PR-SCTP) allowing to limit the number of retransmissions or to
> > >    prioritize user messages for more efficient send buffer usage.
> > > Although this document defines an extension of an existing protocol, =
there
> > are no explicit considerations about operations and management. The OPS
> > and Transport ADs should decide whether this is an issue to be addresse=
d
> > before the document is approved.
> > >
> > > Specifically, following the checklists in RFC 5707, Appendix A:
> > >
> > > -       Deployment is not discussed, although there is text that says=
 that the
> > Limited Retransmissions Policy can be used with data channels in the
> > WebRTC protocol stack, and that the Priority Policy can be used in the =
IPFIX
> > protocol stack
> > The introduction says, that "The decision to abandon a user message is
> > sender side only". So for deploying the additional policies you need to
> > implement it at the sender side.
>=20
> This is not exactly what I meant by deployment. My understanding is that =
the
> policies defined in this document come to answer some specific needs of
> protocols like IPFIX and WebRTC. Am I correct? If I am, I would expect th=
e
> policies to be deployed where these protocols run.
>=20
> > > -       Installation and initial setup is not discussed
> > We normally don't discuss the installation of the OS (assuming that the=
 SCTP
> > stack is part of the kernel, which is the case for Linux, FreeBSD and S=
olaris) or
> > how to install applications (assuming that the transport stack is part =
of the
> > application, which is the case for browsers like Firefox, Chrome and Op=
era).
>=20
> Thank you for the clarification. Maybe it would help writing just this - =
the
> installation of the new capabilities will be part of OS upgrades.
>=20
> > > -       Migration Path does not seem to apply
> > Migrating from what? You can just use an implementation at the sender s=
ide
> > and you can operate with every receiver implemening RFC 3758.
>=20
> This is OK - that's what I had in mind when I said 'does not apply' - so =
no
> need to do anything.
>=20
> > > -       There is information about RFC 3758 being mandatory to implem=
ent in
> > order to implement these extensions
> > > -       The impact on the network operation is not discussed explicit=
ly
> > In the security considerations section we say that the SCTP association=
 using
> > this extension is not more aggressive than one not using the extension.
>=20
> OK.
>=20
> > > -       There are no explicit suggestions about verifying correct ope=
rations,
> > although one can understand that the socket options described in sectio=
ns
> > 4.3, 4.4, 4.5 are useful to determine stream specific status, associati=
on
> > specific status, and to get and set the PR-SCTP support
> > Are you suggesting to specify test cases? At least this is not common r=
ight
> > now in transport area although it would make sense in my opinion...
>=20
> OK
>=20
> > > -       Interoperability does not seem to apply excepting the require=
ment
> to
> > implement RFC 3758
> > And that is all what is needed...
>=20
> OK
>=20
> > > -       There is no information about faults or threshold conditions =
to be reported
> > Not sure what you are expecting here.
>=20
> Nothing - this is a point in the 5707 list which does not seem to apply.
>=20
> > > -       Configuration is not discussed, it may not apply, but it woul=
d be good
> > to state this
> > Well, configuration is described in detail in the socket API section. T=
his
> is how
> > you configure the transport stack.
>=20
> OK
>=20
> > > -       There are no manageability considerations of any kind
> > Isn't the socket API what you use to manage the transport stack? Or are=
 you
> > referring to MIB stuff?
>=20
> Whatever is used by operators to perform and verify installation, check
> behavior, and troubleshoot problems.
>=20
> > >
> > > One terminology issue is worth being considered: The document speaks
> > about two additional policies for PR-SCTP. However, the RFC defining PR=
-
> > SCTP (RFC 3758) does not use the term policy at all. Timed Reliability =
which
> in
> > this document is called a 'policy' is described in RFC 3758 as a 'servi=
ce to
> > upper layer'. It would be good to either align terminology, or to expla=
in
> that
> > the term policy used here corresponds to the 'service' described in RFC
> 3758.
> > That is a good catch. Terminology has evolved over time.
> >
> > I changed in the introduction
> >
> > The decision to abandon a user message
> > is sender side only and the exact condition is called a PR-SCTP policy.
> >
> > to
> >
> > The decision to abandon a user message
> > is sender side only and the exact condition is called a PR-SCTP policy
> (<xref
> > target=3D'RFC3758'/> refers to them as 'PR-SCTP Services').
>=20
> OK
>=20
> > >
> > > Regards,
> > >
> > > Dan


From nobody Wed Dec 10 08:23:51 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6881E1A8726; Wed, 10 Dec 2014 08:23:47 -0800 (PST)
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] autolearn=ham
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 P68a5PfCj9-K; Wed, 10 Dec 2014 08:23:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABC791A86F1; Wed, 10 Dec 2014 08:23:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141210162345.24062.91686.idtracker@ietfa.amsl.com>
Date: Wed, 10 Dec 2014 08:23:45 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ImIbKXmiEI1ieoP5vaWKHZYteSQ
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-07.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 16:23:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : DTLS Encapsulation of SCTP Packets
        Authors         : Michael Tuexen
                          Randall R. Stewart
                          Randell Jesup
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-dtls-encaps-07.txt
	Pages           : 9
	Date            : 2014-12-10

Abstract:
   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol originally defined to run on top of the network protocols
   IPv4 or IPv6.  This document specifies how SCTP can be used on top of
   the Datagram Transport Layer Security (DTLS) protocol.  Using the
   encapsulation method described in this document, SCTP is agnostic
   about the protocols being used below DTLS, explicit IP addresses can
   not be used in the SCTP control chunks.  As a consequence, the SCTP
   associations are single homed.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Dec 10 08:24:52 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA60D1A8734 for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 08:24:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 cG3W5IuJVHi7 for <tsvwg@ietfa.amsl.com>; Wed, 10 Dec 2014 08:24:47 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D9591A872C for <tsvwg@ietf.org>; Wed, 10 Dec 2014 08:24:43 -0800 (PST)
Received: from [192.168.1.200] (p508F26DA.dip0.t-ipconnect.de [80.143.38.218]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 899511C104818; Wed, 10 Dec 2014 17:24:40 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <CAKKJt-cfjoyQ4CLA760sHi=MiZhyu9DPxqryVuwuYTjS1JNKgw@mail.gmail.com>
Date: Wed, 10 Dec 2014 17:24:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7EEB119-03E1-4188-B0CA-4DEC32DA2075@fh-muenster.de>
References: <CAD-KJEKXRXanDF-sYSLU1jmTCUo7TmRNtBttv3r9mU-yXmfcDA@mail.gmail.com> <6CD19CB2-9623-4FAE-BABF-EEAF1CAEBF3F@fh-muenster.de> <CAKKJt-ft8jzCju1ZfSfURrm7QD6xecobUUUDQtavgOtaQrcsCw@mail.gmail.com> <537B8880-8D15-4A2D-B67E-7A4470821CD2@fh-muenster.de> <CAKKJt-cfjoyQ4CLA760sHi=MiZhyu9DPxqryVuwuYTjS1JNKgw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/hRULj6AVoRfuGmCgD1l3p-Dyvek
Cc: Spencer Dawkins <spencerdawkins@gmail.com>, draft-ietf-tsvwg-sctp-dtls-encaps@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] AD Evaluation of draft-ietf-tsvwg-sctp-dtls-encaps
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 16:24:50 -0000

On 10 Dec 2014, at 13:43, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:

> Hi, Michael,
>=20
> On Wed, Dec 10, 2014 at 3:32 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> On 10 Dec 2014, at 04:51, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> > Now that the telechat is settling down ...
> >
> > On Tue, Dec 9, 2014 at 10:48 AM, Michael Tuexen =
<tuexen@fh-muenster.de> wrote:
> > On 08 Dec 2014, at 22:44, Spencer Dawkins <spencerdawkins@gmail.com> =
wrote:
> >
> > > Dear Authors,
> > >
> > > I had a small number of comments, mostly but not entirely at nit =
level, on this draft. I suspect that you would see them again from other =
ADs and from review teams.
> > Hi Spencer,
> >
> > thanks for the comments. See my replies inline.
> > >
> > > Would you like to respin before Last Call?
> > Sure. This makes things simple, I think and will make Gorry happy, =
who suggested already
> > a text change...
> >
> > Best regards
> > Michael
> > >
> > > Spencer
> > >
> > > -- my notes
> > >
> > > In this text:
> > >
> > > 3.  Encapsulation and Decapsulation Procedure
> > >
> > >    When an SCTP packet is provided to the DTLS layer, the complete =
SCTP
> > >    packet, consisting of the SCTP common header and a number of =
SCTP
> > >    chunks, MUST be handled as the payload of the application layer
> > >    protocol of DTLS.  When the DTLS layer has processed a DTLS =
record
> > >    containing a message of the application layer protocol, the =
payload
> > >    MUST be given up to the SCTP layer.  The SCTP layer expects an =
SCTP
> > >    common header followed by a number of SCTP chunks.
> > >
> > > I don't read the MUSTs as 2119 MUSTs. You're just describing =
functionality. "is handled" and "is given up to" (which I might suggest =
saying as "is passed to") are probably more appropriate.
> > OK, changed. I think there was a comment requesting some normative =
language in the part
> > of the document describing the actual encap/decaps, that is why the =
MUST went in. But
> > if you think this is not necessary, I take them out.
> >
> > I think they are probably attractive nuisances that would get at =
least Comments if not Discusses from a couple of other ADs (names on =
request).
> OK. Text changed as suggested.
> >
> > >
> > >    In this text:
> > >
> > > 5.  DTLS Considerations
> > >
> > >    If path MTU discovery is performed by the SCTP layer and IPv4 =
is used
> > >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> > >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> > >    with the Don't Fragment (DF) bit set.  If controlling the DF =
bit is
> > >    not possible, for example due to implementation restrictions, a =
safe
> > >    value for the path MTU has to be used by the SCTP stack.  It is
> > >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> > >                         ^^^^ is this "safe"?
> >
> > We talked about this one :-)
> >
> > This is what the WG thinks is save. We discussed this also with =
members
> > of the RTCWeb WG. Do you think that we should use a different value? =
If yes,
> > which one? The motivation was based on the value for IPv6, and then =
taking
> > into account some more bytes for headers... and we ended up with =
1200.
> > >
> > >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> > >    fragmented IP packets of reassembled size of 576 bytes.
> > >
> > > In this text:
> > >
> > > 5.  DTLS Considerations
> > >
> > >    If path MTU discovery is performed by the SCTP layer and IPv4 =
is used
> > >    as the network layer protocol, the DTLS implementation SHOULD =
allow
> > >    the DTLS user to enforce that the corresponding IPv4 packet is =
sent
> > >    with the Don't Fragment (DF) bit set.  If controlling the DF =
bit is
> > >    not possible, for example due to implementation restrictions, a =
safe
> > >    value for the path MTU has to be used by the SCTP stack.  It is
> > >    RECOMMENDED that the save value does not exceed 1200 bytes.  =
Please
> > >    note that [RFC1122] only requires end hosts to be able to =
reassemble
> > >    fragmented IP packets of reassembled size of 576 bytes.
> > >                             ^^^^^^^^^^^^^^^^^^^
> > > I'm not sure you need to say "reassembled size of", but if you =
don't just delete this text, I'd suggest "able to reassemble fragmented =
IP packets up to 576 bytes in length".
> > Taken.
> > >
> > > In this text:
> > >
> > > 6.5.  Partial Reliability Extension
> > >
> > >    Partial reliability as defined in [RFC3758] can be used in
> > >    combination with DTLS encapsulation.  It is also possible to =
use
> > >                                             ^^^^^^^^^^^^^^^^
> > >    additional PR-SCTP policies.
> > >
> > > Is there a reference you could provide for implementers? Perhaps =
to draft-ietf-tsvwg-sctp-prpolicies, also submitted for publication, but =
please note my use of future tense in 6.7 comment ...
> > Changed to
> > It is also possible to use
> > additional PR-SCTP policies, for example the ones defined in
> > <xref target=3D'I-D.ietf-tsvwg-sctp-prpolicies'/>.</t>
> >
> > Sounds perfect. And that pushes me to get the write-up done for that =
draft :-)
> >
> > >
> > > In this text:
> > >
> > > 6.7.  Interleaving of Large User Messages
> > >
> > >    SCTP as defined in [RFC4960] does not support the interleaving =
of
> > >    large user messages that need to be fragmented and reassembled =
by the
> > >    SCTP layer.  The protocol extension defined in
> > >    [I-D.ietf-tsvwg-sctp-ndata] overcomes this limitation and can =
be used
> > >    with DTLS encapsulation.
> > >
> > > I think I understand why you have =
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ listed as =
Informational, but it feels like it's on the edge of being Normative, or =
at least implementers are encouraged to support this extension now. Is =
this important enough to need to be said in this specification? If so, =
would it be correct to say this?
> > >
> > >    The protocol extension being defined in
> > >    [I-D.ietf-tsvwg-sctp-ndata] would overcome this limitation and =
could be used
> > >    with DTLS encapsulation.
> > I just want to say that the extension defined in =
I-D.ietf-tsvwg-sctp-ndata (whatever RFC it will be)
> > can be used with DTLS encaps. For RTCWeb it will be used (it is =
mandatory to implement), but there
> > might be other use cases where this extension is not necessary.
> > Since I'm not sure I got the point you want to make, please let me =
know if my intention is now
> > clearer and which text you prefer to express this.
> >
> > I'm mostly wondering if other ADs will think this reference is =
normative - if it is, you'd be REF-HOLD on a draft that's still "draft =
exists".
> It is OK for me to be REF-HOLD on that ID. The same applies to the =
other documents in the reference
> section.
> >
> > If saying that is important enough to hold this draft, please do the =
right thing.
> OK. Let me try.
> If we are ref-hold on I-D.ietf-tsvwg-sctp-ndata, everything will be =
fine after that ID turns into an RFC.
> If we are not ref-hold on I-D.ietf-tsvwg-sctp-ndata, the reference =
will be to an particular version
> of the ID, which is not what is intended. It is intended to refer to =
the corresponding RFC eventually.
>=20
> If you are fine with REF-HOLD, there's no change required. My =
suggestion would be to put in a section that's a Note to the RFC Editor, =
saying that although the reference is Informative, the document should =
be held until I-D.ietf-tsvwg-sctp-ndata has been approved.
OK. I added text for that.
>=20
> I COULD include that as an RFC Editor Note in the datatracker, but =
putting it in the document will make it harder to miss during approval =
and publication.
>=20
> I think that's all the questions we had for each other. When you =
submit the next revision, I'll request Last Call for it.
Done.
>=20
> And thanks for your continued good work on SCTP!
Thanks to you for your fast and constructive way of cooperation!

Best regards
Michael
>=20
> Spencer
> =20
> This mean:
> We either
> use your language and are not REF-HOLD on I-D.ietf-tsvwg-sctp-ndata
> or
> keep the current wording but make sure that we are REF-HOLD on =
I-D.ietf-tsvwg-sctp-ndata.
>=20
> I don't know how I can make sure that the document is REF-HOLD on =
I-D.ietf-tsvwg-sctp-ndata. I can live
> with both options. Which one do you suggest?
> >
> > I was attempting to provide text that didn't tie as closely to this =
specific draft.
> I think we need to be consistent. All extensions discussed in section =
6.1 to 6.7 are
> referenced using non normative references. They should all handled the =
same way. So if
> you want to make one normative, please do so for the others. However, =
based on the discussion
> on the WG it was decided that using non-normative references is the =
best way.
> >
> > There's at least a 70-percent chance that no one will push on this - =
as I said, if it's normative, it's barely normative. You can leave it =
this way, just be thinking about what your response will be if someone =
asks.
> >
> > But please, do the right thing ;-)
> >
> > Best regards
> > Michael
> >
> > Thanks for your quick responses on this. It's always a pleasure to =
work on stuff that's still in short-term memory ...
> >
> > Spencer
>=20
>=20


From nobody Wed Dec 10 09:04:12 2014
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D437D1A1B71; Wed, 10 Dec 2014 09:04:08 -0800 (PST)
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] autolearn=ham
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 XLgt_5nK3cN8; Wed, 10 Dec 2014 09:04:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC2D1A0047; Wed, 10 Dec 2014 09:04:07 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20141210170407.14042.51693.idtracker@ietfa.amsl.com>
Date: Wed, 10 Dec 2014 09:04:07 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/EyQB-mwe3tTvYN5nV5Wb9re1xqY
Cc: tsvwg@ietf.org
Subject: [tsvwg] Last Call: <draft-ietf-tsvwg-sctp-dtls-encaps-07.txt> (DTLS Encapsulation of SCTP Packets) to Proposed Standard
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 17:04:09 -0000

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'DTLS Encapsulation of SCTP Packets'
  <draft-ietf-tsvwg-sctp-dtls-encaps-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-12-24. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The Stream Control Transmission Protocol (SCTP) is a transport
   protocol originally defined to run on top of the network protocols
   IPv4 or IPv6.  This document specifies how SCTP can be used on top of
   the Datagram Transport Layer Security (DTLS) protocol.  Using the
   encapsulation method described in this document, SCTP is agnostic
   about the protocols being used below DTLS, explicit IP addresses can
   not be used in the SCTP control chunks.  As a consequence, the SCTP
   associations are single homed.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Wed Dec 10 12:53:05 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB8271A1A93; Wed, 10 Dec 2014 12:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 7CHBblSuF2lR; Wed, 10 Dec 2014 12:52:54 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 416961A6F2B; Wed, 10 Dec 2014 12:52:54 -0800 (PST)
Received: from [192.168.1.200] (p508F38DF.dip0.t-ipconnect.de [80.143.56.223]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 8D6721C1622D0; Wed, 10 Dec 2014 21:52:51 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
Date: Wed, 10 Dec 2014 21:52:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Lr3jmRInyq3QLRw-kfuTcFJMGwQ
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 20:52:57 -0000

On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan) <dromasca@avaya.com> =
wrote:

> Hi Michael,
>=20
> Thank you for addressing the issues raised in the OPS-DIR review.=20
>=20
> First, please see the disclaimer that I put in my review:=20
>=20
>>> Although this document defines an extension of an existing protocol, =
there
>> are no explicit considerations about operations and management. The =
OPS
>> and Transport ADs should decide whether this is an issue to be =
addressed
>> before the document is approved.
>=20
> The OPS-DIR reviews are written to help the OPS ADs with a reading of =
the I-Ds in review from the perspective of the operators using the and =
deploying the new protocols or extensions defined by the document. We - =
the reviewers - believe that the operational and manageability issues =
are important, but it's up to the ADs to decide whether they are =
important enough to require changes in the document, and what these =
changes should be.=20
Hi Dan,

understood. But I want to understand your points and possibly address =
them...
>=20
> More in-line.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Wednesday, December 10, 2014 1:02 AM
>> To: Romascanu, Dan (Dan)
>> Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
>> prpolicies.all@tools.ietf.org
>> Subject: Re: OPS-DIR review of =
draft-ietf-tsvwg-sctp-prpolicies-05.txt
>>=20
>> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com>
>> wrote:
>>=20
>>> I have reviewed this document as part of the Operational =
directorate's
>> ongoing effort to review all IETF documents being processed by the =
IESG.
>> These comments  were written primarily for the benefit of the =
operational
>> area directors.  Document editors and WG chairs should treat these
>> comments just like any other last call comments.
>> Hi Dan,
>>=20
>> thank you very much for your review. Please see my questions and
>> comments in-line.
>>=20
>> Best regards
>> Michael
>>>=20
>>>=20
>>> Summary: Ready with issues
>>>=20
>>> Document Ready, but Operational and Management considerations
>> missing.
>>>=20
>>> As the Abstract says:
>>>=20
>>>   This document defines two additional policies for the Partial
>>>   Reliability Extension of the Stream Control Transmission Protocol
>>>   (PR-SCTP) allowing to limit the number of retransmissions or to
>>>   prioritize user messages for more efficient send buffer usage.
>>> Although this document defines an extension of an existing protocol, =
there
>> are no explicit considerations about operations and management. The =
OPS
>> and Transport ADs should decide whether this is an issue to be =
addressed
>> before the document is approved.
>>>=20
>>> Specifically, following the checklists in RFC 5707, Appendix A:
>>>=20
>>> -       Deployment is not discussed, although there is text that =
says that the
>> Limited Retransmissions Policy can be used with data channels in the
>> WebRTC protocol stack, and that the Priority Policy can be used in =
the IPFIX
>> protocol stack
>> The introduction says, that "The decision to abandon a user message =
is
>> sender side only". So for deploying the additional policies you need =
to
>> implement it at the sender side.
>=20
> This is not exactly what I meant by deployment. My understanding is =
that the policies defined in this document come to answer some specific =
needs of protocols like IPFIX and WebRTC. Am I correct? If I am, I would =
expect the policies to be deployed where these protocols run.=20
For IPFIX some of this is discussed in
https://tools.ietf.org/html/rfc7011#section-10.2
For RTCWeb is is discussed in
=
https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1
Please note that the policies defined here are of general use. So the =
description
how to use it will be in the documents describing the use cases.
>=20
>>> -       Installation and initial setup is not discussed
>> We normally don't discuss the installation of the OS (assuming that =
the SCTP
>> stack is part of the kernel, which is the case for Linux, FreeBSD and =
Solaris) or
>> how to install applications (assuming that the transport stack is =
part of the
>> application, which is the case for browsers like Firefox, Chrome and =
Opera).
>=20
> Thank you for the clarification. Maybe it would help writing just this =
- the installation of the new capabilities will be part of OS upgrades.=20=

... if you use a stack provided by the kernel. If the stack is provided =
by
an application, you need to install the application.
So it comes down to: You need to install the software which contains the =
SCTP stack you are using.
For me, this is obvious. So I'm hesitating to add this. It would be a =
sentence which
you can copy to almost every SCTP (or TCP) specification.
>=20
>>> -       Migration Path does not seem to apply
>> Migrating from what? You can just use an implementation at the sender =
side
>> and you can operate with every receiver implemening RFC 3758.
>=20
> This is OK - that's what I had in mind when I said 'does not apply' - =
so no need to do anything.=20
>=20
>>> -       There is information about RFC 3758 being mandatory to =
implement in
>> order to implement these extensions
>>> -       The impact on the network operation is not discussed =
explicitly
>> In the security considerations section we say that the SCTP =
association using
>> this extension is not more aggressive than one not using the =
extension.
>=20
> OK.=20
>=20
>>> -       There are no explicit suggestions about verifying correct =
operations,
>> although one can understand that the socket options described in =
sections
>> 4.3, 4.4, 4.5 are useful to determine stream specific status, =
association
>> specific status, and to get and set the PR-SCTP support
>> Are you suggesting to specify test cases? At least this is not common =
right
>> now in transport area although it would make sense in my opinion...
>=20
> OK
>=20
>>> -       Interoperability does not seem to apply excepting the =
requirement to
>> implement RFC 3758
>> And that is all what is needed...
>=20
> OK
>=20
>>> -       There is no information about faults or threshold conditions =
to be
>> reported
>> Not sure what you are expecting here.
>=20
> Nothing - this is a point in the 5707 list which does not seem to =
apply.
>=20
>>> -       Configuration is not discussed, it may not apply, but it =
would be good
>> to state this
>> Well, configuration is described in detail in the socket API section. =
This is how
>> you configure the transport stack.
>=20
> OK
>=20
>>> -       There are no manageability considerations of any kind
>> Isn't the socket API what you use to manage the transport stack? Or =
are you
>> referring to MIB stuff?
>=20
> Whatever is used by operators to perform and verify installation, =
check behavior, and troubleshoot problems.=20
Ahh, OK. I don't think an operator would use the socket API for that.
If you want to test you transport stack you need to have tests and a =
test tool
for running these tests. Up to now, the IETF (at least the transport =
area)
hasn't specified tests. Personally, I would really love to do it and =
think
that it is very important. But I think this is a decision not limited to =
this particular
document, but to (transport) protocols in general. So I leave it up to =
the ADs...
>=20
>>>=20
>>> One terminology issue is worth being considered: The document speaks
>> about two additional policies for PR-SCTP. However, the RFC defining =
PR-
>> SCTP (RFC 3758) does not use the term policy at all. Timed =
Reliability which in
>> this document is called a 'policy' is described in RFC 3758 as a =
'service to
>> upper layer'. It would be good to either align terminology, or to =
explain that
>> the term policy used here corresponds to the 'service' described in =
RFC 3758.
>> That is a good catch. Terminology has evolved over time.
>>=20
>> I changed in the introduction
>>=20
>> The decision to abandon a user message
>> is sender side only and the exact condition is called a PR-SCTP =
policy.
>>=20
>> to
>>=20
>> The decision to abandon a user message
>> is sender side only and the exact condition is called a PR-SCTP =
policy (<xref
>> target=3D'RFC3758'/> refers to them as 'PR-SCTP Services').
>=20
> OK=20
>=20
>>>=20
>>> Regards,
>>>=20
>>> Dan
>=20
>=20


From nobody Wed Dec 10 14:09:58 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35C6A1A8A55; Wed, 10 Dec 2014 14:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 Rte_6LOX_mPo; Wed, 10 Dec 2014 14:09:45 -0800 (PST)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 257661A89E1; Wed, 10 Dec 2014 14:09:45 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id gm9so3202860lab.26 for <multiple recipients>; Wed, 10 Dec 2014 14:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6OVkczcbvhW0HsdvpUwX1cH0Yrxmzik9VhDWeODfbj0=; b=VwJ56hP0vFtB058YT4ZEf0myHJt3mCwHWqHb7usCkeTw9E5D8whExkpDjKhgYXqmLs BjZHppXwPtZp3Dm7ec6OBFvrILD3BmxWQJeDT2ekbmLeDlHR0hoTLT+eASNajN6HWR3G YUdu7i9iD2OwvoozOGODcgidHCI4QCtryPjTPQ0hxL+p81bunAzgd7NOmhRX79whu2ws 9h1YkTynsaQET1zAl87bStRQKKBPyb0I9/MHFwYtX1pv3qcGI3zWOGnJd9K/BQAUx/Fb rslAntWVNNBwkhyGzEqlaMH5oRaT/c5t48R7wHNEhickq8Th6nY0JpRX9k19dAQqkuXA MU0A==
MIME-Version: 1.0
X-Received: by 10.112.138.137 with SMTP id qq9mr6368815lbb.80.1418249383643; Wed, 10 Dec 2014 14:09:43 -0800 (PST)
Received: by 10.152.185.195 with HTTP; Wed, 10 Dec 2014 14:09:43 -0800 (PST)
In-Reply-To: <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com> <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de>
Date: Wed, 10 Dec 2014 16:09:43 -0600
Message-ID: <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Michael Tuexen <tuexen@fh-muenster.de>
Content-Type: multipart/alternative; boundary=089e0112cc54b70df40509e3eaa1
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Eq958VopMNzdK9XRTBc1Dg_EnbI
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 22:09:50 -0000

--089e0112cc54b70df40509e3eaa1
Content-Type: text/plain; charset=UTF-8

>From at least one AD :-)

On Wed, Dec 10, 2014 at 2:52 PM, Michael Tuexen <tuexen@fh-muenster.de>
wrote:

> On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:
>
> > Hi Michael,
> >
> > Thank you for addressing the issues raised in the OPS-DIR review.
> >
> > First, please see the disclaimer that I put in my review:
> >
> >>> Although this document defines an extension of an existing protocol,
> there
> >> are no explicit considerations about operations and management. The OPS
> >> and Transport ADs should decide whether this is an issue to be addressed
> >> before the document is approved.
> >
> > The OPS-DIR reviews are written to help the OPS ADs with a reading of
> the I-Ds in review from the perspective of the operators using the and
> deploying the new protocols or extensions defined by the document. We - the
> reviewers - believe that the operational and manageability issues are
> important, but it's up to the ADs to decide whether they are important
> enough to require changes in the document, and what these changes should be.
> Hi Dan,
>
> understood. But I want to understand your points and possibly address
> them...
> >
> > More in-line.
> >
> > Regards,
> >
> > Dan
> >
> >
> >> -----Original Message-----
> >> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >> Sent: Wednesday, December 10, 2014 1:02 AM
> >> To: Romascanu, Dan (Dan)
> >> Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
> >> prpolicies.all@tools.ietf.org
> >> Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
> >>
> >> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) <dromasca@avaya.com>
> >> wrote:
> >>
> >>> I have reviewed this document as part of the Operational directorate's
> >> ongoing effort to review all IETF documents being processed by the IESG.
> >> These comments  were written primarily for the benefit of the
> operational
> >> area directors.  Document editors and WG chairs should treat these
> >> comments just like any other last call comments.
> >> Hi Dan,
> >>
> >> thank you very much for your review. Please see my questions and
> >> comments in-line.
> >>
> >> Best regards
> >> Michael
> >>>
> >>>
> >>> Summary: Ready with issues
> >>>
> >>> Document Ready, but Operational and Management considerations
> >> missing.
> >>>
> >>> As the Abstract says:
> >>>
> >>>   This document defines two additional policies for the Partial
> >>>   Reliability Extension of the Stream Control Transmission Protocol
> >>>   (PR-SCTP) allowing to limit the number of retransmissions or to
> >>>   prioritize user messages for more efficient send buffer usage.
> >>> Although this document defines an extension of an existing protocol,
> there
> >> are no explicit considerations about operations and management. The OPS
> >> and Transport ADs should decide whether this is an issue to be addressed
> >> before the document is approved.
> >>>
> >>> Specifically, following the checklists in RFC 5707, Appendix A:
> >>>
> >>> -       Deployment is not discussed, although there is text that says
> that the
> >> Limited Retransmissions Policy can be used with data channels in the
> >> WebRTC protocol stack, and that the Priority Policy can be used in the
> IPFIX
> >> protocol stack
> >> The introduction says, that "The decision to abandon a user message is
> >> sender side only". So for deploying the additional policies you need to
> >> implement it at the sender side.
> >
> > This is not exactly what I meant by deployment. My understanding is that
> the policies defined in this document come to answer some specific needs of
> protocols like IPFIX and WebRTC. Am I correct? If I am, I would expect the
> policies to be deployed where these protocols run.
> For IPFIX some of this is discussed in
> https://tools.ietf.org/html/rfc7011#section-10.2
> For RTCWeb is is discussed in
> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1
> Please note that the policies defined here are of general use. So the
> description
> how to use it will be in the documents describing the use cases.
> >
> >>> -       Installation and initial setup is not discussed
> >> We normally don't discuss the installation of the OS (assuming that the
> SCTP
> >> stack is part of the kernel, which is the case for Linux, FreeBSD and
> Solaris) or
> >> how to install applications (assuming that the transport stack is part
> of the
> >> application, which is the case for browsers like Firefox, Chrome and
> Opera).
> >
> > Thank you for the clarification. Maybe it would help writing just this -
> the installation of the new capabilities will be part of OS upgrades.
> ... if you use a stack provided by the kernel. If the stack is provided by
> an application, you need to install the application.
> So it comes down to: You need to install the software which contains the
> SCTP stack you are using.
> For me, this is obvious. So I'm hesitating to add this. It would be a
> sentence which
> you can copy to almost every SCTP (or TCP) specification.
> >
> >>> -       Migration Path does not seem to apply
> >> Migrating from what? You can just use an implementation at the sender
> side
> >> and you can operate with every receiver implemening RFC 3758.
> >
> > This is OK - that's what I had in mind when I said 'does not apply' - so
> no need to do anything.
> >
> >>> -       There is information about RFC 3758 being mandatory to
> implement in
> >> order to implement these extensions
> >>> -       The impact on the network operation is not discussed explicitly
> >> In the security considerations section we say that the SCTP association
> using
> >> this extension is not more aggressive than one not using the extension.
> >
> > OK.
> >
> >>> -       There are no explicit suggestions about verifying correct
> operations,
> >> although one can understand that the socket options described in
> sections
> >> 4.3, 4.4, 4.5 are useful to determine stream specific status,
> association
> >> specific status, and to get and set the PR-SCTP support
> >> Are you suggesting to specify test cases? At least this is not common
> right
> >> now in transport area although it would make sense in my opinion...
> >
> > OK
> >
> >>> -       Interoperability does not seem to apply excepting the
> requirement to
> >> implement RFC 3758
> >> And that is all what is needed...
> >
> > OK
> >
> >>> -       There is no information about faults or threshold conditions
> to be
> >> reported
> >> Not sure what you are expecting here.
> >
> > Nothing - this is a point in the 5707 list which does not seem to apply.
> >
> >>> -       Configuration is not discussed, it may not apply, but it would
> be good
> >> to state this
> >> Well, configuration is described in detail in the socket API section.
> This is how
> >> you configure the transport stack.
> >
> > OK
> >
> >>> -       There are no manageability considerations of any kind
> >> Isn't the socket API what you use to manage the transport stack? Or are
> you
> >> referring to MIB stuff?
> >
> > Whatever is used by operators to perform and verify installation, check
> behavior, and troubleshoot problems.
> Ahh, OK. I don't think an operator would use the socket API for that.
> If you want to test you transport stack you need to have tests and a test
> tool
> for running these tests. Up to now, the IETF (at least the transport area)
> hasn't specified tests. Personally, I would really love to do it and think
> that it is very important. But I think this is a decision not limited to
> this particular
> document, but to (transport) protocols in general. So I leave it up to the
> ADs...
>
>
I'd say the question of test cases has been raised to the attention of
TSVWG (cc on this thread), and I'd be happy to consider that if they think
working on that would be a good plan, but I don't think this document needs
to wait for them to figure that out.

I'm good with Michael submitting an update addressing the comments as
discussed in this thread.

Thanks,

Spencer

--089e0112cc54b70df40509e3eaa1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">From at least one AD :-)<br><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Wed, Dec 10, 2014 at 2:52 PM, Michael Tuexen=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:tuexen@fh-muenster.de" target=3D"_=
blank">tuexen@fh-muenster.de</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border=
-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><spa=
n class=3D"">On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan) &lt;<a href=3D"=
mailto:dromasca@avaya.com">dromasca@avaya.com</a>&gt; wrote:<br>
<br>
&gt; Hi Michael,<br>
&gt;<br>
&gt; Thank you for addressing the issues raised in the OPS-DIR review.<br>
&gt;<br>
&gt; First, please see the disclaimer that I put in my review:<br>
&gt;<br>
&gt;&gt;&gt; Although this document defines an extension of an existing pro=
tocol, there<br>
&gt;&gt; are no explicit considerations about operations and management. Th=
e OPS<br>
&gt;&gt; and Transport ADs should decide whether this is an issue to be add=
ressed<br>
&gt;&gt; before the document is approved.<br>
&gt;<br>
&gt; The OPS-DIR reviews are written to help the OPS ADs with a reading of =
the I-Ds in review from the perspective of the operators using the and depl=
oying the new protocols or extensions defined by the document. We - the rev=
iewers - believe that the operational and manageability issues are importan=
t, but it&#39;s up to the ADs to decide whether they are important enough t=
o require changes in the document, and what these changes should be.<br>
</span>Hi Dan,<br>
<br>
understood. But I want to understand your points and possibly address them.=
..<br>
<div><div class=3D"h5">&gt;<br>
&gt; More in-line.<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Dan<br>
&gt;<br>
&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: Michael Tuexen [mailto:<a href=3D"mailto:tuexen@fh-muenster.=
de">tuexen@fh-muenster.de</a>]<br>
&gt;&gt; Sent: Wednesday, December 10, 2014 1:02 AM<br>
&gt;&gt; To: Romascanu, Dan (Dan)<br>
&gt;&gt; Cc: <a href=3D"mailto:ops-dir@ietf.org">ops-dir@ietf.org</a>; <a h=
ref=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; draft-ietf-tsvwg-sctp-<br=
>
&gt;&gt; <a href=3D"mailto:prpolicies.all@tools.ietf.org">prpolicies.all@to=
ols.ietf.org</a><br>
&gt;&gt; Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05=
.txt<br>
&gt;&gt;<br>
&gt;&gt; On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan) &lt;<a href=3D"mail=
to:dromasca@avaya.com">dromasca@avaya.com</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; I have reviewed this document as part of the Operational direc=
torate&#39;s<br>
&gt;&gt; ongoing effort to review all IETF documents being processed by the=
 IESG.<br>
&gt;&gt; These comments=C2=A0 were written primarily for the benefit of the=
 operational<br>
&gt;&gt; area directors.=C2=A0 Document editors and WG chairs should treat =
these<br>
&gt;&gt; comments just like any other last call comments.<br>
&gt;&gt; Hi Dan,<br>
&gt;&gt;<br>
&gt;&gt; thank you very much for your review. Please see my questions and<b=
r>
&gt;&gt; comments in-line.<br>
&gt;&gt;<br>
&gt;&gt; Best regards<br>
&gt;&gt; Michael<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Summary: Ready with issues<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Document Ready, but Operational and Management considerations<=
br>
&gt;&gt; missing.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; As the Abstract says:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0This document defines two additional policies for =
the Partial<br>
&gt;&gt;&gt;=C2=A0 =C2=A0Reliability Extension of the Stream Control Transm=
ission Protocol<br>
&gt;&gt;&gt;=C2=A0 =C2=A0(PR-SCTP) allowing to limit the number of retransm=
issions or to<br>
&gt;&gt;&gt;=C2=A0 =C2=A0prioritize user messages for more efficient send b=
uffer usage.<br>
&gt;&gt;&gt; Although this document defines an extension of an existing pro=
tocol, there<br>
&gt;&gt; are no explicit considerations about operations and management. Th=
e OPS<br>
&gt;&gt; and Transport ADs should decide whether this is an issue to be add=
ressed<br>
&gt;&gt; before the document is approved.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Specifically, following the checklists in RFC 5707, Appendix A=
:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Deployment is not discussed, altho=
ugh there is text that says that the<br>
&gt;&gt; Limited Retransmissions Policy can be used with data channels in t=
he<br>
&gt;&gt; WebRTC protocol stack, and that the Priority Policy can be used in=
 the IPFIX<br>
&gt;&gt; protocol stack<br>
&gt;&gt; The introduction says, that &quot;The decision to abandon a user m=
essage is<br>
&gt;&gt; sender side only&quot;. So for deploying the additional policies y=
ou need to<br>
&gt;&gt; implement it at the sender side.<br>
&gt;<br>
&gt; This is not exactly what I meant by deployment. My understanding is th=
at the policies defined in this document come to answer some specific needs=
 of protocols like IPFIX and WebRTC. Am I correct? If I am, I would expect =
the policies to be deployed where these protocols run.<br>
</div></div>For IPFIX some of this is discussed in<br>
<a href=3D"https://tools.ietf.org/html/rfc7011#section-10.2" target=3D"_bla=
nk">https://tools.ietf.org/html/rfc7011#section-10.2</a><br>
For RTCWeb is is discussed in<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#se=
ction-6.1" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-rtcweb-=
data-channel-12#section-6.1</a><br>
Please note that the policies defined here are of general use. So the descr=
iption<br>
how to use it will be in the documents describing the use cases.<br>
<span class=3D"">&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Installation and initial setup is =
not discussed<br>
&gt;&gt; We normally don&#39;t discuss the installation of the OS (assuming=
 that the SCTP<br>
&gt;&gt; stack is part of the kernel, which is the case for Linux, FreeBSD =
and Solaris) or<br>
&gt;&gt; how to install applications (assuming that the transport stack is =
part of the<br>
&gt;&gt; application, which is the case for browsers like Firefox, Chrome a=
nd Opera).<br>
&gt;<br>
&gt; Thank you for the clarification. Maybe it would help writing just this=
 - the installation of the new capabilities will be part of OS upgrades.<br=
>
</span>... if you use a stack provided by the kernel. If the stack is provi=
ded by<br>
an application, you need to install the application.<br>
So it comes down to: You need to install the software which contains the SC=
TP stack you are using.<br>
For me, this is obvious. So I&#39;m hesitating to add this. It would be a s=
entence which<br>
you can copy to almost every SCTP (or TCP) specification.<br>
<div><div class=3D"h5">&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Migration Path does not seem to ap=
ply<br>
&gt;&gt; Migrating from what? You can just use an implementation at the sen=
der side<br>
&gt;&gt; and you can operate with every receiver implemening RFC 3758.<br>
&gt;<br>
&gt; This is OK - that&#39;s what I had in mind when I said &#39;does not a=
pply&#39; - so no need to do anything.<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There is information about RFC 375=
8 being mandatory to implement in<br>
&gt;&gt; order to implement these extensions<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0The impact on the network operatio=
n is not discussed explicitly<br>
&gt;&gt; In the security considerations section we say that the SCTP associ=
ation using<br>
&gt;&gt; this extension is not more aggressive than one not using the exten=
sion.<br>
&gt;<br>
&gt; OK.<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There are no explicit suggestions =
about verifying correct operations,<br>
&gt;&gt; although one can understand that the socket options described in s=
ections<br>
&gt;&gt; 4.3, 4.4, 4.5 are useful to determine stream specific status, asso=
ciation<br>
&gt;&gt; specific status, and to get and set the PR-SCTP support<br>
&gt;&gt; Are you suggesting to specify test cases? At least this is not com=
mon right<br>
&gt;&gt; now in transport area although it would make sense in my opinion..=
.<br>
&gt;<br>
&gt; OK<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Interoperability does not seem to =
apply excepting the requirement to<br>
&gt;&gt; implement RFC 3758<br>
&gt;&gt; And that is all what is needed...<br>
&gt;<br>
&gt; OK<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There is no information about faul=
ts or threshold conditions to be<br>
&gt;&gt; reported<br>
&gt;&gt; Not sure what you are expecting here.<br>
&gt;<br>
&gt; Nothing - this is a point in the 5707 list which does not seem to appl=
y.<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0Configuration is not discussed, it=
 may not apply, but it would be good<br>
&gt;&gt; to state this<br>
&gt;&gt; Well, configuration is described in detail in the socket API secti=
on. This is how<br>
&gt;&gt; you configure the transport stack.<br>
&gt;<br>
&gt; OK<br>
&gt;<br>
&gt;&gt;&gt; -=C2=A0 =C2=A0 =C2=A0 =C2=A0There are no manageability conside=
rations of any kind<br>
&gt;&gt; Isn&#39;t the socket API what you use to manage the transport stac=
k? Or are you<br>
&gt;&gt; referring to MIB stuff?<br>
&gt;<br>
&gt; Whatever is used by operators to perform and verify installation, chec=
k behavior, and troubleshoot problems.<br>
</div></div>Ahh, OK. I don&#39;t think an operator would use the socket API=
 for that.<br>
If you want to test you transport stack you need to have tests and a test t=
ool<br>
for running these tests. Up to now, the IETF (at least the transport area)<=
br>
hasn&#39;t specified tests. Personally, I would really love to do it and th=
ink<br>
that it is very important. But I think this is a decision not limited to th=
is particular<br>
document, but to (transport) protocols in general. So I leave it up to the =
ADs...<br><br></blockquote><div><br></div><div>I&#39;d say=C2=A0the questio=
n of test cases=C2=A0has been raised to the attention of TSVWG (cc on this =
thread), and I&#39;d be happy to consider that if they think working on tha=
t would be a good plan, but I don&#39;t think this document needs to wait f=
or them to figure that out.</div><div><br></div><div>I&#39;m good with Mich=
ael submitting an update addressing the comments as discussed in this threa=
d.</div><div><br></div><div>Thanks,</div><div><br></div><div>Spencer</div><=
/div><br></div></div>

--089e0112cc54b70df40509e3eaa1--


From nobody Thu Dec 11 02:01:50 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C66151ACDB4 for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 02:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level: 
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 6M4mM6dN_WnN for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 02:01:40 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B401ACDA9 for <tsvwg@ietf.org>; Thu, 11 Dec 2014 02:01:39 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id sBBA1823009309; Thu, 11 Dec 2014 11:01:16 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
Date: Thu, 11 Dec 2014 11:01:15 +0100
Message-ID: <00e401d01529$6bbdfd00$4339f700$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E5_01D01531.CD83EBA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAVKKgS1VddqZ9PR8+NJ74v6qx/Sw==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/o5pfp7AoAWGSKTFiij_pL6Jhc1c
Cc: 'Gorry Fairhurst' <gorry@erg.abdn.ac.uk>, =?utf-8?Q?'David_Fl=C3=B3rez_Rodr=C3=ADguez'?= <david.florezrodriguez@telefonica.com>, =?utf-8?Q?'Manuel_N=C3=BA=C3=B1ez_Sanz'?= <manuel.nunezsanz@telefonica.com>, =?utf-8?Q?'Juan_Antonio_Castell_Luc=C3=ADa'?= <juanantonio.castelllucia@telefonica.com>, 'Gonzalo Camarillo' <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <mls.ietf@gmail.com>, 'Fernando Pascual Blanco' <fernando.pascualblanco@telefonica.com>, "'Dan Wing \(dwing\)'" <dwing@cisco.com>, "'Michael Ramalho \(mramalho\)'" <mramalho@cisco.com>
Subject: [tsvwg] New version of the TCM drafts
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 10:01:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00E5_01D01531.CD83EBA0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
We have just submitted new versions of the two TCM drafts:
=20
- Tunneling Compressing and Multiplexing (TCM) Traffic Flows. Reference =
Model. draft-saldana-tsvwg-tcmtf-08
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
=20
- Delay Limits and Multiplexing Policies to be employed with Tunneling =
Compressing and Multiplexing Traffic Flows. =
draft-suznjevic-tsvwg-mtd-tcmtf-04
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
=20
In addition, yesterday I submitted another draft about Simplemux =
(http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/), a =
multiplexing protocol simpler than PPPMux (I will send another e-mail =
explaining it).
=20
We have built an implementation of TCM over Simplemux =
(https://github.com/TCM-TF/simplemux), and we will soon report the =
results of some tests we are planning.
=20
Best regards,
=20
Jose Saldana
PS: These are some of the improvements:
- keywords have been added
    multiplexing
    header compression
    optimization
    small-packet flows
=20
- We talk about =E2=80=9CTunneling, Compressing and Multiplexing =
(TCM)=E2=80=9D instead of =E2=80=9CTunneling Compressed and Multiplexed =
Traffic Flows (TCM-TF)=E2=80=9D. It is a bit confusing if we talk about =
TCM in some places and TCM-TF in others. In addition, TCM is very easy =
to remember.
=20
- We have improved the abstract and the introduction, talking about =
=E2=80=9Coptimization=E2=80=9D, =E2=80=9Csmall-packet flows=E2=80=9D =
here and there.
=20
- We have updated the reference to COAP (it is now an RFC and it was a =
draft some months ago).
=20
- We have added a reference for supporting the statement saying that =
routers have a limit in the number of pps they can manage.
=20
- We have modified the titles of some subsections.
=20

------=_NextPart_000_00E5_01D01531.CD83EBA0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DProgId content=3DWord.Document><meta name=3DGenerator =
content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D01531.C70A34A0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'>Hi <span =
class=3DSpellE>all</span>,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>We have just submitted =
new versions of the two TCM drafts:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- Tunneling =
Compressing and Multiplexing (TCM) Traffic Flows. Reference Model. =
draft-saldana-tsvwg-tcmtf-08<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- Delay Limits and =
Multiplexing Policies to be employed with Tunneling Compressing and =
Multiplexing Traffic Flows. =
draft-suznjevic-tsvwg-mtd-tcmtf-04<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>In addition, yesterday =
I submitted another draft about <span class=3DSpellE>Simplemux</span> =
(<a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/">h=
ttp://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/</a>), a =
multiplexing protocol simpler than PPPMux (I will send another e-mail =
explaining it).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>We have built an =
implementation of TCM over <span class=3DSpellE>Simplemux</span> (<a =
href=3D"https://github.com/TCM-TF/simplemux">https://github.com/TCM-TF/si=
mplemux</a>), and we will soon report the results of some tests we are =
planning.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US;mso-fareast-language:ES;mso-=
no-proof:yes'>Jose Saldana<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>PS: These are some of =
the improvements:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- keywords have been =
added<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 =
</span>multiplexing<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 </span>header =
compression<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 =
</span>optimization<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 </span>small-packet =
flows<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We talk about =
=E2=80=9CTunneling, Compressing and Multiplexing (TCM)=E2=80=9D instead =
of =E2=80=9CTunneling Compressed and Multiplexed Traffic Flows =
(TCM-TF)=E2=80=9D. It is a bit confusing if we talk about TCM in some =
places and TCM-TF in others. In addition, TCM is very easy to =
remember.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have improved the =
abstract and the introduction, talking about =
=E2=80=9Coptimization=E2=80=9D, =E2=80=9Csmall-packet flows=E2=80=9D =
here and there.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have updated the =
reference to COAP (it is now an RFC and it was a draft some months =
ago).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have added a =
reference for supporting the statement saying that routers have a limit =
in the number of pps they can manage.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have modified the =
titles of some subsections.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></bod=
y></html>
------=_NextPart_000_00E5_01D01531.CD83EBA0--


From nobody Thu Dec 11 02:11:15 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968361ACDC4 for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 02:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 D9Ro6Mt6W-3B for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 02:11:07 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9276A1A1A73 for <tsvwg@ietf.org>; Thu, 11 Dec 2014 02:11:06 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id sBBAB2qW027608 for <tsvwg@ietf.org>; Thu, 11 Dec 2014 11:11:02 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
Date: Thu, 11 Dec 2014 11:11:09 +0100
Message-ID: <00fa01d0152a$c8f60340$5ae209c0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FB_01D01533.2ABBA3C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAVKsK/+8m9NwlIQQKdMNyO2VHjEQ==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/qEdiihPF3h1IA43Vgi9r9Ik4oSc
Subject: [tsvwg] A new draft submitted to tsvwg: Simplemux
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 10:11:13 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00FB_01D01533.2ABBA3C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,
 
This is an Internet Draft I submitted yesterday to tsvwg:
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?include_text=
1
 
Simplemux could be seen as a generic protocol for multiplexing any protocol
on any other protocol. The initial idea was: could this be used instead of
PPPMux in TCM? However, I think it may have more fields of application.
 
The idea is similar to that of PPPMux (RFC3153). However, PPP, and L2TP in
turn, are not required, thus reducing complexity:
 
| Ext hdr || Mux hdr | packet || Mux hdr | packet || ...||
 
It is different from TMux [RFC1692], because TMux  combines multiple short
transport segments, but not full packets, so it works between the same pair
of machines.  However, there are scenarios where a number of low-efficiency
flows share a common path, but they do not travel between the same pair of
machines.  
 
A "Protocol" number should be requested to IANA for saying in the external
header that Simplemux is inside. Each Mux header would include another
"Protocol" field, so it would permit the multiplexing of different packets
in the same bundle: IPv4, IPv6, ROHC, etc.
 
If you could have a look to the draft and send your comments, it would be
fine.
 
An implementation of Simplemux using IP/UDP as the multiplexing (external)
protocol and IP or ROHC as the multiplexed protocol can be found here:
https://github.com/TCM-TF/simplemux
 
 
Thanks in advance!
 
Jose
 

------=_NextPart_000_00FB_01D01533.2ABBA3C0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D01533.29664CF0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;
	mso-style-unhide:no;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Hi =
all,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>This is an Internet =
Draft I submitted yesterday to <span =
class=3DSpellE>tsvwg</span>:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?in=
clude_text=3D1">http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simpl=
emux/?include_text=3D1</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span class=3DSpellE><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'>Simplemux</span></span><spa=
n lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'> could be seen as a =
generic protocol for multiplexing any protocol on any other protocol. =
The initial idea was: could this be used instead of PPPMux in TCM? =
However, I think it may have more fields of =
application.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>The idea is similar to =
that of PPPMux (RFC3153). However, PPP, and L2TP in turn, are not =
required, thus reducing complexity:</span><span lang=3DEN-US =
style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>&nbsp;</span><span =
lang=3DEN-US style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'>| Ext<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>|| Mux<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>| packet || Mux<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>| packet || ...||</span><span =
lang=3DEN-US style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'>&nbsp;<o:p></o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>It is different from =
<span class=3DSpellE>TMux</span> [RFC1692], because <span =
class=3DSpellE>TMux</span> <span =
style=3D'mso-spacerun:yes'>&nbsp;</span>combines multiple short =
transport segments, but not full packets, so it works between the same =
pair of machines.<span style=3D'mso-spacerun:yes'>&nbsp; </span>However, =
there are scenarios where a number of low-efficiency flows share a =
common path, but they do not travel between the same pair of =
machines.<span style=3D'mso-spacerun:yes'>&nbsp; =
</span><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>A =
&#8220;Protocol&#8221; number should be requested to IANA for saying in =
the external header that <span class=3DSpellE>Simplemux</span> is =
inside. Each Mux header would include another &#8220;Protocol&#8221; =
field, so it would permit the multiplexing of different packets in the =
same bundle: IPv4, IPv6, ROHC, etc.</span><span lang=3DEN-US =
style=3D'mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>If you could have a =
look to the draft and send your comments, it would be =
fine.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>An implementation of =
<span class=3DSpellE>Simplemux</span> using IP/UDP as the multiplexing =
(external) protocol and IP or ROHC as the multiplexed protocol can be =
found here:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"https://github.com/TCM-TF/simplemux">https://github.com/TCM-TF/si=
mplemux</a><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Thanks in =
advance!<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US;mso-no-proof:yes'>Jose<o:p><=
/o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00FB_01D01533.2ABBA3C0--


From nobody Thu Dec 11 02:16:20 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55D541ACDD1; Thu, 11 Dec 2014 02:16:14 -0800 (PST)
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] autolearn=ham
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 7fU56Y7wg0zH; Thu, 11 Dec 2014 02:16:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2181A1A73; Thu, 11 Dec 2014 02:16:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141211101613.2660.87336.idtracker@ietfa.amsl.com>
Date: Thu, 11 Dec 2014 02:16:13 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/DsbDKuZWu1jVk22zqACpGjGojz0
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-prpolicies-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 10:16:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : Additional Policies for the Partial Reliability Extension of the Stream Control Transmission Protocol
        Authors         : Michael Tuexen
                          Robin Seggelmann
                          Randall R. Stewart
                          Salvatore Loreto
	Filename        : draft-ietf-tsvwg-sctp-prpolicies-06.txt
	Pages           : 10
	Date            : 2014-12-11

Abstract:
   This document defines two additional policies for the Partial
   Reliability Extension of the Stream Control Transmission Protocol
   (PR-SCTP) allowing to limit the number of retransmissions or to
   prioritize user messages for more efficient send buffer usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-prpolicies-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-prpolicies-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Dec 11 02:16:21 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D1CC1ACDE4 for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 02:16:17 -0800 (PST)
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] autolearn=ham
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 NupEP5HwhgqN; Thu, 11 Dec 2014 02:16:15 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C351ACDD9; Thu, 11 Dec 2014 02:16:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: gorry@erg.abdn.ac.uk, tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org, spencerdawkins.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141211101613.2660.26399.idtracker@ietfa.amsl.com>
Date: Thu, 11 Dec 2014 02:16:13 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/8Lqpx1vQJbLpweoqHBzb5mIc9C4
Subject: [tsvwg] New Version Notification - draft-ietf-tsvwg-sctp-prpolicies-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 10:16:17 -0000

A new version (-06) has been submitted for draft-ietf-tsvwg-sctp-prpolicies:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-prpolicies-06.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-prpolicies-06

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Thu Dec 11 02:57:48 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9041D1A878C; Thu, 11 Dec 2014 02:57:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.92
X-Spam-Level: 
X-Spam-Status: No, score=-4.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zws1wo8dSrF0; Thu, 11 Dec 2014 02:57:41 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7BB31A8725; Thu, 11 Dec 2014 02:57:40 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQHABN4iVSHCzIm/2dsb2JhbABZgkMhIlJYBIMBsCIBAQEBAQEGkjyFbwIcfhYBAQEBAQF8hAwBAQEBAgESEQpMBQcEAgEIDQQEAQEBChYHAwICAh8RFAkIAgQBDQUIGod2AwkIAQy2H4pHkGsNhVwBAQEBAQEBAQEBAQEBAQEBAQEBAQEXhXyHQoFQARURFhcEBgEGA4JfLoETBYN2igmDPoF8gUAvAYJPMIItgiaFHDqCF4M3IoFbghFuAQEBgQABAR4ifgEBAQ
X-IronPort-AV: E=Sophos; i="5.07,557,1413259200"; d="scan'208,217"; a="98655045"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 11 Dec 2014 05:57:38 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 11 Dec 2014 05:57:37 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Thu, 11 Dec 2014 11:57:36 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Michael Tuexen <tuexen@fh-muenster.de>
Thread-Topic: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
Thread-Index: AQHQFAQfYnsa0fyMxkuTKo1O1asdxJyIvJOggACBJgCAABV7gIAA5u3g
Date: Thu, 11 Dec 2014 10:57:35 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com> <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de> <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com>
In-Reply-To: <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C92B8EFAZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/qFBGOoG4t4paPfbevkxstMKiLjY
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 10:57:44 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C92B8EFAZFFEXMB04globa_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

w5ggIEknbSBnb29kIHdpdGggTWljaGFlbCBzdWJtaXR0aW5nIGFuIHVwZGF0ZSBhZGRyZXNzaW5n
IHRoZSBjb21tZW50cyBhcyBkaXNjdXNzZWQgaW4gdGhpcyB0aHJlYWQuDQoNCsOYDQoNCsOYICBU
aGFua3MsDQoNCsOYDQoNCsOYICBTcGVuY2VyDQoNCk1lIHRvby4gQ2FuIHlvdSBwbGVhc2Ugc2Vu
ZCBtZSBhIG5vdGUgd2hlbiB0aGlzIGhhcHBlbnMsIHNvIHRoYXQgSSBkbyBub3QgbWlzcyB0aGUg
dXBkYXRlPw0KDQpUaGFua3MgZm9yIGNvbnNpZGVyaW5nIG15IGNvbW1lbnRzLg0KDQpSZWdhcmRz
LA0KDQpEYW4NCg0KDQpGcm9tOiBTcGVuY2VyIERhd2tpbnMgYXQgSUVURiBbbWFpbHRvOnNwZW5j
ZXJkYXdraW5zLmlldGZAZ21haWwuY29tXQ0KU2VudDogVGh1cnNkYXksIERlY2VtYmVyIDExLCAy
MDE0IDEyOjEwIEFNDQpUbzogTWljaGFlbCBUdWV4ZW4NCkNjOiBSb21hc2NhbnUsIERhbiAoRGFu
KTsgb3BzLWRpckBpZXRmLm9yZzsgdHN2d2dAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtdHN2d2ctc2N0
cC1wcnBvbGljaWVzLmFsbEB0b29scy5pZXRmLm9yZw0KU3ViamVjdDogUmU6IE9QUy1ESVIgcmV2
aWV3IG9mIGRyYWZ0LWlldGYtdHN2d2ctc2N0cC1wcnBvbGljaWVzLTA1LnR4dA0KDQpGcm9tIGF0
IGxlYXN0IG9uZSBBRCA6LSkNCg0KT24gV2VkLCBEZWMgMTAsIDIwMTQgYXQgMjo1MiBQTSwgTWlj
aGFlbCBUdWV4ZW4gPHR1ZXhlbkBmaC1tdWVuc3Rlci5kZTxtYWlsdG86dHVleGVuQGZoLW11ZW5z
dGVyLmRlPj4gd3JvdGU6DQpPbiAxMCBEZWMgMjAxNCwgYXQgMTM6MjMsIFJvbWFzY2FudSwgRGFu
IChEYW4pIDxkcm9tYXNjYUBhdmF5YS5jb208bWFpbHRvOmRyb21hc2NhQGF2YXlhLmNvbT4+IHdy
b3RlOg0KDQo+IEhpIE1pY2hhZWwsDQo+DQo+IFRoYW5rIHlvdSBmb3IgYWRkcmVzc2luZyB0aGUg
aXNzdWVzIHJhaXNlZCBpbiB0aGUgT1BTLURJUiByZXZpZXcuDQo+DQo+IEZpcnN0LCBwbGVhc2Ug
c2VlIHRoZSBkaXNjbGFpbWVyIHRoYXQgSSBwdXQgaW4gbXkgcmV2aWV3Og0KPg0KPj4+IEFsdGhv
dWdoIHRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhbiBleHRlbnNpb24gb2YgYW4gZXhpc3RpbmcgcHJv
dG9jb2wsIHRoZXJlDQo+PiBhcmUgbm8gZXhwbGljaXQgY29uc2lkZXJhdGlvbnMgYWJvdXQgb3Bl
cmF0aW9ucyBhbmQgbWFuYWdlbWVudC4gVGhlIE9QUw0KPj4gYW5kIFRyYW5zcG9ydCBBRHMgc2hv
dWxkIGRlY2lkZSB3aGV0aGVyIHRoaXMgaXMgYW4gaXNzdWUgdG8gYmUgYWRkcmVzc2VkDQo+PiBi
ZWZvcmUgdGhlIGRvY3VtZW50IGlzIGFwcHJvdmVkLg0KPg0KPiBUaGUgT1BTLURJUiByZXZpZXdz
IGFyZSB3cml0dGVuIHRvIGhlbHAgdGhlIE9QUyBBRHMgd2l0aCBhIHJlYWRpbmcgb2YgdGhlIEkt
RHMgaW4gcmV2aWV3IGZyb20gdGhlIHBlcnNwZWN0aXZlIG9mIHRoZSBvcGVyYXRvcnMgdXNpbmcg
dGhlIGFuZCBkZXBsb3lpbmcgdGhlIG5ldyBwcm90b2NvbHMgb3IgZXh0ZW5zaW9ucyBkZWZpbmVk
IGJ5IHRoZSBkb2N1bWVudC4gV2UgLSB0aGUgcmV2aWV3ZXJzIC0gYmVsaWV2ZSB0aGF0IHRoZSBv
cGVyYXRpb25hbCBhbmQgbWFuYWdlYWJpbGl0eSBpc3N1ZXMgYXJlIGltcG9ydGFudCwgYnV0IGl0
J3MgdXAgdG8gdGhlIEFEcyB0byBkZWNpZGUgd2hldGhlciB0aGV5IGFyZSBpbXBvcnRhbnQgZW5v
dWdoIHRvIHJlcXVpcmUgY2hhbmdlcyBpbiB0aGUgZG9jdW1lbnQsIGFuZCB3aGF0IHRoZXNlIGNo
YW5nZXMgc2hvdWxkIGJlLg0KSGkgRGFuLA0KDQp1bmRlcnN0b29kLiBCdXQgSSB3YW50IHRvIHVu
ZGVyc3RhbmQgeW91ciBwb2ludHMgYW5kIHBvc3NpYmx5IGFkZHJlc3MgdGhlbS4uLg0KPg0KPiBN
b3JlIGluLWxpbmUuDQo+DQo+IFJlZ2FyZHMsDQo+DQo+IERhbg0KPg0KPg0KPj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IE1pY2hhZWwgVHVleGVuIFttYWlsdG86dHVleGVu
QGZoLW11ZW5zdGVyLmRlPG1haWx0bzp0dWV4ZW5AZmgtbXVlbnN0ZXIuZGU+XQ0KPj4gU2VudDog
V2VkbmVzZGF5LCBEZWNlbWJlciAxMCwgMjAxNCAxOjAyIEFNDQo+PiBUbzogUm9tYXNjYW51LCBE
YW4gKERhbikNCj4+IENjOiBvcHMtZGlyQGlldGYub3JnPG1haWx0bzpvcHMtZGlyQGlldGYub3Jn
PjsgdHN2d2dAaWV0Zi5vcmc8bWFpbHRvOnRzdndnQGlldGYub3JnPjsgZHJhZnQtaWV0Zi10c3Z3
Zy1zY3RwLQ0KPj4gcHJwb2xpY2llcy5hbGxAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOnBycG9saWNp
ZXMuYWxsQHRvb2xzLmlldGYub3JnPg0KPj4gU3ViamVjdDogUmU6IE9QUy1ESVIgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtdHN2d2ctc2N0cC1wcnBvbGljaWVzLTA1LnR4dA0KPj4NCj4+IE9uIDI2IE5v
diAyMDE0LCBhdCAxMzozMywgUm9tYXNjYW51LCBEYW4gKERhbikgPGRyb21hc2NhQGF2YXlhLmNv
bTxtYWlsdG86ZHJvbWFzY2FAYXZheWEuY29tPj4NCj4+IHdyb3RlOg0KPj4NCj4+PiBJIGhhdmUg
cmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBwYXJ0IG9mIHRoZSBPcGVyYXRpb25hbCBkaXJlY3Rv
cmF0ZSdzDQo+PiBvbmdvaW5nIGVmZm9ydCB0byByZXZpZXcgYWxsIElFVEYgZG9jdW1lbnRzIGJl
aW5nIHByb2Nlc3NlZCBieSB0aGUgSUVTRy4NCj4+IFRoZXNlIGNvbW1lbnRzICB3ZXJlIHdyaXR0
ZW4gcHJpbWFyaWx5IGZvciB0aGUgYmVuZWZpdCBvZiB0aGUgb3BlcmF0aW9uYWwNCj4+IGFyZWEg
ZGlyZWN0b3JzLiAgRG9jdW1lbnQgZWRpdG9ycyBhbmQgV0cgY2hhaXJzIHNob3VsZCB0cmVhdCB0
aGVzZQ0KPj4gY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMu
DQo+PiBIaSBEYW4sDQo+Pg0KPj4gdGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgeW91ciByZXZpZXcu
IFBsZWFzZSBzZWUgbXkgcXVlc3Rpb25zIGFuZA0KPj4gY29tbWVudHMgaW4tbGluZS4NCj4+DQo+
PiBCZXN0IHJlZ2FyZHMNCj4+IE1pY2hhZWwNCj4+Pg0KPj4+DQo+Pj4gU3VtbWFyeTogUmVhZHkg
d2l0aCBpc3N1ZXMNCj4+Pg0KPj4+IERvY3VtZW50IFJlYWR5LCBidXQgT3BlcmF0aW9uYWwgYW5k
IE1hbmFnZW1lbnQgY29uc2lkZXJhdGlvbnMNCj4+IG1pc3NpbmcuDQo+Pj4NCj4+PiBBcyB0aGUg
QWJzdHJhY3Qgc2F5czoNCj4+Pg0KPj4+ICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHR3byBhZGRp
dGlvbmFsIHBvbGljaWVzIGZvciB0aGUgUGFydGlhbA0KPj4+ICAgUmVsaWFiaWxpdHkgRXh0ZW5z
aW9uIG9mIHRoZSBTdHJlYW0gQ29udHJvbCBUcmFuc21pc3Npb24gUHJvdG9jb2wNCj4+PiAgIChQ
Ui1TQ1RQKSBhbGxvd2luZyB0byBsaW1pdCB0aGUgbnVtYmVyIG9mIHJldHJhbnNtaXNzaW9ucyBv
ciB0bw0KPj4+ICAgcHJpb3JpdGl6ZSB1c2VyIG1lc3NhZ2VzIGZvciBtb3JlIGVmZmljaWVudCBz
ZW5kIGJ1ZmZlciB1c2FnZS4NCj4+PiBBbHRob3VnaCB0aGlzIGRvY3VtZW50IGRlZmluZXMgYW4g
ZXh0ZW5zaW9uIG9mIGFuIGV4aXN0aW5nIHByb3RvY29sLCB0aGVyZQ0KPj4gYXJlIG5vIGV4cGxp
Y2l0IGNvbnNpZGVyYXRpb25zIGFib3V0IG9wZXJhdGlvbnMgYW5kIG1hbmFnZW1lbnQuIFRoZSBP
UFMNCj4+IGFuZCBUcmFuc3BvcnQgQURzIHNob3VsZCBkZWNpZGUgd2hldGhlciB0aGlzIGlzIGFu
IGlzc3VlIHRvIGJlIGFkZHJlc3NlZA0KPj4gYmVmb3JlIHRoZSBkb2N1bWVudCBpcyBhcHByb3Zl
ZC4NCj4+Pg0KPj4+IFNwZWNpZmljYWxseSwgZm9sbG93aW5nIHRoZSBjaGVja2xpc3RzIGluIFJG
QyA1NzA3LCBBcHBlbmRpeCBBOg0KPj4+DQo+Pj4gLSAgICAgICBEZXBsb3ltZW50IGlzIG5vdCBk
aXNjdXNzZWQsIGFsdGhvdWdoIHRoZXJlIGlzIHRleHQgdGhhdCBzYXlzIHRoYXQgdGhlDQo+PiBM
aW1pdGVkIFJldHJhbnNtaXNzaW9ucyBQb2xpY3kgY2FuIGJlIHVzZWQgd2l0aCBkYXRhIGNoYW5u
ZWxzIGluIHRoZQ0KPj4gV2ViUlRDIHByb3RvY29sIHN0YWNrLCBhbmQgdGhhdCB0aGUgUHJpb3Jp
dHkgUG9saWN5IGNhbiBiZSB1c2VkIGluIHRoZSBJUEZJWA0KPj4gcHJvdG9jb2wgc3RhY2sNCj4+
IFRoZSBpbnRyb2R1Y3Rpb24gc2F5cywgdGhhdCAiVGhlIGRlY2lzaW9uIHRvIGFiYW5kb24gYSB1
c2VyIG1lc3NhZ2UgaXMNCj4+IHNlbmRlciBzaWRlIG9ubHkiLiBTbyBmb3IgZGVwbG95aW5nIHRo
ZSBhZGRpdGlvbmFsIHBvbGljaWVzIHlvdSBuZWVkIHRvDQo+PiBpbXBsZW1lbnQgaXQgYXQgdGhl
IHNlbmRlciBzaWRlLg0KPg0KPiBUaGlzIGlzIG5vdCBleGFjdGx5IHdoYXQgSSBtZWFudCBieSBk
ZXBsb3ltZW50LiBNeSB1bmRlcnN0YW5kaW5nIGlzIHRoYXQgdGhlIHBvbGljaWVzIGRlZmluZWQg
aW4gdGhpcyBkb2N1bWVudCBjb21lIHRvIGFuc3dlciBzb21lIHNwZWNpZmljIG5lZWRzIG9mIHBy
b3RvY29scyBsaWtlIElQRklYIGFuZCBXZWJSVEMuIEFtIEkgY29ycmVjdD8gSWYgSSBhbSwgSSB3
b3VsZCBleHBlY3QgdGhlIHBvbGljaWVzIHRvIGJlIGRlcGxveWVkIHdoZXJlIHRoZXNlIHByb3Rv
Y29scyBydW4uDQpGb3IgSVBGSVggc29tZSBvZiB0aGlzIGlzIGRpc2N1c3NlZCBpbg0KaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzcwMTEjc2VjdGlvbi0xMC4yPGh0dHBzOi8vdXJsZGVm
ZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fdG9vbHMuaWV0Zi5vcmdfaHRt
bF9yZmM3MDExLTIzc2VjdGlvbi0yRDEwLjImZD1BQU1GYVEmYz1CRnBXUXc4YnN1S3BsMVNnaVpI
NjRRJnI9STRkekd4UjMxT2NOWENKZlF6dmxzaUxRZnVjQlhSdWNQdmRycGhwQnNGQSZtPTZjVVFV
N1d6R3hWekxJSEFzMHh4UVBtRjZ1eFg1QlkxdUJRY2laR1RDY2Mmcz1McWpTUWtqTkdlYkF2Q0Zn
VFNOeFhRX2U0Mjd2T0dUaFZZVUlBUE1KRGd3JmU9Pg0KRm9yIFJUQ1dlYiBpcyBpcyBkaXNjdXNz
ZWQgaW4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJ0Y3dlYi1kYXRh
LWNoYW5uZWwtMTIjc2VjdGlvbi02LjE8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29t
L3YyL3VybD91PWh0dHBzLTNBX190b29scy5pZXRmLm9yZ19odG1sX2RyYWZ0LTJEaWV0Zi0yRHJ0
Y3dlYi0yRGRhdGEtMkRjaGFubmVsLTJEMTItMjNzZWN0aW9uLTJENi4xJmQ9QUFNRmFRJmM9QkZw
V1F3OGJzdUtwbDFTZ2laSDY0USZyPUk0ZHpHeFIzMU9jTlhDSmZRenZsc2lMUWZ1Y0JYUnVjUHZk
cnBocEJzRkEmbT02Y1VRVTdXekd4VnpMSUhBczB4eFFQbUY2dXhYNUJZMXVCUWNpWkdUQ2NjJnM9
blZMM0VfNlBnZ2pJS3lMSUlzcEd0N1p6alZPb0dVMGZJb3Q5ODZqNnlUcyZlPT4NClBsZWFzZSBu
b3RlIHRoYXQgdGhlIHBvbGljaWVzIGRlZmluZWQgaGVyZSBhcmUgb2YgZ2VuZXJhbCB1c2UuIFNv
IHRoZSBkZXNjcmlwdGlvbg0KaG93IHRvIHVzZSBpdCB3aWxsIGJlIGluIHRoZSBkb2N1bWVudHMg
ZGVzY3JpYmluZyB0aGUgdXNlIGNhc2VzLg0KPg0KPj4+IC0gICAgICAgSW5zdGFsbGF0aW9uIGFu
ZCBpbml0aWFsIHNldHVwIGlzIG5vdCBkaXNjdXNzZWQNCj4+IFdlIG5vcm1hbGx5IGRvbid0IGRp
c2N1c3MgdGhlIGluc3RhbGxhdGlvbiBvZiB0aGUgT1MgKGFzc3VtaW5nIHRoYXQgdGhlIFNDVFAN
Cj4+IHN0YWNrIGlzIHBhcnQgb2YgdGhlIGtlcm5lbCwgd2hpY2ggaXMgdGhlIGNhc2UgZm9yIExp
bnV4LCBGcmVlQlNEIGFuZCBTb2xhcmlzKSBvcg0KPj4gaG93IHRvIGluc3RhbGwgYXBwbGljYXRp
b25zIChhc3N1bWluZyB0aGF0IHRoZSB0cmFuc3BvcnQgc3RhY2sgaXMgcGFydCBvZiB0aGUNCj4+
IGFwcGxpY2F0aW9uLCB3aGljaCBpcyB0aGUgY2FzZSBmb3IgYnJvd3NlcnMgbGlrZSBGaXJlZm94
LCBDaHJvbWUgYW5kIE9wZXJhKS4NCj4NCj4gVGhhbmsgeW91IGZvciB0aGUgY2xhcmlmaWNhdGlv
bi4gTWF5YmUgaXQgd291bGQgaGVscCB3cml0aW5nIGp1c3QgdGhpcyAtIHRoZSBpbnN0YWxsYXRp
b24gb2YgdGhlIG5ldyBjYXBhYmlsaXRpZXMgd2lsbCBiZSBwYXJ0IG9mIE9TIHVwZ3JhZGVzLg0K
Li4uIGlmIHlvdSB1c2UgYSBzdGFjayBwcm92aWRlZCBieSB0aGUga2VybmVsLiBJZiB0aGUgc3Rh
Y2sgaXMgcHJvdmlkZWQgYnkNCmFuIGFwcGxpY2F0aW9uLCB5b3UgbmVlZCB0byBpbnN0YWxsIHRo
ZSBhcHBsaWNhdGlvbi4NClNvIGl0IGNvbWVzIGRvd24gdG86IFlvdSBuZWVkIHRvIGluc3RhbGwg
dGhlIHNvZnR3YXJlIHdoaWNoIGNvbnRhaW5zIHRoZSBTQ1RQIHN0YWNrIHlvdSBhcmUgdXNpbmcu
DQpGb3IgbWUsIHRoaXMgaXMgb2J2aW91cy4gU28gSSdtIGhlc2l0YXRpbmcgdG8gYWRkIHRoaXMu
IEl0IHdvdWxkIGJlIGEgc2VudGVuY2Ugd2hpY2gNCnlvdSBjYW4gY29weSB0byBhbG1vc3QgZXZl
cnkgU0NUUCAob3IgVENQKSBzcGVjaWZpY2F0aW9uLg0KPg0KPj4+IC0gICAgICAgTWlncmF0aW9u
IFBhdGggZG9lcyBub3Qgc2VlbSB0byBhcHBseQ0KPj4gTWlncmF0aW5nIGZyb20gd2hhdD8gWW91
IGNhbiBqdXN0IHVzZSBhbiBpbXBsZW1lbnRhdGlvbiBhdCB0aGUgc2VuZGVyIHNpZGUNCj4+IGFu
ZCB5b3UgY2FuIG9wZXJhdGUgd2l0aCBldmVyeSByZWNlaXZlciBpbXBsZW1lbmluZyBSRkMgMzc1
OC4NCj4NCj4gVGhpcyBpcyBPSyAtIHRoYXQncyB3aGF0IEkgaGFkIGluIG1pbmQgd2hlbiBJIHNh
aWQgJ2RvZXMgbm90IGFwcGx5JyAtIHNvIG5vIG5lZWQgdG8gZG8gYW55dGhpbmcuDQo+DQo+Pj4g
LSAgICAgICBUaGVyZSBpcyBpbmZvcm1hdGlvbiBhYm91dCBSRkMgMzc1OCBiZWluZyBtYW5kYXRv
cnkgdG8gaW1wbGVtZW50IGluDQo+PiBvcmRlciB0byBpbXBsZW1lbnQgdGhlc2UgZXh0ZW5zaW9u
cw0KPj4+IC0gICAgICAgVGhlIGltcGFjdCBvbiB0aGUgbmV0d29yayBvcGVyYXRpb24gaXMgbm90
IGRpc2N1c3NlZCBleHBsaWNpdGx5DQo+PiBJbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMg
c2VjdGlvbiB3ZSBzYXkgdGhhdCB0aGUgU0NUUCBhc3NvY2lhdGlvbiB1c2luZw0KPj4gdGhpcyBl
eHRlbnNpb24gaXMgbm90IG1vcmUgYWdncmVzc2l2ZSB0aGFuIG9uZSBub3QgdXNpbmcgdGhlIGV4
dGVuc2lvbi4NCj4NCj4gT0suDQo+DQo+Pj4gLSAgICAgICBUaGVyZSBhcmUgbm8gZXhwbGljaXQg
c3VnZ2VzdGlvbnMgYWJvdXQgdmVyaWZ5aW5nIGNvcnJlY3Qgb3BlcmF0aW9ucywNCj4+IGFsdGhv
dWdoIG9uZSBjYW4gdW5kZXJzdGFuZCB0aGF0IHRoZSBzb2NrZXQgb3B0aW9ucyBkZXNjcmliZWQg
aW4gc2VjdGlvbnMNCj4+IDQuMywgNC40LCA0LjUgYXJlIHVzZWZ1bCB0byBkZXRlcm1pbmUgc3Ry
ZWFtIHNwZWNpZmljIHN0YXR1cywgYXNzb2NpYXRpb24NCj4+IHNwZWNpZmljIHN0YXR1cywgYW5k
IHRvIGdldCBhbmQgc2V0IHRoZSBQUi1TQ1RQIHN1cHBvcnQNCj4+IEFyZSB5b3Ugc3VnZ2VzdGlu
ZyB0byBzcGVjaWZ5IHRlc3QgY2FzZXM/IEF0IGxlYXN0IHRoaXMgaXMgbm90IGNvbW1vbiByaWdo
dA0KPj4gbm93IGluIHRyYW5zcG9ydCBhcmVhIGFsdGhvdWdoIGl0IHdvdWxkIG1ha2Ugc2Vuc2Ug
aW4gbXkgb3Bpbmlvbi4uLg0KPg0KPiBPSw0KPg0KPj4+IC0gICAgICAgSW50ZXJvcGVyYWJpbGl0
eSBkb2VzIG5vdCBzZWVtIHRvIGFwcGx5IGV4Y2VwdGluZyB0aGUgcmVxdWlyZW1lbnQgdG8NCj4+
IGltcGxlbWVudCBSRkMgMzc1OA0KPj4gQW5kIHRoYXQgaXMgYWxsIHdoYXQgaXMgbmVlZGVkLi4u
DQo+DQo+IE9LDQo+DQo+Pj4gLSAgICAgICBUaGVyZSBpcyBubyBpbmZvcm1hdGlvbiBhYm91dCBm
YXVsdHMgb3IgdGhyZXNob2xkIGNvbmRpdGlvbnMgdG8gYmUNCj4+IHJlcG9ydGVkDQo+PiBOb3Qg
c3VyZSB3aGF0IHlvdSBhcmUgZXhwZWN0aW5nIGhlcmUuDQo+DQo+IE5vdGhpbmcgLSB0aGlzIGlz
IGEgcG9pbnQgaW4gdGhlIDU3MDcgbGlzdCB3aGljaCBkb2VzIG5vdCBzZWVtIHRvIGFwcGx5Lg0K
Pg0KPj4+IC0gICAgICAgQ29uZmlndXJhdGlvbiBpcyBub3QgZGlzY3Vzc2VkLCBpdCBtYXkgbm90
IGFwcGx5LCBidXQgaXQgd291bGQgYmUgZ29vZA0KPj4gdG8gc3RhdGUgdGhpcw0KPj4gV2VsbCwg
Y29uZmlndXJhdGlvbiBpcyBkZXNjcmliZWQgaW4gZGV0YWlsIGluIHRoZSBzb2NrZXQgQVBJIHNl
Y3Rpb24uIFRoaXMgaXMgaG93DQo+PiB5b3UgY29uZmlndXJlIHRoZSB0cmFuc3BvcnQgc3RhY2su
DQo+DQo+IE9LDQo+DQo+Pj4gLSAgICAgICBUaGVyZSBhcmUgbm8gbWFuYWdlYWJpbGl0eSBjb25z
aWRlcmF0aW9ucyBvZiBhbnkga2luZA0KPj4gSXNuJ3QgdGhlIHNvY2tldCBBUEkgd2hhdCB5b3Ug
dXNlIHRvIG1hbmFnZSB0aGUgdHJhbnNwb3J0IHN0YWNrPyBPciBhcmUgeW91DQo+PiByZWZlcnJp
bmcgdG8gTUlCIHN0dWZmPw0KPg0KPiBXaGF0ZXZlciBpcyB1c2VkIGJ5IG9wZXJhdG9ycyB0byBw
ZXJmb3JtIGFuZCB2ZXJpZnkgaW5zdGFsbGF0aW9uLCBjaGVjayBiZWhhdmlvciwgYW5kIHRyb3Vi
bGVzaG9vdCBwcm9ibGVtcy4NCkFoaCwgT0suIEkgZG9uJ3QgdGhpbmsgYW4gb3BlcmF0b3Igd291
bGQgdXNlIHRoZSBzb2NrZXQgQVBJIGZvciB0aGF0Lg0KSWYgeW91IHdhbnQgdG8gdGVzdCB5b3Ug
dHJhbnNwb3J0IHN0YWNrIHlvdSBuZWVkIHRvIGhhdmUgdGVzdHMgYW5kIGEgdGVzdCB0b29sDQpm
b3IgcnVubmluZyB0aGVzZSB0ZXN0cy4gVXAgdG8gbm93LCB0aGUgSUVURiAoYXQgbGVhc3QgdGhl
IHRyYW5zcG9ydCBhcmVhKQ0KaGFzbid0IHNwZWNpZmllZCB0ZXN0cy4gUGVyc29uYWxseSwgSSB3
b3VsZCByZWFsbHkgbG92ZSB0byBkbyBpdCBhbmQgdGhpbmsNCnRoYXQgaXQgaXMgdmVyeSBpbXBv
cnRhbnQuIEJ1dCBJIHRoaW5rIHRoaXMgaXMgYSBkZWNpc2lvbiBub3QgbGltaXRlZCB0byB0aGlz
IHBhcnRpY3VsYXINCmRvY3VtZW50LCBidXQgdG8gKHRyYW5zcG9ydCkgcHJvdG9jb2xzIGluIGdl
bmVyYWwuIFNvIEkgbGVhdmUgaXQgdXAgdG8gdGhlIEFEcy4uLg0KDQpJJ2Qgc2F5IHRoZSBxdWVz
dGlvbiBvZiB0ZXN0IGNhc2VzIGhhcyBiZWVuIHJhaXNlZCB0byB0aGUgYXR0ZW50aW9uIG9mIFRT
VldHIChjYyBvbiB0aGlzIHRocmVhZCksIGFuZCBJJ2QgYmUgaGFwcHkgdG8gY29uc2lkZXIgdGhh
dCBpZiB0aGV5IHRoaW5rIHdvcmtpbmcgb24gdGhhdCB3b3VsZCBiZSBhIGdvb2QgcGxhbiwgYnV0
IEkgZG9uJ3QgdGhpbmsgdGhpcyBkb2N1bWVudCBuZWVkcyB0byB3YWl0IGZvciB0aGVtIHRvIGZp
Z3VyZSB0aGF0IG91dC4NCg0KSSdtIGdvb2Qgd2l0aCBNaWNoYWVsIHN1Ym1pdHRpbmcgYW4gdXBk
YXRlIGFkZHJlc3NpbmcgdGhlIGNvbW1lbnRzIGFzIGRpc2N1c3NlZCBpbiB0aGlzIHRocmVhZC4N
Cg0KVGhhbmtzLA0KDQpTcGVuY2VyDQoNCg==

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C92B8EFAZFFEXMB04globa_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAgMDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIg
MiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3Nl
LTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNv
Tm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNv
LXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQ
YXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGNtOw0KCW1h
cmdpbi1yaWdodDowY207DQoJbWFyZ2luLWJvdHRvbTowY207DQoJbWFyZ2luLWxlZnQ6MzYuMHB0
Ow0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4w
cHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRT
ZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1p
ZDoxMDQwOTMzNjkyOw0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRl
LWlkczotNTAxODY3MzM2IC0xNzk4NTA3OTcwIDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3
Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxl
dmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74OYOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczsN
Cgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJpOw0KCW1zby1iaWRpLWZvbnQtZmFtaWx5
OkFyaWFsO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxs
ZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250
LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6
bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5l
dyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1m
YW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTgu
MHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZl
bDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+C
pzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
b2wNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KLS0+
PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9
ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0
PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0K
PC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0K
PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBz
dHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+PCFbaWYg
IXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OldpbmdkaW5ncyI+PHNwYW4g
c3R5bGU9Im1zby1saXN0Oklnbm9yZSI+w5g8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtU
aW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5k
aWZdPjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+SSdtIGdvb2Qgd2l0aCBNaWNoYWVsIHN1Ym1pdHRp
bmcgYW4gdXBkYXRlIGFkZHJlc3NpbmcgdGhlIGNvbW1lbnRzIGFzIGRpc2N1c3NlZCBpbiB0aGlz
IHRocmVhZC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHls
ZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+PCFbaWYgIXN1
cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OldpbmdkaW5ncyI+PHNwYW4gc3R5
bGU9Im1zby1saXN0Oklnbm9yZSI+w5g8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1l
cyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZd
PjxzcGFuIGRpcj0iTFRSIj48L3NwYW4+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9InRleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAg
bGV2ZWwxIGxmbzEiPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTpXaW5nZGluZ3MiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPsOYPHNwYW4gc3R5bGU9
ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsNCjwvc3Bhbj48
L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+PC9zcGFuPlRoYW5rcyw8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRl
bnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+PCFbaWYgIXN1cHBvcnRMaXN0c10+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OldpbmdkaW5ncyI+PHNwYW4gc3R5bGU9Im1zby1saXN0
Oklnbm9yZSI+w5g8c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4m
cXVvdDsiPiZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIGRpcj0i
TFRSIj48L3NwYW4+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFn
cmFwaCIgc3R5bGU9InRleHQtaW5kZW50Oi0xOC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEi
PjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpXaW5nZGluZ3Mi
PjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPsOYPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQg
JnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFu
PjwhW2VuZGlmXT48c3BhbiBkaXI9IkxUUiI+PC9zcGFuPlNwZW5jZXI8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TWUgdG9vLiBDYW4g
eW91IHBsZWFzZSBzZW5kIG1lIGEgbm90ZSB3aGVuIHRoaXMgaGFwcGVucywgc28gdGhhdCBJIGRv
IG5vdCBtaXNzIHRoZSB1cGRhdGU/DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoYW5rcyBmb3IgY29uc2lkZXJpbmcg
bXkgY29tbWVudHMuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5EYW48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8
ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEu
MHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90OyI+IFNwZW5jZXIgRGF3a2lucyBhdCBJRVRGIFttYWlsdG86c3BlbmNlcmRh
d2tpbnMuaWV0ZkBnbWFpbC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIERlY2Vt
YmVyIDExLCAyMDE0IDEyOjEwIEFNPGJyPg0KPGI+VG86PC9iPiBNaWNoYWVsIFR1ZXhlbjxicj4N
CjxiPkNjOjwvYj4gUm9tYXNjYW51LCBEYW4gKERhbik7IG9wcy1kaXJAaWV0Zi5vcmc7IHRzdndn
QGlldGYub3JnOyBkcmFmdC1pZXRmLXRzdndnLXNjdHAtcHJwb2xpY2llcy5hbGxAdG9vbHMuaWV0
Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IE9QUy1ESVIgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtdHN2d2ctc2N0cC1wcnBvbGljaWVzLTA1LnR4dDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gcm9tIGF0IGxlYXN0IG9uZSBBRCA6LSk8bzpw
PjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBXZWQsIERlYyAxMCwgMjAxNCBh
dCAyOjUyIFBNLCBNaWNoYWVsIFR1ZXhlbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnR1ZXhlbkBmaC1t
dWVuc3Rlci5kZSIgdGFyZ2V0PSJfYmxhbmsiPnR1ZXhlbkBmaC1tdWVuc3Rlci5kZTwvYT4mZ3Q7
IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gMTAgRGVjIDIw
MTQsIGF0IDEzOjIzLCBSb21hc2NhbnUsIERhbiAoRGFuKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRy
b21hc2NhQGF2YXlhLmNvbSI+ZHJvbWFzY2FAYXZheWEuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0K
PGJyPg0KJmd0OyBIaSBNaWNoYWVsLDxicj4NCiZndDs8YnI+DQomZ3Q7IFRoYW5rIHlvdSBmb3Ig
YWRkcmVzc2luZyB0aGUgaXNzdWVzIHJhaXNlZCBpbiB0aGUgT1BTLURJUiByZXZpZXcuPGJyPg0K
Jmd0Ozxicj4NCiZndDsgRmlyc3QsIHBsZWFzZSBzZWUgdGhlIGRpc2NsYWltZXIgdGhhdCBJIHB1
dCBpbiBteSByZXZpZXc6PGJyPg0KJmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBBbHRob3VnaCB0aGlz
IGRvY3VtZW50IGRlZmluZXMgYW4gZXh0ZW5zaW9uIG9mIGFuIGV4aXN0aW5nIHByb3RvY29sLCB0
aGVyZTxicj4NCiZndDsmZ3Q7IGFyZSBubyBleHBsaWNpdCBjb25zaWRlcmF0aW9ucyBhYm91dCBv
cGVyYXRpb25zIGFuZCBtYW5hZ2VtZW50LiBUaGUgT1BTPGJyPg0KJmd0OyZndDsgYW5kIFRyYW5z
cG9ydCBBRHMgc2hvdWxkIGRlY2lkZSB3aGV0aGVyIHRoaXMgaXMgYW4gaXNzdWUgdG8gYmUgYWRk
cmVzc2VkPGJyPg0KJmd0OyZndDsgYmVmb3JlIHRoZSBkb2N1bWVudCBpcyBhcHByb3ZlZC48YnI+
DQomZ3Q7PGJyPg0KJmd0OyBUaGUgT1BTLURJUiByZXZpZXdzIGFyZSB3cml0dGVuIHRvIGhlbHAg
dGhlIE9QUyBBRHMgd2l0aCBhIHJlYWRpbmcgb2YgdGhlIEktRHMgaW4gcmV2aWV3IGZyb20gdGhl
IHBlcnNwZWN0aXZlIG9mIHRoZSBvcGVyYXRvcnMgdXNpbmcgdGhlIGFuZCBkZXBsb3lpbmcgdGhl
IG5ldyBwcm90b2NvbHMgb3IgZXh0ZW5zaW9ucyBkZWZpbmVkIGJ5IHRoZSBkb2N1bWVudC4gV2Ug
LSB0aGUgcmV2aWV3ZXJzIC0gYmVsaWV2ZSB0aGF0IHRoZSBvcGVyYXRpb25hbA0KIGFuZCBtYW5h
Z2VhYmlsaXR5IGlzc3VlcyBhcmUgaW1wb3J0YW50LCBidXQgaXQncyB1cCB0byB0aGUgQURzIHRv
IGRlY2lkZSB3aGV0aGVyIHRoZXkgYXJlIGltcG9ydGFudCBlbm91Z2ggdG8gcmVxdWlyZSBjaGFu
Z2VzIGluIHRoZSBkb2N1bWVudCwgYW5kIHdoYXQgdGhlc2UgY2hhbmdlcyBzaG91bGQgYmUuPGJy
Pg0KSGkgRGFuLDxicj4NCjxicj4NCnVuZGVyc3Rvb2QuIEJ1dCBJIHdhbnQgdG8gdW5kZXJzdGFu
ZCB5b3VyIHBvaW50cyBhbmQgcG9zc2libHkgYWRkcmVzcyB0aGVtLi4uPG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDs8YnI+DQomZ3Q7IE1vcmUg
aW4tbGluZS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBSZWdhcmRzLDxicj4NCiZndDs8YnI+DQomZ3Q7
IERhbjxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyZndDsgLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS08YnI+DQomZ3Q7Jmd0OyBGcm9tOiBNaWNoYWVsIFR1ZXhlbiBbbWFpbHRvOjxhIGhy
ZWY9Im1haWx0bzp0dWV4ZW5AZmgtbXVlbnN0ZXIuZGUiPnR1ZXhlbkBmaC1tdWVuc3Rlci5kZTwv
YT5dPGJyPg0KJmd0OyZndDsgU2VudDogV2VkbmVzZGF5LCBEZWNlbWJlciAxMCwgMjAxNCAxOjAy
IEFNPGJyPg0KJmd0OyZndDsgVG86IFJvbWFzY2FudSwgRGFuIChEYW4pPGJyPg0KJmd0OyZndDsg
Q2M6IDxhIGhyZWY9Im1haWx0bzpvcHMtZGlyQGlldGYub3JnIj5vcHMtZGlyQGlldGYub3JnPC9h
PjsgPGEgaHJlZj0ibWFpbHRvOnRzdndnQGlldGYub3JnIj4NCnRzdndnQGlldGYub3JnPC9hPjsg
ZHJhZnQtaWV0Zi10c3Z3Zy1zY3RwLTxicj4NCiZndDsmZ3Q7IDxhIGhyZWY9Im1haWx0bzpwcnBv
bGljaWVzLmFsbEB0b29scy5pZXRmLm9yZyI+cHJwb2xpY2llcy5hbGxAdG9vbHMuaWV0Zi5vcmc8
L2E+PGJyPg0KJmd0OyZndDsgU3ViamVjdDogUmU6IE9QUy1ESVIgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtdHN2d2ctc2N0cC1wcnBvbGljaWVzLTA1LnR4dDxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsgT24gMjYgTm92IDIwMTQsIGF0IDEzOjMzLCBSb21hc2NhbnUsIERhbiAoRGFuKSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmRyb21hc2NhQGF2YXlhLmNvbSI+ZHJvbWFzY2FAYXZheWEuY29tPC9hPiZn
dDs8YnI+DQomZ3Q7Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBJ
IGhhdmUgcmV2aWV3ZWQgdGhpcyBkb2N1bWVudCBhcyBwYXJ0IG9mIHRoZSBPcGVyYXRpb25hbCBk
aXJlY3RvcmF0ZSdzPGJyPg0KJmd0OyZndDsgb25nb2luZyBlZmZvcnQgdG8gcmV2aWV3IGFsbCBJ
RVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cuPGJyPg0KJmd0OyZndDsg
VGhlc2UgY29tbWVudHMmbmJzcDsgd2VyZSB3cml0dGVuIHByaW1hcmlseSBmb3IgdGhlIGJlbmVm
aXQgb2YgdGhlIG9wZXJhdGlvbmFsPGJyPg0KJmd0OyZndDsgYXJlYSBkaXJlY3RvcnMuJm5ic3A7
IERvY3VtZW50IGVkaXRvcnMgYW5kIFdHIGNoYWlycyBzaG91bGQgdHJlYXQgdGhlc2U8YnI+DQom
Z3Q7Jmd0OyBjb21tZW50cyBqdXN0IGxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy48
YnI+DQomZ3Q7Jmd0OyBIaSBEYW4sPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyB0aGFuayB5
b3UgdmVyeSBtdWNoIGZvciB5b3VyIHJldmlldy4gUGxlYXNlIHNlZSBteSBxdWVzdGlvbnMgYW5k
PGJyPg0KJmd0OyZndDsgY29tbWVudHMgaW4tbGluZS48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7IEJlc3QgcmVnYXJkczxicj4NCiZndDsmZ3Q7IE1pY2hhZWw8YnI+DQomZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgU3VtbWFyeTogUmVhZHkgd2l0aCBp
c3N1ZXM8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgRG9jdW1lbnQgUmVhZHks
IGJ1dCBPcGVyYXRpb25hbCBhbmQgTWFuYWdlbWVudCBjb25zaWRlcmF0aW9uczxicj4NCiZndDsm
Z3Q7IG1pc3NpbmcuPGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IEFzIHRoZSBB
YnN0cmFjdCBzYXlzOjxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZuYnNwOyAm
bmJzcDtUaGlzIGRvY3VtZW50IGRlZmluZXMgdHdvIGFkZGl0aW9uYWwgcG9saWNpZXMgZm9yIHRo
ZSBQYXJ0aWFsPGJyPg0KJmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwO1JlbGlhYmlsaXR5IEV4dGVu
c2lvbiBvZiB0aGUgU3RyZWFtIENvbnRyb2wgVHJhbnNtaXNzaW9uIFByb3RvY29sPGJyPg0KJmd0
OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyhQUi1TQ1RQKSBhbGxvd2luZyB0byBsaW1pdCB0aGUgbnVt
YmVyIG9mIHJldHJhbnNtaXNzaW9ucyBvciB0bzxicj4NCiZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJz
cDtwcmlvcml0aXplIHVzZXIgbWVzc2FnZXMgZm9yIG1vcmUgZWZmaWNpZW50IHNlbmQgYnVmZmVy
IHVzYWdlLjxicj4NCiZndDsmZ3Q7Jmd0OyBBbHRob3VnaCB0aGlzIGRvY3VtZW50IGRlZmluZXMg
YW4gZXh0ZW5zaW9uIG9mIGFuIGV4aXN0aW5nIHByb3RvY29sLCB0aGVyZTxicj4NCiZndDsmZ3Q7
IGFyZSBubyBleHBsaWNpdCBjb25zaWRlcmF0aW9ucyBhYm91dCBvcGVyYXRpb25zIGFuZCBtYW5h
Z2VtZW50LiBUaGUgT1BTPGJyPg0KJmd0OyZndDsgYW5kIFRyYW5zcG9ydCBBRHMgc2hvdWxkIGRl
Y2lkZSB3aGV0aGVyIHRoaXMgaXMgYW4gaXNzdWUgdG8gYmUgYWRkcmVzc2VkPGJyPg0KJmd0OyZn
dDsgYmVmb3JlIHRoZSBkb2N1bWVudCBpcyBhcHByb3ZlZC48YnI+DQomZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsgU3BlY2lmaWNhbGx5LCBmb2xsb3dpbmcgdGhlIGNoZWNrbGlzdHMgaW4g
UkZDIDU3MDcsIEFwcGVuZGl4IEE6PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
IC0mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtEZXBsb3ltZW50IGlzIG5vdCBkaXNjdXNzZWQs
IGFsdGhvdWdoIHRoZXJlIGlzIHRleHQgdGhhdCBzYXlzIHRoYXQgdGhlPGJyPg0KJmd0OyZndDsg
TGltaXRlZCBSZXRyYW5zbWlzc2lvbnMgUG9saWN5IGNhbiBiZSB1c2VkIHdpdGggZGF0YSBjaGFu
bmVscyBpbiB0aGU8YnI+DQomZ3Q7Jmd0OyBXZWJSVEMgcHJvdG9jb2wgc3RhY2ssIGFuZCB0aGF0
IHRoZSBQcmlvcml0eSBQb2xpY3kgY2FuIGJlIHVzZWQgaW4gdGhlIElQRklYPGJyPg0KJmd0OyZn
dDsgcHJvdG9jb2wgc3RhY2s8YnI+DQomZ3Q7Jmd0OyBUaGUgaW50cm9kdWN0aW9uIHNheXMsIHRo
YXQgJnF1b3Q7VGhlIGRlY2lzaW9uIHRvIGFiYW5kb24gYSB1c2VyIG1lc3NhZ2UgaXM8YnI+DQom
Z3Q7Jmd0OyBzZW5kZXIgc2lkZSBvbmx5JnF1b3Q7LiBTbyBmb3IgZGVwbG95aW5nIHRoZSBhZGRp
dGlvbmFsIHBvbGljaWVzIHlvdSBuZWVkIHRvPGJyPg0KJmd0OyZndDsgaW1wbGVtZW50IGl0IGF0
IHRoZSBzZW5kZXIgc2lkZS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBUaGlzIGlzIG5vdCBleGFjdGx5
IHdoYXQgSSBtZWFudCBieSBkZXBsb3ltZW50LiBNeSB1bmRlcnN0YW5kaW5nIGlzIHRoYXQgdGhl
IHBvbGljaWVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBjb21lIHRvIGFuc3dlciBzb21lIHNw
ZWNpZmljIG5lZWRzIG9mIHByb3RvY29scyBsaWtlIElQRklYIGFuZCBXZWJSVEMuIEFtIEkgY29y
cmVjdD8gSWYgSSBhbSwgSSB3b3VsZCBleHBlY3QgdGhlIHBvbGljaWVzIHRvIGJlIGRlcGxveWVk
IHdoZXJlIHRoZXNlDQogcHJvdG9jb2xzIHJ1bi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gb3IgSVBGSVggc29tZSBvZiB0aGlzIGlzIGRpc2N1
c3NlZCBpbjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92
Mi91cmw/dT1odHRwcy0zQV9fdG9vbHMuaWV0Zi5vcmdfaHRtbF9yZmM3MDExLTIzc2VjdGlvbi0y
RDEwLjImYW1wO2Q9QUFNRmFRJmFtcDtjPUJGcFdRdzhic3VLcGwxU2dpWkg2NFEmYW1wO3I9STRk
ekd4UjMxT2NOWENKZlF6dmxzaUxRZnVjQlhSdWNQdmRycGhwQnNGQSZhbXA7bT02Y1VRVTdXekd4
VnpMSUhBczB4eFFQbUY2dXhYNUJZMXVCUWNpWkdUQ2NjJmFtcDtzPUxxalNRa2pOR2ViQXZDRmdU
U054WFFfZTQyN3ZPR1RoVllVSUFQTUpEZ3cmYW1wO2U9IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzcwMTEjc2VjdGlvbi0xMC4yPC9hPjxicj4NCkZvciBS
VENXZWIgaXMgaXMgZGlzY3Vzc2VkIGluPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNl
LnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX190b29scy5pZXRmLm9yZ19odG1sX2Ry
YWZ0LTJEaWV0Zi0yRHJ0Y3dlYi0yRGRhdGEtMkRjaGFubmVsLTJEMTItMjNzZWN0aW9uLTJENi4x
JmFtcDtkPUFBTUZhUSZhbXA7Yz1CRnBXUXc4YnN1S3BsMVNnaVpINjRRJmFtcDtyPUk0ZHpHeFIz
MU9jTlhDSmZRenZsc2lMUWZ1Y0JYUnVjUHZkcnBocEJzRkEmYW1wO209NmNVUVU3V3pHeFZ6TElI
QXMweHhRUG1GNnV4WDVCWTF1QlFjaVpHVENjYyZhbXA7cz1uVkwzRV82UGdnaklLeUxJSXNwR3Q3
WnpqVk9vR1UwZklvdDk4Nmo2eVRzJmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXJ0Y3dlYi1kYXRhLWNoYW5uZWwtMTIjc2VjdGlv
bi02LjE8L2E+PGJyPg0KUGxlYXNlIG5vdGUgdGhhdCB0aGUgcG9saWNpZXMgZGVmaW5lZCBoZXJl
IGFyZSBvZiBnZW5lcmFsIHVzZS4gU28gdGhlIGRlc2NyaXB0aW9uPGJyPg0KaG93IHRvIHVzZSBp
dCB3aWxsIGJlIGluIHRoZSBkb2N1bWVudHMgZGVzY3JpYmluZyB0aGUgdXNlIGNhc2VzLjxicj4N
CiZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgLSZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0luc3Rh
bGxhdGlvbiBhbmQgaW5pdGlhbCBzZXR1cCBpcyBub3QgZGlzY3Vzc2VkPGJyPg0KJmd0OyZndDsg
V2Ugbm9ybWFsbHkgZG9uJ3QgZGlzY3VzcyB0aGUgaW5zdGFsbGF0aW9uIG9mIHRoZSBPUyAoYXNz
dW1pbmcgdGhhdCB0aGUgU0NUUDxicj4NCiZndDsmZ3Q7IHN0YWNrIGlzIHBhcnQgb2YgdGhlIGtl
cm5lbCwgd2hpY2ggaXMgdGhlIGNhc2UgZm9yIExpbnV4LCBGcmVlQlNEIGFuZCBTb2xhcmlzKSBv
cjxicj4NCiZndDsmZ3Q7IGhvdyB0byBpbnN0YWxsIGFwcGxpY2F0aW9ucyAoYXNzdW1pbmcgdGhh
dCB0aGUgdHJhbnNwb3J0IHN0YWNrIGlzIHBhcnQgb2YgdGhlPGJyPg0KJmd0OyZndDsgYXBwbGlj
YXRpb24sIHdoaWNoIGlzIHRoZSBjYXNlIGZvciBicm93c2VycyBsaWtlIEZpcmVmb3gsIENocm9t
ZSBhbmQgT3BlcmEpLjxicj4NCiZndDs8YnI+DQomZ3Q7IFRoYW5rIHlvdSBmb3IgdGhlIGNsYXJp
ZmljYXRpb24uIE1heWJlIGl0IHdvdWxkIGhlbHAgd3JpdGluZyBqdXN0IHRoaXMgLSB0aGUgaW5z
dGFsbGF0aW9uIG9mIHRoZSBuZXcgY2FwYWJpbGl0aWVzIHdpbGwgYmUgcGFydCBvZiBPUyB1cGdy
YWRlcy48YnI+DQouLi4gaWYgeW91IHVzZSBhIHN0YWNrIHByb3ZpZGVkIGJ5IHRoZSBrZXJuZWwu
IElmIHRoZSBzdGFjayBpcyBwcm92aWRlZCBieTxicj4NCmFuIGFwcGxpY2F0aW9uLCB5b3UgbmVl
ZCB0byBpbnN0YWxsIHRoZSBhcHBsaWNhdGlvbi48YnI+DQpTbyBpdCBjb21lcyBkb3duIHRvOiBZ
b3UgbmVlZCB0byBpbnN0YWxsIHRoZSBzb2Z0d2FyZSB3aGljaCBjb250YWlucyB0aGUgU0NUUCBz
dGFjayB5b3UgYXJlIHVzaW5nLjxicj4NCkZvciBtZSwgdGhpcyBpcyBvYnZpb3VzLiBTbyBJJ20g
aGVzaXRhdGluZyB0byBhZGQgdGhpcy4gSXQgd291bGQgYmUgYSBzZW50ZW5jZSB3aGljaDxicj4N
CnlvdSBjYW4gY29weSB0byBhbG1vc3QgZXZlcnkgU0NUUCAob3IgVENQKSBzcGVjaWZpY2F0aW9u
LjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7
PGJyPg0KJmd0OyZndDsmZ3Q7IC0mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtNaWdyYXRpb24g
UGF0aCBkb2VzIG5vdCBzZWVtIHRvIGFwcGx5PGJyPg0KJmd0OyZndDsgTWlncmF0aW5nIGZyb20g
d2hhdD8gWW91IGNhbiBqdXN0IHVzZSBhbiBpbXBsZW1lbnRhdGlvbiBhdCB0aGUgc2VuZGVyIHNp
ZGU8YnI+DQomZ3Q7Jmd0OyBhbmQgeW91IGNhbiBvcGVyYXRlIHdpdGggZXZlcnkgcmVjZWl2ZXIg
aW1wbGVtZW5pbmcgUkZDIDM3NTguPGJyPg0KJmd0Ozxicj4NCiZndDsgVGhpcyBpcyBPSyAtIHRo
YXQncyB3aGF0IEkgaGFkIGluIG1pbmQgd2hlbiBJIHNhaWQgJ2RvZXMgbm90IGFwcGx5JyAtIHNv
IG5vIG5lZWQgdG8gZG8gYW55dGhpbmcuPGJyPg0KJmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyAtJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7VGhlcmUgaXMgaW5mb3JtYXRpb24gYWJvdXQgUkZDIDM3
NTggYmVpbmcgbWFuZGF0b3J5IHRvIGltcGxlbWVudCBpbjxicj4NCiZndDsmZ3Q7IG9yZGVyIHRv
IGltcGxlbWVudCB0aGVzZSBleHRlbnNpb25zPGJyPg0KJmd0OyZndDsmZ3Q7IC0mbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtUaGUgaW1wYWN0IG9uIHRoZSBuZXR3b3JrIG9wZXJhdGlvbiBpcyBu
b3QgZGlzY3Vzc2VkIGV4cGxpY2l0bHk8YnI+DQomZ3Q7Jmd0OyBJbiB0aGUgc2VjdXJpdHkgY29u
c2lkZXJhdGlvbnMgc2VjdGlvbiB3ZSBzYXkgdGhhdCB0aGUgU0NUUCBhc3NvY2lhdGlvbiB1c2lu
Zzxicj4NCiZndDsmZ3Q7IHRoaXMgZXh0ZW5zaW9uIGlzIG5vdCBtb3JlIGFnZ3Jlc3NpdmUgdGhh
biBvbmUgbm90IHVzaW5nIHRoZSBleHRlbnNpb24uPGJyPg0KJmd0Ozxicj4NCiZndDsgT0suPGJy
Pg0KJmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyAtJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7VGhl
cmUgYXJlIG5vIGV4cGxpY2l0IHN1Z2dlc3Rpb25zIGFib3V0IHZlcmlmeWluZyBjb3JyZWN0IG9w
ZXJhdGlvbnMsPGJyPg0KJmd0OyZndDsgYWx0aG91Z2ggb25lIGNhbiB1bmRlcnN0YW5kIHRoYXQg
dGhlIHNvY2tldCBvcHRpb25zIGRlc2NyaWJlZCBpbiBzZWN0aW9uczxicj4NCiZndDsmZ3Q7IDQu
MywgNC40LCA0LjUgYXJlIHVzZWZ1bCB0byBkZXRlcm1pbmUgc3RyZWFtIHNwZWNpZmljIHN0YXR1
cywgYXNzb2NpYXRpb248YnI+DQomZ3Q7Jmd0OyBzcGVjaWZpYyBzdGF0dXMsIGFuZCB0byBnZXQg
YW5kIHNldCB0aGUgUFItU0NUUCBzdXBwb3J0PGJyPg0KJmd0OyZndDsgQXJlIHlvdSBzdWdnZXN0
aW5nIHRvIHNwZWNpZnkgdGVzdCBjYXNlcz8gQXQgbGVhc3QgdGhpcyBpcyBub3QgY29tbW9uIHJp
Z2h0PGJyPg0KJmd0OyZndDsgbm93IGluIHRyYW5zcG9ydCBhcmVhIGFsdGhvdWdoIGl0IHdvdWxk
IG1ha2Ugc2Vuc2UgaW4gbXkgb3Bpbmlvbi4uLjxicj4NCiZndDs8YnI+DQomZ3Q7IE9LPGJyPg0K
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyAtJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7SW50ZXJv
cGVyYWJpbGl0eSBkb2VzIG5vdCBzZWVtIHRvIGFwcGx5IGV4Y2VwdGluZyB0aGUgcmVxdWlyZW1l
bnQgdG88YnI+DQomZ3Q7Jmd0OyBpbXBsZW1lbnQgUkZDIDM3NTg8YnI+DQomZ3Q7Jmd0OyBBbmQg
dGhhdCBpcyBhbGwgd2hhdCBpcyBuZWVkZWQuLi48YnI+DQomZ3Q7PGJyPg0KJmd0OyBPSzxicj4N
CiZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgLSZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1RoZXJl
IGlzIG5vIGluZm9ybWF0aW9uIGFib3V0IGZhdWx0cyBvciB0aHJlc2hvbGQgY29uZGl0aW9ucyB0
byBiZTxicj4NCiZndDsmZ3Q7IHJlcG9ydGVkPGJyPg0KJmd0OyZndDsgTm90IHN1cmUgd2hhdCB5
b3UgYXJlIGV4cGVjdGluZyBoZXJlLjxicj4NCiZndDs8YnI+DQomZ3Q7IE5vdGhpbmcgLSB0aGlz
IGlzIGEgcG9pbnQgaW4gdGhlIDU3MDcgbGlzdCB3aGljaCBkb2VzIG5vdCBzZWVtIHRvIGFwcGx5
Ljxicj4NCiZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgLSZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
O0NvbmZpZ3VyYXRpb24gaXMgbm90IGRpc2N1c3NlZCwgaXQgbWF5IG5vdCBhcHBseSwgYnV0IGl0
IHdvdWxkIGJlIGdvb2Q8YnI+DQomZ3Q7Jmd0OyB0byBzdGF0ZSB0aGlzPGJyPg0KJmd0OyZndDsg
V2VsbCwgY29uZmlndXJhdGlvbiBpcyBkZXNjcmliZWQgaW4gZGV0YWlsIGluIHRoZSBzb2NrZXQg
QVBJIHNlY3Rpb24uIFRoaXMgaXMgaG93PGJyPg0KJmd0OyZndDsgeW91IGNvbmZpZ3VyZSB0aGUg
dHJhbnNwb3J0IHN0YWNrLjxicj4NCiZndDs8YnI+DQomZ3Q7IE9LPGJyPg0KJmd0Ozxicj4NCiZn
dDsmZ3Q7Jmd0OyAtJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7VGhlcmUgYXJlIG5vIG1hbmFn
ZWFiaWxpdHkgY29uc2lkZXJhdGlvbnMgb2YgYW55IGtpbmQ8YnI+DQomZ3Q7Jmd0OyBJc24ndCB0
aGUgc29ja2V0IEFQSSB3aGF0IHlvdSB1c2UgdG8gbWFuYWdlIHRoZSB0cmFuc3BvcnQgc3RhY2s/
IE9yIGFyZSB5b3U8YnI+DQomZ3Q7Jmd0OyByZWZlcnJpbmcgdG8gTUlCIHN0dWZmPzxicj4NCiZn
dDs8YnI+DQomZ3Q7IFdoYXRldmVyIGlzIHVzZWQgYnkgb3BlcmF0b3JzIHRvIHBlcmZvcm0gYW5k
IHZlcmlmeSBpbnN0YWxsYXRpb24sIGNoZWNrIGJlaGF2aW9yLCBhbmQgdHJvdWJsZXNob290IHBy
b2JsZW1zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+QWhoLCBPSy4gSSBkb24ndCB0aGluayBh
biBvcGVyYXRvciB3b3VsZCB1c2UgdGhlIHNvY2tldCBBUEkgZm9yIHRoYXQuPGJyPg0KSWYgeW91
IHdhbnQgdG8gdGVzdCB5b3UgdHJhbnNwb3J0IHN0YWNrIHlvdSBuZWVkIHRvIGhhdmUgdGVzdHMg
YW5kIGEgdGVzdCB0b29sPGJyPg0KZm9yIHJ1bm5pbmcgdGhlc2UgdGVzdHMuIFVwIHRvIG5vdywg
dGhlIElFVEYgKGF0IGxlYXN0IHRoZSB0cmFuc3BvcnQgYXJlYSk8YnI+DQpoYXNuJ3Qgc3BlY2lm
aWVkIHRlc3RzLiBQZXJzb25hbGx5LCBJIHdvdWxkIHJlYWxseSBsb3ZlIHRvIGRvIGl0IGFuZCB0
aGluazxicj4NCnRoYXQgaXQgaXMgdmVyeSBpbXBvcnRhbnQuIEJ1dCBJIHRoaW5rIHRoaXMgaXMg
YSBkZWNpc2lvbiBub3QgbGltaXRlZCB0byB0aGlzIHBhcnRpY3VsYXI8YnI+DQpkb2N1bWVudCwg
YnV0IHRvICh0cmFuc3BvcnQpIHByb3RvY29scyBpbiBnZW5lcmFsLiBTbyBJIGxlYXZlIGl0IHVw
IHRvIHRoZSBBRHMuLi48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkknZCBzYXkmbmJzcDt0aGUgcXVlc3Rpb24gb2YgdGVzdCBjYXNlcyZuYnNwO2hhcyBiZWVu
IHJhaXNlZCB0byB0aGUgYXR0ZW50aW9uIG9mIFRTVldHIChjYyBvbiB0aGlzIHRocmVhZCksIGFu
ZCBJJ2QgYmUgaGFwcHkgdG8gY29uc2lkZXIgdGhhdCBpZiB0aGV5IHRoaW5rIHdvcmtpbmcgb24g
dGhhdCB3b3VsZCBiZSBhIGdvb2QgcGxhbiwgYnV0IEkgZG9uJ3QgdGhpbmsgdGhpcyBkb2N1bWVu
dCBuZWVkcyB0byB3YWl0IGZvciB0aGVtDQogdG8gZmlndXJlIHRoYXQgb3V0LjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ20gZ29vZCB3aXRo
IE1pY2hhZWwgc3VibWl0dGluZyBhbiB1cGRhdGUgYWRkcmVzc2luZyB0aGUgY29tbWVudHMgYXMg
ZGlzY3Vzc2VkIGluIHRoaXMgdGhyZWFkLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNwZW5jZXI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C92B8EFAZFFEXMB04globa_--


From nobody Thu Dec 11 03:10:40 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B291A6F97; Thu, 11 Dec 2014 03:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 r-PYoMJRz24g; Thu, 11 Dec 2014 03:10:33 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C343D1A88AC; Thu, 11 Dec 2014 03:10:30 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 88C462FE091; Thu, 11 Dec 2014 11:10:29 +0000 (GMT)
Received: from 2001:630:241:207:21f:5bff:fe38:7354 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Thu, 11 Dec 2014 11:10:29 -0000
Message-ID: <7d7fcc0039f4fe019b8981541c9bdcd2.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com> <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de> <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com>
Date: Thu, 11 Dec 2014 11:10:29 -0000
From: gorry@erg.abdn.ac.uk
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/8AjemyjflC5nCyIRqaaO7iqNXdc
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, Michael Tuexen <tuexen@fh-muenster.de>, "draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org" <draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 11:10:36 -0000

So, it seems most of this is covered by clear statements that describe
this as a sender-side only change to the transport protocol of the
endpoint stack. ... and description and references to examples where
deployment is expected, etc - I suggest to expand the introduction?

Michael can you run the changes by me as the document shepherd, so I can
check that I see the logic and it doesn't potentially  create new issues?

Gorry

> Ã˜  I'm good with Michael submitting an update addressing the comments as
> discussed in this thread.
>
> Ã˜
>
> Ã˜  Thanks,
>
> Ã˜
>
> Ã˜  Spencer
>
> Me too. Can you please send me a note when this happens, so that I do not
> miss the update?
>
> Thanks for considering my comments.
>
> Regards,
>
> Dan
>
>
> From: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com]
> Sent: Thursday, December 11, 2014 12:10 AM
> To: Michael Tuexen
> Cc: Romascanu, Dan (Dan); ops-dir@ietf.org; tsvwg@ietf.org;
> draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org
> Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
>
> From at least one AD :-)
>
> On Wed, Dec 10, 2014 at 2:52 PM, Michael Tuexen
> <tuexen@fh-muenster.de<mailto:tuexen@fh-muenster.de>> wrote:
> On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan)
> <dromasca@avaya.com<mailto:dromasca@avaya.com>> wrote:
>
>> Hi Michael,
>>
>> Thank you for addressing the issues raised in the OPS-DIR review.
>>
>> First, please see the disclaimer that I put in my review:
>>
>>>> Although this document defines an extension of an existing protocol,
>>>> there
>>> are no explicit considerations about operations and management. The
>>> OPS
>>> and Transport ADs should decide whether this is an issue to be
>>> addressed
>>> before the document is approved.
>>
>> The OPS-DIR reviews are written to help the OPS ADs with a reading of
>> the I-Ds in review from the perspective of the operators using the and
>> deploying the new protocols or extensions defined by the document. We -
>> the reviewers - believe that the operational and manageability issues
>> are important, but it's up to the ADs to decide whether they are
>> important enough to require changes in the document, and what these
>> changes should be.
> Hi Dan,
>
> understood. But I want to understand your points and possibly address
> them...
>>
>> More in-line.
>>
>> Regards,
>>
>> Dan
>>
>>
>>> -----Original Message-----
>>> From: Michael Tuexen
>>> [mailto:tuexen@fh-muenster.de<mailto:tuexen@fh-muenster.de>]
>>> Sent: Wednesday, December 10, 2014 1:02 AM
>>> To: Romascanu, Dan (Dan)
>>> Cc: ops-dir@ietf.org<mailto:ops-dir@ietf.org>;
>>> tsvwg@ietf.org<mailto:tsvwg@ietf.org>; draft-ietf-tsvwg-sctp-
>>> prpolicies.all@tools.ietf.org<mailto:prpolicies.all@tools.ietf.org>
>>> Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
>>>
>>> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan)
>>> <dromasca@avaya.com<mailto:dromasca@avaya.com>>
>>> wrote:
>>>
>>>> I have reviewed this document as part of the Operational
>>>> directorate's
>>> ongoing effort to review all IETF documents being processed by the
>>> IESG.
>>> These comments  were written primarily for the benefit of the
>>> operational
>>> area directors.  Document editors and WG chairs should treat these
>>> comments just like any other last call comments.
>>> Hi Dan,
>>>
>>> thank you very much for your review. Please see my questions and
>>> comments in-line.
>>>
>>> Best regards
>>> Michael
>>>>
>>>>
>>>> Summary: Ready with issues
>>>>
>>>> Document Ready, but Operational and Management considerations
>>> missing.
>>>>
>>>> As the Abstract says:
>>>>
>>>>   This document defines two additional policies for the Partial
>>>>   Reliability Extension of the Stream Control Transmission Protocol
>>>>   (PR-SCTP) allowing to limit the number of retransmissions or to
>>>>   prioritize user messages for more efficient send buffer usage.
>>>> Although this document defines an extension of an existing protocol,
>>>> there
>>> are no explicit considerations about operations and management. The
>>> OPS
>>> and Transport ADs should decide whether this is an issue to be
>>> addressed
>>> before the document is approved.
>>>>
>>>> Specifically, following the checklists in RFC 5707, Appendix A:
>>>>
>>>> -       Deployment is not discussed, although there is text that says
>>>> that the
>>> Limited Retransmissions Policy can be used with data channels in the
>>> WebRTC protocol stack, and that the Priority Policy can be used in the
>>> IPFIX
>>> protocol stack
>>> The introduction says, that "The decision to abandon a user message is
>>> sender side only". So for deploying the additional policies you need
>>> to
>>> implement it at the sender side.
>>
>> This is not exactly what I meant by deployment. My understanding is that
>> the policies defined in this document come to answer some specific needs
>> of protocols like IPFIX and WebRTC. Am I correct? If I am, I would
>> expect the policies to be deployed where these protocols run.
> For IPFIX some of this is discussed in
> https://tools.ietf.org/html/rfc7011#section-10.2<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7011-23section-2D10.2&d=AAMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&s=LqjSQkjNGebAvCFgTSNxXQ_e427vOGThVYUIAPMJDgw&e=>
> For RTCWeb is is discussed in
> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Drtcweb-2Ddata-2Dchannel-2D12-23section-2D6.1&d=AAMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&s=nVL3E_6PggjIKyLIIspGt7ZzjVOoGU0fIot986j6yTs&e=>
> Please note that the policies defined here are of general use. So the
> description
> how to use it will be in the documents describing the use cases.
>>
>>>> -       Installation and initial setup is not discussed
>>> We normally don't discuss the installation of the OS (assuming that the
>>> SCTP
>>> stack is part of the kernel, which is the case for Linux, FreeBSD and
>>> Solaris) or
>>> how to install applications (assuming that the transport stack is part
>>> of the
>>> application, which is the case for browsers like Firefox, Chrome and
>>> Opera).
>>
>> Thank you for the clarification. Maybe it would help writing just this -
>> the installation of the new capabilities will be part of OS upgrades.
> ... if you use a stack provided by the kernel. If the stack is provided
> by
> an application, you need to install the application.
> So it comes down to: You need to install the software which contains the
> SCTP stack you are using.
> For me, this is obvious. So I'm hesitating to add this. It would be a
> sentence which
> you can copy to almost every SCTP (or TCP) specification.
>>
>>>> -       Migration Path does not seem to apply
>>> Migrating from what? You can just use an implementation at the sender
>>> side
>>> and you can operate with every receiver implemening RFC 3758.
>>
>> This is OK - that's what I had in mind when I said 'does not apply' - so
>> no need to do anything.
>>
>>>> -       There is information about RFC 3758 being mandatory to
>>>> implement in
>>> order to implement these extensions
>>>> -       The impact on the network operation is not discussed
>>>> explicitly
>>> In the security considerations section we say that the SCTP association
>>> using
>>> this extension is not more aggressive than one not using the
>>> extension.
>>
>> OK.
>>
>>>> -       There are no explicit suggestions about verifying correct
>>>> operations,
>>> although one can understand that the socket options described in
>>> sections
>>> 4.3, 4.4, 4.5 are useful to determine stream specific status,
>>> association
>>> specific status, and to get and set the PR-SCTP support
>>> Are you suggesting to specify test cases? At least this is not common
>>> right
>>> now in transport area although it would make sense in my opinion...
>>
>> OK
>>
>>>> -       Interoperability does not seem to apply excepting the
>>>> requirement to
>>> implement RFC 3758
>>> And that is all what is needed...
>>
>> OK
>>
>>>> -       There is no information about faults or threshold conditions
>>>> to be
>>> reported
>>> Not sure what you are expecting here.
>>
>> Nothing - this is a point in the 5707 list which does not seem to
>> apply.
>>
>>>> -       Configuration is not discussed, it may not apply, but it would
>>>> be good
>>> to state this
>>> Well, configuration is described in detail in the socket API section.
>>> This is how
>>> you configure the transport stack.
>>
>> OK
>>
>>>> -       There are no manageability considerations of any kind
>>> Isn't the socket API what you use to manage the transport stack? Or are
>>> you
>>> referring to MIB stuff?
>>
>> Whatever is used by operators to perform and verify installation, check
>> behavior, and troubleshoot problems.
> Ahh, OK. I don't think an operator would use the socket API for that.
> If you want to test you transport stack you need to have tests and a test
> tool
> for running these tests. Up to now, the IETF (at least the transport
> area)
> hasn't specified tests. Personally, I would really love to do it and
> think
> that it is very important. But I think this is a decision not limited to
> this particular
> document, but to (transport) protocols in general. So I leave it up to the
> ADs...
>
> I'd say the question of test cases has been raised to the attention of
> TSVWG (cc on this thread), and I'd be happy to consider that if they think
> working on that would be a good plan, but I don't think this document
> needs to wait for them to figure that out.
>
> I'm good with Michael submitting an update addressing the comments as
> discussed in this thread.
>
> Thanks,
>
> Spencer
>
>


From nobody Thu Dec 11 06:36:45 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCC21ACEE4; Thu, 11 Dec 2014 06:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 9fn9d-SXCY3m; Thu, 11 Dec 2014 06:36:40 -0800 (PST)
Received: from rachael.franken.de (rachael.franken.de [193.175.24.38]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC8E81ACEEE; Thu, 11 Dec 2014 06:36:34 -0800 (PST)
Received: by rachael.franken.de (Postfix, from userid 33) id A8AF71112CEC4; Thu, 11 Dec 2014 15:36:32 +0100 (CET)
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 11 Dec 2014 15:36:32 +0100
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com> <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de> <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com>
Message-ID: <6b6424e96f45f8a35917ed87b2ea65d2@mail-n.franken.de>
X-Sender: tuexen@fh-muenster.de
User-Agent: Roundcube Webmail/0.9.2
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ZwIGCAPNzvYsIJgpMJKZp7qnISQ
Cc: ops-dir@ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 14:36:43 -0000

On 2014-12-11 11:57, Romascanu, Dan (Dan) wrote:
> Ã˜ I'm good with Michael submitting an update addressing the comments
> as discussed in this thread.
> 
> Ã˜
> 
> Ã˜ Thanks,
> 
> Ã˜
> 
> Ã˜ Spencer
> 
> Me too. Can you please send me a note when this happens, so that I do
> not miss the update?
Sure. The updated version is available at
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-prpolicies-06
> 
> Thanks for considering my comments.
Thanks for providing them!

Best regards
Michael
> 
> Regards,
> 
> Dan
> 
> FROM: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com]
>  SENT: Thursday, December 11, 2014 12:10 AM
>  TO: Michael Tuexen
>  CC: Romascanu, Dan (Dan); ops-dir@ietf.org; tsvwg@ietf.org;
> draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org
>  SUBJECT: Re: OPS-DIR review of
> draft-ietf-tsvwg-sctp-prpolicies-05.txt
> 
> From at least one AD :-)
> 
> On Wed, Dec 10, 2014 at 2:52 PM, Michael Tuexen
> <tuexen@fh-muenster.de> wrote:
> 
> On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan) <dromasca@avaya.com>
> wrote:
> 
>  > Hi Michael,
>  >
>  > Thank you for addressing the issues raised in the OPS-DIR review.
>  >
>  > First, please see the disclaimer that I put in my review:
>  >
>  >>> Although this document defines an extension of an existing
> protocol, there
>  >> are no explicit considerations about operations and management.
> The OPS
>  >> and Transport ADs should decide whether this is an issue to be
> addressed
>  >> before the document is approved.
>  >
>  > The OPS-DIR reviews are written to help the OPS ADs with a reading
> of the I-Ds in review from the perspective of the operators using the
> and deploying the new protocols or extensions defined by the document.
> We - the reviewers - believe that the operational and manageability
> issues are important, but it's up to the ADs to decide whether they
> are important enough to require changes in the document, and what
> these changes should be.
>  Hi Dan,
> 
>  understood. But I want to understand your points and possibly address
> them...
> 
>> 
>  > More in-line.
>  >
>  > Regards,
>  >
>  > Dan
>  >
>  >
>  >> -----Original Message-----
>  >> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>  >> Sent: Wednesday, December 10, 2014 1:02 AM
>  >> To: Romascanu, Dan (Dan)
>  >> Cc: ops-dir@ietf.org; tsvwg@ietf.org; draft-ietf-tsvwg-sctp-
>  >> prpolicies.all@tools.ietf.org
>  >> Subject: Re: OPS-DIR review of
> draft-ietf-tsvwg-sctp-prpolicies-05.txt
>  >>
>  >> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan)
> <dromasca@avaya.com>
>  >> wrote:
>  >>
>  >>> I have reviewed this document as part of the Operational
> directorate's
>  >> ongoing effort to review all IETF documents being processed by the
> IESG.
>  >> These comments were written primarily for the benefit of the
> operational
>  >> area directors. Document editors and WG chairs should treat these
>  >> comments just like any other last call comments.
>  >> Hi Dan,
>  >>
>  >> thank you very much for your review. Please see my questions and
>  >> comments in-line.
>  >>
>  >> Best regards
>  >> Michael
>  >>>
>  >>>
>  >>> Summary: Ready with issues
>  >>>
>  >>> Document Ready, but Operational and Management considerations
>  >> missing.
>  >>>
>  >>> As the Abstract says:
>  >>>
>  >>> This document defines two additional policies for the Partial
>  >>> Reliability Extension of the Stream Control Transmission Protocol
>  >>> (PR-SCTP) allowing to limit the number of retransmissions or to
>  >>> prioritize user messages for more efficient send buffer usage.
>  >>> Although this document defines an extension of an existing
> protocol, there
>  >> are no explicit considerations about operations and management.
> The OPS
>  >> and Transport ADs should decide whether this is an issue to be
> addressed
>  >> before the document is approved.
>  >>>
>  >>> Specifically, following the checklists in RFC 5707, Appendix A:
>  >>>
>  >>> - Deployment is not discussed, although there is text that says
> that the
>  >> Limited Retransmissions Policy can be used with data channels in
> the
>  >> WebRTC protocol stack, and that the Priority Policy can be used in
> the IPFIX
>  >> protocol stack
>  >> The introduction says, that "The decision to abandon a user
> message is
>  >> sender side only". So for deploying the additional policies you
> need to
>  >> implement it at the sender side.
>  >
>  > This is not exactly what I meant by deployment. My understanding is
> that the policies defined in this document come to answer some
> specific needs of protocols like IPFIX and WebRTC. Am I correct? If I
> am, I would expect the policies to be deployed where these protocols
> run.
> 
> For IPFIX some of this is discussed in
>  https://tools.ietf.org/html/rfc7011#section-10.2 [1]
>  For RTCWeb is is discussed in
>  
> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1
> [2]
>  Please note that the policies defined here are of general use. So the
> description
>  how to use it will be in the documents describing the use cases.
>  >
>  >>> - Installation and initial setup is not discussed
>  >> We normally don't discuss the installation of the OS (assuming
> that the SCTP
>  >> stack is part of the kernel, which is the case for Linux, FreeBSD
> and Solaris) or
>  >> how to install applications (assuming that the transport stack is
> part of the
>  >> application, which is the case for browsers like Firefox, Chrome
> and Opera).
>  >
>  > Thank you for the clarification. Maybe it would help writing just
> this - the installation of the new capabilities will be part of OS
> upgrades.
>  ... if you use a stack provided by the kernel. If the stack is
> provided by
>  an application, you need to install the application.
>  So it comes down to: You need to install the software which contains
> the SCTP stack you are using.
>  For me, this is obvious. So I'm hesitating to add this. It would be a
> sentence which
>  you can copy to almost every SCTP (or TCP) specification.
> 
>> 
>  >>> - Migration Path does not seem to apply
>  >> Migrating from what? You can just use an implementation at the
> sender side
>  >> and you can operate with every receiver implemening RFC 3758.
>  >
>  > This is OK - that's what I had in mind when I said 'does not apply'
> - so no need to do anything.
>  >
>  >>> - There is information about RFC 3758 being mandatory to
> implement in
>  >> order to implement these extensions
>  >>> - The impact on the network operation is not discussed explicitly
>  >> In the security considerations section we say that the SCTP
> association using
>  >> this extension is not more aggressive than one not using the
> extension.
>  >
>  > OK.
>  >
>  >>> - There are no explicit suggestions about verifying correct
> operations,
>  >> although one can understand that the socket options described in
> sections
>  >> 4.3, 4.4, 4.5 are useful to determine stream specific status,
> association
>  >> specific status, and to get and set the PR-SCTP support
>  >> Are you suggesting to specify test cases? At least this is not
> common right
>  >> now in transport area although it would make sense in my
> opinion...
>  >
>  > OK
>  >
>  >>> - Interoperability does not seem to apply excepting the
> requirement to
>  >> implement RFC 3758
>  >> And that is all what is needed...
>  >
>  > OK
>  >
>  >>> - There is no information about faults or threshold conditions to
> be
>  >> reported
>  >> Not sure what you are expecting here.
>  >
>  > Nothing - this is a point in the 5707 list which does not seem to
> apply.
>  >
>  >>> - Configuration is not discussed, it may not apply, but it would
> be good
>  >> to state this
>  >> Well, configuration is described in detail in the socket API
> section. This is how
>  >> you configure the transport stack.
>  >
>  > OK
>  >
>  >>> - There are no manageability considerations of any kind
>  >> Isn't the socket API what you use to manage the transport stack?
> Or are you
>  >> referring to MIB stuff?
>  >
>  > Whatever is used by operators to perform and verify installation,
> check behavior, and troubleshoot problems.
> 
> Ahh, OK. I don't think an operator would use the socket API for that.
>  If you want to test you transport stack you need to have tests and a
> test tool
>  for running these tests. Up to now, the IETF (at least the transport
> area)
>  hasn't specified tests. Personally, I would really love to do it and
> think
>  that it is very important. But I think this is a decision not limited
> to this particular
>  document, but to (transport) protocols in general. So I leave it up
> to the ADs...
> 
> I'd say the question of test cases has been raised to the attention of
> TSVWG (cc on this thread), and I'd be happy to consider that if they
> think working on that would be a good plan, but I don't think this
> document needs to wait for them to figure that out.
> 
> I'm good with Michael submitting an update addressing the comments as
> discussed in this thread.
> 
> Thanks,
> 
> Spencer
> 
> 
> 
> Links:
> ------
> [1]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7011-23section-2D10.2&amp;d=AAMFaQ&amp;c=BFpWQw8bsuKpl1SgiZH64Q&amp;r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&amp;s=LqjSQkjNGebAvCFgTSNxXQ_e427vOGThVYUIAPMJDgw&amp;e=
> [2]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Drtcweb-2Ddata-2Dchannel-2D12-23section-2D6.1&amp;d=AAMFaQ&amp;c=BFpWQw8bsuKpl1SgiZH64Q&amp;r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&amp;s=nVL3E_6PggjIKyLIIspGt7ZzjVOoGU0fIot986j6yTs&amp;e=


From nobody Thu Dec 11 06:38:03 2014
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2281ACEE4; Thu, 11 Dec 2014 06:38:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 zC7PqO8VMMSN; Thu, 11 Dec 2014 06:37:59 -0800 (PST)
Received: from rachael.franken.de (rachael.franken.de [IPv6:2001:638:a02:a001:21f:d0ff:fe8e:76d3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09F9D1ACEE3; Thu, 11 Dec 2014 06:37:59 -0800 (PST)
Received: by rachael.franken.de (Postfix, from userid 33) id 92F601112CEC6; Thu, 11 Dec 2014 15:37:56 +0100 (CET)
To: gorry@erg.abdn.ac.uk
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 11 Dec 2014 15:37:56 +0100
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <7d7fcc0039f4fe019b8981541c9bdcd2.squirrel@spey.erg.abdn.ac.uk>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C912939@AZ-FFEXMB04.global.avaya.com> <AA1F20D3-B5EA-43F6-84D8-999E359FDFF5@fh-muenster.de> <9904FB1B0159DA42B0B887B7FA8119CA5C92A523@AZ-FFEXMB04.global.avaya.com> <34E7FE23-64C6-4F9D-B10D-C946168C2766@fh-muenster.de> <CAKKJt-cdzypHk+sEYsVU8Bu7Oi3bwygCoa9ZPHnSv3BqhyZAsA@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA5C92B8EF@AZ-FFEXMB04.global.avaya.com> <7d7fcc0039f4fe019b8981541c9bdcd2.squirrel@spey.erg.abdn.ac.uk>
Message-ID: <f09872dccc889774748f29f69f5c7364@mail-n.franken.de>
X-Sender: tuexen@fh-muenster.de
User-Agent: Roundcube Webmail/0.9.2
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Vhj2o3CWhDgDI9OqlHjQOS7lJMI
Cc: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, ops-dir@ietf.org, draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org, tsvwg@ietf.org
Subject: Re: [tsvwg] OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 14:38:01 -0000

On 2014-12-11 12:10, gorry@erg.abdn.ac.uk wrote:
> So, it seems most of this is covered by clear statements that describe
> this as a sender-side only change to the transport protocol of the
> endpoint stack. ... and description and references to examples where
> deployment is expected, etc - I suggest to expand the introduction?
> 
> Michael can you run the changes by me as the document shepherd, so I 
> can
> check that I see the logic and it doesn't potentially  create new 
> issues?
Hi Gorry,

I'm sorry, I already submitted the version. Please have a look at
https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-prpolicies-06
and let me know if they changes are OK for you. If not I can
incorporate your suggested changes.

Best regards
Michael
> 
> Gorry
> 
>> ÃƒËœ  I'm good with Michael submitting an update addressing the comments 
>> as
>> discussed in this thread.
>> 
>> ÃƒËœ
>> 
>> ÃƒËœ  Thanks,
>> 
>> ÃƒËœ
>> 
>> ÃƒËœ  Spencer
>> 
>> Me too. Can you please send me a note when this happens, so that I do 
>> not
>> miss the update?
>> 
>> Thanks for considering my comments.
>> 
>> Regards,
>> 
>> Dan
>> 
>> 
>> From: Spencer Dawkins at IETF [mailto:spencerdawkins.ietf@gmail.com]
>> Sent: Thursday, December 11, 2014 12:10 AM
>> To: Michael Tuexen
>> Cc: Romascanu, Dan (Dan); ops-dir@ietf.org; tsvwg@ietf.org;
>> draft-ietf-tsvwg-sctp-prpolicies.all@tools.ietf.org
>> Subject: Re: OPS-DIR review of draft-ietf-tsvwg-sctp-prpolicies-05.txt
>> 
>> From at least one AD :-)
>> 
>> On Wed, Dec 10, 2014 at 2:52 PM, Michael Tuexen
>> <tuexen@fh-muenster.de<mailto:tuexen@fh-muenster.de>> wrote:
>> On 10 Dec 2014, at 13:23, Romascanu, Dan (Dan)
>> <dromasca@avaya.com<mailto:dromasca@avaya.com>> wrote:
>> 
>>> Hi Michael,
>>> 
>>> Thank you for addressing the issues raised in the OPS-DIR review.
>>> 
>>> First, please see the disclaimer that I put in my review:
>>> 
>>>>> Although this document defines an extension of an existing 
>>>>> protocol,
>>>>> there
>>>> are no explicit considerations about operations and management. The
>>>> OPS
>>>> and Transport ADs should decide whether this is an issue to be
>>>> addressed
>>>> before the document is approved.
>>> 
>>> The OPS-DIR reviews are written to help the OPS ADs with a reading of
>>> the I-Ds in review from the perspective of the operators using the 
>>> and
>>> deploying the new protocols or extensions defined by the document. We 
>>> -
>>> the reviewers - believe that the operational and manageability issues
>>> are important, but it's up to the ADs to decide whether they are
>>> important enough to require changes in the document, and what these
>>> changes should be.
>> Hi Dan,
>> 
>> understood. But I want to understand your points and possibly address
>> them...
>>> 
>>> More in-line.
>>> 
>>> Regards,
>>> 
>>> Dan
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Michael Tuexen
>>>> [mailto:tuexen@fh-muenster.de<mailto:tuexen@fh-muenster.de>]
>>>> Sent: Wednesday, December 10, 2014 1:02 AM
>>>> To: Romascanu, Dan (Dan)
>>>> Cc: ops-dir@ietf.org<mailto:ops-dir@ietf.org>;
>>>> tsvwg@ietf.org<mailto:tsvwg@ietf.org>; draft-ietf-tsvwg-sctp-
>>>> prpolicies.all@tools.ietf.org<mailto:prpolicies.all@tools.ietf.org>
>>>> Subject: Re: OPS-DIR review of 
>>>> draft-ietf-tsvwg-sctp-prpolicies-05.txt
>>>> 
>>>> On 26 Nov 2014, at 13:33, Romascanu, Dan (Dan)
>>>> <dromasca@avaya.com<mailto:dromasca@avaya.com>>
>>>> wrote:
>>>> 
>>>>> I have reviewed this document as part of the Operational
>>>>> directorate's
>>>> ongoing effort to review all IETF documents being processed by the
>>>> IESG.
>>>> These comments  were written primarily for the benefit of the
>>>> operational
>>>> area directors.  Document editors and WG chairs should treat these
>>>> comments just like any other last call comments.
>>>> Hi Dan,
>>>> 
>>>> thank you very much for your review. Please see my questions and
>>>> comments in-line.
>>>> 
>>>> Best regards
>>>> Michael
>>>>> 
>>>>> 
>>>>> Summary: Ready with issues
>>>>> 
>>>>> Document Ready, but Operational and Management considerations
>>>> missing.
>>>>> 
>>>>> As the Abstract says:
>>>>> 
>>>>>   This document defines two additional policies for the Partial
>>>>>   Reliability Extension of the Stream Control Transmission Protocol
>>>>>   (PR-SCTP) allowing to limit the number of retransmissions or to
>>>>>   prioritize user messages for more efficient send buffer usage.
>>>>> Although this document defines an extension of an existing 
>>>>> protocol,
>>>>> there
>>>> are no explicit considerations about operations and management. The
>>>> OPS
>>>> and Transport ADs should decide whether this is an issue to be
>>>> addressed
>>>> before the document is approved.
>>>>> 
>>>>> Specifically, following the checklists in RFC 5707, Appendix A:
>>>>> 
>>>>> -       Deployment is not discussed, although there is text that 
>>>>> says
>>>>> that the
>>>> Limited Retransmissions Policy can be used with data channels in the
>>>> WebRTC protocol stack, and that the Priority Policy can be used in 
>>>> the
>>>> IPFIX
>>>> protocol stack
>>>> The introduction says, that "The decision to abandon a user message 
>>>> is
>>>> sender side only". So for deploying the additional policies you need
>>>> to
>>>> implement it at the sender side.
>>> 
>>> This is not exactly what I meant by deployment. My understanding is 
>>> that
>>> the policies defined in this document come to answer some specific 
>>> needs
>>> of protocols like IPFIX and WebRTC. Am I correct? If I am, I would
>>> expect the policies to be deployed where these protocols run.
>> For IPFIX some of this is discussed in
>> https://tools.ietf.org/html/rfc7011#section-10.2<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7011-23section-2D10.2&d=AAMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&s=LqjSQkjNGebAvCFgTSNxXQ_e427vOGThVYUIAPMJDgw&e=>
>> For RTCWeb is is discussed in
>> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Drtcweb-2Ddata-2Dchannel-2D12-23section-2D6.1&d=AAMFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=6cUQU7WzGxVzLIHAs0xxQPmF6uxX5BY1uBQciZGTCcc&s=nVL3E_6PggjIKyLIIspGt7ZzjVOoGU0fIot986j6yTs&e=>
>> Please note that the policies defined here are of general use. So the
>> description
>> how to use it will be in the documents describing the use cases.
>>> 
>>>>> -       Installation and initial setup is not discussed
>>>> We normally don't discuss the installation of the OS (assuming that 
>>>> the
>>>> SCTP
>>>> stack is part of the kernel, which is the case for Linux, FreeBSD 
>>>> and
>>>> Solaris) or
>>>> how to install applications (assuming that the transport stack is 
>>>> part
>>>> of the
>>>> application, which is the case for browsers like Firefox, Chrome and
>>>> Opera).
>>> 
>>> Thank you for the clarification. Maybe it would help writing just 
>>> this -
>>> the installation of the new capabilities will be part of OS upgrades.
>> ... if you use a stack provided by the kernel. If the stack is 
>> provided
>> by
>> an application, you need to install the application.
>> So it comes down to: You need to install the software which contains 
>> the
>> SCTP stack you are using.
>> For me, this is obvious. So I'm hesitating to add this. It would be a
>> sentence which
>> you can copy to almost every SCTP (or TCP) specification.
>>> 
>>>>> -       Migration Path does not seem to apply
>>>> Migrating from what? You can just use an implementation at the 
>>>> sender
>>>> side
>>>> and you can operate with every receiver implemening RFC 3758.
>>> 
>>> This is OK - that's what I had in mind when I said 'does not apply' - 
>>> so
>>> no need to do anything.
>>> 
>>>>> -       There is information about RFC 3758 being mandatory to
>>>>> implement in
>>>> order to implement these extensions
>>>>> -       The impact on the network operation is not discussed
>>>>> explicitly
>>>> In the security considerations section we say that the SCTP 
>>>> association
>>>> using
>>>> this extension is not more aggressive than one not using the
>>>> extension.
>>> 
>>> OK.
>>> 
>>>>> -       There are no explicit suggestions about verifying correct
>>>>> operations,
>>>> although one can understand that the socket options described in
>>>> sections
>>>> 4.3, 4.4, 4.5 are useful to determine stream specific status,
>>>> association
>>>> specific status, and to get and set the PR-SCTP support
>>>> Are you suggesting to specify test cases? At least this is not 
>>>> common
>>>> right
>>>> now in transport area although it would make sense in my opinion...
>>> 
>>> OK
>>> 
>>>>> -       Interoperability does not seem to apply excepting the
>>>>> requirement to
>>>> implement RFC 3758
>>>> And that is all what is needed...
>>> 
>>> OK
>>> 
>>>>> -       There is no information about faults or threshold 
>>>>> conditions
>>>>> to be
>>>> reported
>>>> Not sure what you are expecting here.
>>> 
>>> Nothing - this is a point in the 5707 list which does not seem to
>>> apply.
>>> 
>>>>> -       Configuration is not discussed, it may not apply, but it 
>>>>> would
>>>>> be good
>>>> to state this
>>>> Well, configuration is described in detail in the socket API 
>>>> section.
>>>> This is how
>>>> you configure the transport stack.
>>> 
>>> OK
>>> 
>>>>> -       There are no manageability considerations of any kind
>>>> Isn't the socket API what you use to manage the transport stack? Or 
>>>> are
>>>> you
>>>> referring to MIB stuff?
>>> 
>>> Whatever is used by operators to perform and verify installation, 
>>> check
>>> behavior, and troubleshoot problems.
>> Ahh, OK. I don't think an operator would use the socket API for that.
>> If you want to test you transport stack you need to have tests and a 
>> test
>> tool
>> for running these tests. Up to now, the IETF (at least the transport
>> area)
>> hasn't specified tests. Personally, I would really love to do it and
>> think
>> that it is very important. But I think this is a decision not limited 
>> to
>> this particular
>> document, but to (transport) protocols in general. So I leave it up to 
>> the
>> ADs...
>> 
>> I'd say the question of test cases has been raised to the attention of
>> TSVWG (cc on this thread), and I'd be happy to consider that if they 
>> think
>> working on that would be a good plan, but I don't think this document
>> needs to wait for them to figure that out.
>> 
>> I'm good with Michael submitting an update addressing the comments as
>> discussed in this thread.
>> 
>> Thanks,
>> 
>> Spencer
>> 
>> 


From nobody Thu Dec 11 07:48:27 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05E81ACF1B for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 07:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zHRKmF4t3cFm for <tsvwg@ietfa.amsl.com>; Thu, 11 Dec 2014 07:48:15 -0800 (PST)
Received: from ortiz.unizar.es (ortiz.unizar.es [155.210.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23A921ACF24 for <tsvwg@ietf.org>; Thu, 11 Dec 2014 07:48:13 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by ortiz.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id sBBFm8E5003296 for <tsvwg@ietf.org>; Thu, 11 Dec 2014 16:48:08 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: <tsvwg@ietf.org>
Date: Thu, 11 Dec 2014 16:48:16 +0100
Message-ID: <002401d01559$e13abca0$a3b035e0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01D01562.4300AB40"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAVWREaHO0zT/i8TgiFKeJ6e3aYog==
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Ulo-BP3yGELTMSeWTBWL7mPjQnE
Subject: [tsvwg] Some results obtained with TCM
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 15:48:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0025_01D01562.4300AB40
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
Today I have performed a small battery of tests with the TCM =
implementation (https://github.com/TCM-TF/simplemux/). We hope we will =
be able to test it in other scenarios and with better machines soon.
=20
Multiplexing and compressing with ROHC 10 VoIP flows (G729a with 2 =
samples per packet):
Average BW reduction: 36.50%
Average PPS reduction: 78.83%
Average multiplexing delay: 4123.33 us
stdev of the multiplexing delay: 3845.13 us
=20
Multiplexing and compressing with ROHC 10 flows of Quake3 (a First =
Person Shooter game)
Average BW reduction: 22.23%
Average PPS reduction: 92.99%
Average multiplexing delay: 5148.72 us
stdev of the multiplexing delay: 2991.43 us
=20
=20
You can find the full report (with graphs and details) here: =
https://github.com/TCM-TF/simplemux/blob/develop/Simplemux_VoIP =
<https://github.com/TCM-TF/simplemux/blob/develop/Simplemux_VoIP&Quake3_r=
esults_v1.pdf?raw=3Dtrue> &Quake3_results_v1.pdf?raw=3Dtrue
=20
Best regards,
=20
Jose
=20
De: tsvwg [mailto:tsvwg-bounces@ietf.org] En nombre de Jose Saldana
Enviado el: jueves, 11 de diciembre de 2014 11:01
Para: tsvwg@ietf.org
CC: 'Gorry Fairhurst'; 'David Fl=C3=B3rez Rodr=C3=ADguez'; 'Manuel =
N=C3=BA=C3=B1ez Sanz'; 'Juan Antonio Castell Luc=C3=ADa'; 'Gonzalo =
Camarillo'; Martin Stiemerling; 'Fernando Pascual Blanco'; 'Dan Wing =
(dwing)'; 'Michael Ramalho (mramalho)'
Asunto: [tsvwg] New version of the TCM drafts
=20
Hi all,
=20
We have just submitted new versions of the two TCM drafts:
=20
- Tunneling Compressing and Multiplexing (TCM) Traffic Flows. Reference =
Model. draft-saldana-tsvwg-tcmtf-08
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/
=20
- Delay Limits and Multiplexing Policies to be employed with Tunneling =
Compressing and Multiplexing Traffic Flows. =
draft-suznjevic-tsvwg-mtd-tcmtf-04
http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/
=20
In addition, yesterday I submitted another draft about Simplemux =
(http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/), a =
multiplexing protocol simpler than PPPMux (I will send another e-mail =
explaining it).
=20
We have built an implementation of TCM over Simplemux =
(https://github.com/TCM-TF/simplemux), and we will soon report the =
results of some tests we are planning.
=20
Best regards,
=20
Jose Saldana
PS: These are some of the improvements:
- keywords have been added
    multiplexing
    header compression
    optimization
    small-packet flows
=20
- We talk about =E2=80=9CTunneling, Compressing and Multiplexing =
(TCM)=E2=80=9D instead of =E2=80=9CTunneling Compressed and Multiplexed =
Traffic Flows (TCM-TF)=E2=80=9D. It is a bit confusing if we talk about =
TCM in some places and TCM-TF in others. In addition, TCM is very easy =
to remember.
=20
- We have improved the abstract and the introduction, talking about =
=E2=80=9Coptimization=E2=80=9D, =E2=80=9Csmall-packet flows=E2=80=9D =
here and there.
=20
- We have updated the reference to COAP (it is now an RFC and it was a =
draft some months ago).
=20
- We have added a reference for supporting the statement saying that =
routers have a limit in the number of pps they can manage.
=20
- We have modified the titles of some subsections.
=20

------=_NextPart_000_0025_01D01562.4300AB40
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DProgId content=3DWord.Document><meta name=3DGenerator =
content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D01562.419A3D70"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloCorreo17
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.EstiloCorreo18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'>Hi <span =
class=3DSpellE>all</span>,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Today I have performed =
a small battery of tests with the TCM implementation (<a =
href=3D"https://github.com/TCM-TF/simplemux/">https://github.com/TCM-TF/s=
implemux/</a>). We hope we will be able to test it in other scenarios =
and with better machines soon.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Multiplexing and =
compressing with ROHC 10 VoIP flows (G729a with 2 samples per =
packet):<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average BW reduction: =
36.50%<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average PPS reduction: =
78.83%<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average multiplexing delay: 4123.33 =
us<o:p></o:p></span></p><p class=3DMsoNormal><span class=3DSpellE><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>stdev</span></span><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'> of the multiplexing =
delay: 3845.13 us<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Multiplexing and =
compressing with ROHC 10 flows of Quake3 (a First Person Shooter =
game)<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average BW reduction: =
22.23%<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average PPS reduction: =
92.99%<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Average multiplexing delay: 5148.72 =
us<o:p></o:p></span></p><p class=3DMsoNormal><span class=3DSpellE><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>stdev</span></span><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'> of the multiplexing =
delay: 2991.43 us<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>You can find the full =
report (with graphs and details) here: <a =
href=3D"https://github.com/TCM-TF/simplemux/blob/develop/Simplemux_VoIP&a=
mp;Quake3_results_v1.pdf?raw=3Dtrue">https://github.com/TCM-TF/simplemux/=
blob/develop/Simplemux_VoIP&amp;Quake3_results_v1.pdf?raw=3Dtrue</a><o:p>=
</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-fareast-language:ES;mso-no-proof:yes'>Jose<o:p><=
/o:p></span></p></div><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-fareast-language:ES'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-fareast-language:ES'> tsvwg =
[mailto:tsvwg-bounces@ietf.org] <b>En nombre de </b>Jose =
Saldana<br><b>Enviado el:</b> jueves, 11 de diciembre de 2014 =
11:01<br><b>Para:</b> tsvwg@ietf.org<br><b>CC:</b> 'Gorry Fairhurst'; =
'David Fl=C3=B3rez Rodr=C3=ADguez'; 'Manuel N=C3=BA=C3=B1ez Sanz'; 'Juan =
Antonio Castell Luc=C3=ADa'; 'Gonzalo Camarillo'; Martin Stiemerling; =
'Fernando Pascual Blanco'; 'Dan Wing (dwing)'; 'Michael Ramalho =
(mramalho)'<br><b>Asunto:</b> [tsvwg] New version of the TCM =
drafts<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'>Hi all,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>We have just submitted =
new versions of the two TCM drafts:<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- Tunneling =
Compressing and Multiplexing (TCM) Traffic Flows. Reference Model. =
draft-saldana-tsvwg-tcmtf-08<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/">http:=
//datatracker.ietf.org/doc/draft-saldana-tsvwg-tcmtf/</a><o:p></o:p></spa=
n></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- Delay Limits and =
Multiplexing Policies to be employed with Tunneling Compressing and =
Multiplexing Traffic Flows. =
draft-suznjevic-tsvwg-mtd-tcmtf-04<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><a =
href=3D"http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/"=
>http://datatracker.ietf.org/doc/draft-suznjevic-tsvwg-mtd-tcmtf/</a><o:p=
></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>In addition, yesterday =
I submitted another draft about Simplemux (<a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/">h=
ttp://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/</a>), a =
multiplexing protocol simpler than PPPMux (I will send another e-mail =
explaining it).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>We have built an =
implementation of TCM over Simplemux (<a =
href=3D"https://github.com/TCM-TF/simplemux">https://github.com/TCM-TF/si=
mplemux</a>), and we will soon report the results of some tests we are =
planning.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US;mso-fareast-language:ES;mso-=
no-proof:yes'>Jose Saldana<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>PS: These are some of =
the improvements:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- keywords have been =
added<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 =
</span>multiplexing<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 </span>header =
compression<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 =
</span>optimization<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'><span =
style=3D'mso-spacerun:yes'>=C2=A0=C2=A0=C2=A0 </span>small-packet =
flows<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We talk about =
=E2=80=9CTunneling, Compressing and Multiplexing (TCM)=E2=80=9D instead =
of =E2=80=9CTunneling Compressed and Multiplexed Traffic Flows =
(TCM-TF)=E2=80=9D. It is a bit confusing if we talk about TCM in some =
places and TCM-TF in others. In addition, TCM is very easy to =
remember.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have improved the =
abstract and the introduction, talking about =
=E2=80=9Coptimization=E2=80=9D, =E2=80=9Csmall-packet flows=E2=80=9D =
here and there.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have updated the =
reference to COAP (it is now an RFC and it was a draft some months =
ago).<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have added a =
reference for supporting the statement saying that routers have a limit =
in the number of pps they can manage.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New =
Roman";color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D;mso-ansi-language:EN-US'>- We have modified the =
titles of some subsections.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p></div></div=
></body></html>
------=_NextPart_000_0025_01D01562.4300AB40--



From nobody Mon Dec 15 05:32:22 2014
Return-Path: <dromasca@avaya.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB7D1A6EED; Mon, 15 Dec 2014 05:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4MjDhKdnC6Ik; Mon, 15 Dec 2014 05:32:17 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 021E61A3BA3; Mon, 15 Dec 2014 05:32:16 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvYFAGnijlTGmAcV/2dsb2JhbABagkMhIiIwWASzEwEBAQEBAQaSFx0BCIVzAoEaFgEBAQEBAXyEDgEBAxIbTBIBFQcOViYBBAENDRqICgEMsWqgZwEBAQEBAQEDAQEBAQEBAQEBAQEXhgCJQSANBBCCJAxAHYETBYkVgxeBVoM+hjwwgi6CJosoIoNsbgEBAYFCfgEBAQ
X-IronPort-AV: E=Sophos; i="5.07,579,1413259200"; d="scan'208,217"; a="99159696"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 15 Dec 2014 08:32:08 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 15 Dec 2014 08:32:05 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.03.0174.001; Mon, 15 Dec 2014 14:31:59 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-tsvwg-port-use-06.txt
Thread-Index: AdAYa39LlL4BZEPKTtyGV5c4G3F4eg==
Date: Mon, 15 Dec 2014 13:31:57 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA5C930602@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.47]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C930602AZFFEXMB04globa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/KtPcYLdY3jP57hNtY8KabrREVCY
Cc: "draft-ietf-tsvwg-port-use.all@tools.ietf.org" <draft-ietf-tsvwg-port-use.all@tools.ietf.org>
Subject: [tsvwg] Gen-ART review of draft-ietf-tsvwg-port-use-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 13:32:20 -0000

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C930602AZFFEXMB04globa_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. For background on

Gen-ART, please see the FAQ at



<https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.org_=
area_gen_trac_wiki_GenArtfaq&d=3DAAICAg&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dz=
GxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DsITgTP84yGaHOlBBZiB9yr8yJ3saUDz=
_ezXr0_7zXR0&s=3DToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&e=3D <https://=
urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.org_area_gen_=
trac_wiki_GenArtfaq&d=3DAAICAg&c=3DBFpWQw8bsuKpl1SgiZH64Q&r=3DI4dzGxR31OcNX=
CJfQzvlsiLQfucBXRucPvdrphpBsFA&m=3DsITgTP84yGaHOlBBZiB9yr8yJ3saUDz_ezXr0_7z=
XR0&s=3DToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&e=3D%20> >.



Please resolve these comments along with any other Last Call comments

you may receive.



Document: draft-ietf-tsvwg-port-use-06.txt

Reviewer: Dan Romascanu

Review Date: 12/15/14

IETF LC End Date: 12/22/14

IESG Telechat date: not yet



Summary: Ready with issues



The document is very clear and well written. I suggest that the author addr=
esses the couple of issues raised here which are not show stoppers but thei=
r resolution can further improve the quality of the document.



Major issues:



Minor issues:



1.       The abstract says:



=D8  This document provides recommendations to application and service
   designers on how to use the transport protocol port number space.



Section 1. Introduction says:



=D8     This document provides information and advice to system designers o=
n
   the use of transport port numbers.



In Section 7.2 'system designers' appears again:



=D8  ... system designers cannot yet rely on their presence.

=D8



I do not like 'system designers' because this term is vague and not defined=
. Beyond the inconsistency in terminology which is obvious in page 2, there=
 is also room for confusion because 'system' is used with a completely diff=
erent meaning as in 'system port'.



I suspect that  in section 1 'system designers' is meant to be an alias for=
 the 'application and service designers' from the intro, while in section 7=
.2 it's rather meant to be an alias for 'network designers'. If I am right =
I suggest replacing in both places.



2.       The privacy considerations are not mentioned at all in the documen=
t. It seems to me that detecting in clear the port numbers and mapping this=
 information to the source/destination addresses can provide information ab=
out specific hosts running specific services. I believe that this aspect sh=
ould be mentioned either in the security considerations section or in a sep=
arate privacy considerations section, and in section 5, together with the p=
aragraphs that mentions the capability of intermediate devices to monitor a=
vailable services, monitor or intercept traffic.







Nits/editorial comments:








--_000_9904FB1B0159DA42B0B887B7FA8119CA5C930602AZFFEXMB04globa_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:731273424;
	mso-list-type:hybrid;
	mso-list-template-ids:498335788 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1661352275;
	mso-list-type:hybrid;
	mso-list-template-ids:1500169756 -2109865764 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0D8;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:Arial;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on<o:p></o:p></p>
<p class=3D"MsoPlainText">Gen-ART, please see the FAQ at<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"https://urldefense.proofpoint.com/=
v2/url?u=3Dhttp-3A__wiki.tools.ietf.org_area_gen_trac_wiki_GenArtfaq&amp;d=
=3DAAICAg&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR31OcNXCJfQzvlsiLQfu=
cBXRucPvdrphpBsFA&amp;m=3DsITgTP84yGaHOlBBZiB9yr8yJ3saUDz_ezXr0_7zXR0&amp;s=
=3DToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&amp;e=3D%20">https://urldefe=
nse.proofpoint.com/v2/url?u=3Dhttp-3A__wiki.tools.ietf.org_area_gen_trac_wi=
ki_GenArtfaq&amp;d=3DAAICAg&amp;c=3DBFpWQw8bsuKpl1SgiZH64Q&amp;r=3DI4dzGxR3=
1OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&amp;m=3DsITgTP84yGaHOlBBZiB9yr8yJ3saUDz=
_ezXr0_7zXR0&amp;s=3DToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&amp;e=3D
</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please resolve these comments along with any othe=
r Last Call comments<o:p></o:p></p>
<p class=3D"MsoPlainText">you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-tsvwg-port-use-06.txt<o:p></=
o:p></p>
<p class=3D"MsoPlainText">Reviewer: Dan Romascanu<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 12/15/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 12/22/14<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: not yet<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: Ready with issues<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">The document is very clear and well written. I su=
ggest that the author addresses the couple of issues raised here which are =
not show stoppers but their resolution can further improve the quality of t=
he document.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>The abstract says: <o:p></=
o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=D8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-family:&quot;Courier New&quot;">This document provides recommendations to =
application and service<br>
&nbsp;&nbsp; designers on how to use the transport protocol port number spa=
ce.</span><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt">Section 1. Introduct=
ion says: <o:p>
</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=D8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;This document provides i=
nformation and advice to system designers on<br>
&nbsp;&nbsp; the use of transport port numbers. </span><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt">In Section 7.2 &#821=
6;system designers&#8217; appears again:
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=D8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span>&#8230; <span style=
=3D"font-family:&quot;Courier New&quot;">
system designers cannot yet rely on their presence.</span><o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l1 level1 lfo2">
<![if !supportLists]><span style=3D"font-family:Wingdings"><span style=3D"m=
so-list:Ignore">=D8<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><o:p>&nbsp;</o:p></=
p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I do not like &#8216;system designers&#8217; beca=
use this term is vague and not defined. Beyond the inconsistency in termino=
logy which is obvious in page 2, there is also room for confusion because &=
#8216;system&#8217; is used with a completely different meaning
 as in &#8216;system port&#8217;. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I suspect that &nbsp;in section 1 &#8216;system d=
esigners&#8217; is meant to be an alias for the &#8216;application and serv=
ice designers&#8217; from the intro, while in section 7.2 it&#8217;s rather=
 meant to be an alias for &#8216;network designers&#8217;. If I am right I =
suggest
 replacing in both places. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>The privacy considerations=
 are not mentioned at all in the document. It seems to me that detecting in=
 clear the port numbers and mapping this information to the source/destinat=
ion addresses can provide information
 about specific hosts running specific services. I believe that this aspect=
 should be mentioned either in the security considerations section or in a =
separate privacy considerations section, and in section 5, together with th=
e paragraphs that mentions the capability
 of intermediate devices to monitor available services, monitor or intercep=
t traffic.
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt"><o:p>&nbsp;</o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_9904FB1B0159DA42B0B887B7FA8119CA5C930602AZFFEXMB04globa_--


From nobody Mon Dec 15 08:58:44 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDED1A86E0; Mon, 15 Dec 2014 08:58:40 -0800 (PST)
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] autolearn=ham
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 VUt90cNfJQzO; Mon, 15 Dec 2014 08:58:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C48741A7D85; Mon, 15 Dec 2014 08:58:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141215165838.31657.16907.idtracker@ietfa.amsl.com>
Date: Mon, 15 Dec 2014 08:58:38 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/TLveA2_vDghqgUA5pXaw0d_IMaE
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 16:58:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : UDP Usage Guidelines
        Authors         : Lars Eggert
                          Godred Fairhurst
                          Greg Shepherd
	Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
	Pages           : 37
	Date            : 2014-12-15

Abstract:
   The User Datagram Protocol (UDP) provides a minimal message-passing
   transport that has no inherent congestion control mechanisms.
   Because congestion control is critical to the stable operation of the
   Internet, applications and other protocols that choose to use UDP as
   an Internet transport must employ mechanisms to prevent congestion
   collapse and to establish some degree of fairness with concurrent
   traffic.  They may also need to implement additional mechanisms,
   depending on how they use UDP.

   This document provides guidelines on the use of UDP for the designers
   of applications, tunnels and other protocols that use UDP.
   Congestion control guidelines are a primary focus, but the document
   also provides guidance on other topics, including message sizes,
   reliability, checksums, and middlebox traversal.

   If published as an RFC, this document will obsolete RFC5405.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Dec 16 18:16:15 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACBE1A0266; Tue, 16 Dec 2014 18:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 7y2TtUUOiPlb; Tue, 16 Dec 2014 18:16:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCA41A0140; Tue, 16 Dec 2014 18:15:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2D9FC18047D; Tue, 16 Dec 2014 18:15:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141217021525.2D9FC18047D@rfc-editor.org>
Date: Tue, 16 Dec 2014 18:15:25 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/VCSqUCsTpYYhiOtSMSqGFYMKRmI
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [tsvwg] RFC 7417 on Extensions to Generic Aggregate RSVP for IPv4 and IPv6 Reservations over Pre-Congestion Notification (PCN) Domains
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 02:16:13 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7417

        Title:      Extensions to Generic Aggregate RSVP 
                    for IPv4 and IPv6 Reservations over 
                    Pre-Congestion Notification (PCN) Domains 
        Author:     G. Karagiannis, A. Bhargava
        Status:     Experimental
        Stream:     IETF
        Date:       December 2014
        Mailbox:    georgios.karagiannis@huawei.com, 
                    anuragb@cisco.com
        Pages:      36
        Characters: 79227
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-rsvp-pcn-11.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7417.txt

This document specifies extensions to Generic Aggregate RSVP
(RFC 4860) for support of the Pre-Congestion Notification (PCN)
Controlled Load (CL) and Single Marking (SM) edge behaviors over
a Diffserv cloud using PCN.

This document is a product of the Transport Area Working Group Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Wed Dec 17 01:41:15 2014
Return-Path: <jsaldana@unizar.es>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D5D1A6FBE for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 01:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UwL78A2_FHtU for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 01:41:05 -0800 (PST)
Received: from huecha.unizar.es (huecha.unizar.es [155.210.1.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE6D51A6FB7 for <tsvwg@ietf.org>; Wed, 17 Dec 2014 01:41:03 -0800 (PST)
Received: from usuarioPC (gtc1pc12.cps.unizar.es [155.210.158.17]) by huecha.unizar.es (8.13.8/8.13.8/Debian-3) with ESMTP id sBH9evCb015786; Wed, 17 Dec 2014 10:40:57 +0100
From: "Jose Saldana" <jsaldana@unizar.es>
To: "'FERNANDO PASCUAL BLANCO'" <fernando.pascualblanco@telefonica.com>, <tsvwg@ietf.org>
References: <00fa01d0152a$c8f60340$5ae209c0$@unizar.es> <AM3PR06MB45275A79D2297EB88D0D6D0E06D0@AM3PR06MB452.eurprd06.prod.outlook.com>
In-Reply-To: <AM3PR06MB45275A79D2297EB88D0D6D0E06D0@AM3PR06MB452.eurprd06.prod.outlook.com>
Date: Wed, 17 Dec 2014 10:41:01 +0100
Message-ID: <00d101d019dd$92001490$b6003db0$@unizar.es>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D2_01D019E5.F3C67860"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJarJhu0LMuKTpzrxByEFlAYB+QmgKMgTO5m2nyoEA=
Content-Language: es
X-Mail-Scanned: Criba 2.0 + Clamd & Bogofilter
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/SOyMW0rminIwcLuR4So5BmEFAdA
Subject: Re: [tsvwg] A new draft submitted to tsvwg: Simplemux
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 09:41:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00D2_01D019E5.F3C67860
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Fernando.
=20
> - Multiplexing layer 3 packets in layer 2 frames?
=20
My idea is that this is an IETF draft, so the protocols considered are =
those defined by IANA: =
http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
=20
The "protocol" field to be included in Simplemux would be 8 bits long, =
in my opinion. This would not be the =E2=80=9CEtherType=E2=80=9D field =
of the Ethernet frame (16 bits long): =
http://en.wikipedia.org/wiki/EtherType.
=20
However, if someone thinks a 16 bytes protocol field could be =
interesting, we can also consider it as an option (with a bit indicating =
it in the first header).
=20
=20
> - Multiplexing layer 3 packets in layer 3 packets?
=20
This would allow these kind of things, if the =E2=80=9Cmultiplexing =
protocol=E2=80=9D is IP:
=20
- encapsulating a number of IP packets in an IP packet: Encapsulated =
Protocol number=3D4 (IPv4 encapsulation, RFC2003)
=20
- Encapsulating a number of Transport Segments in an IP packet (this =
would be equivalent to TMux, RFC1692, =
https://tools.ietf.org/html/rfc1692 ). Encapsulated Protocol number=3D6 =
(TCP, RFC793)
=20
- Encapsulating a number of Ethernet Frames in an IP datagram: =
Encapsulated Protocol number=3D97  ETHERIP, Ethernet-within-IP =
Encapsulation, RFC3378
=20
=20
> Multiplexing layer 3 packets in layer 4 datagrams?
=20
If the =E2=80=9Cmultiplexing protocol=E2=80=9D is UDP, it would also =
make sense: this would avoid the need for a new =
=E2=80=9Cprotocol=E2=80=9D number. The two extremes would just need to =
agree on a port number. In fact, this is what is done in the =
implementation.  <https://github.com/TCM-TF/simplemux> =
https://github.com/TCM-TF/simplemux=20
=20
Best regards,
=20
Jose
=20
De: FERNANDO PASCUAL BLANCO =
[mailto:fernando.pascualblanco@telefonica.com]=20
Enviado el: mi=C3=A9rcoles, 17 de diciembre de 2014 9:56
Para: Jose Saldana; tsvwg@ietf.org
Asunto: RE: [tsvwg] A new draft submitted to tsvwg: Simplemux
=20
Hi Jose,
=20
What multiplexing and what multiplexed protocols are you considering =
here? Are you focused on a determined protocol layer options? Or maybe =
you are defining something generic?
For example:
=20
- Multiplexing layer 3 packets in layer 2 frames?
- Multiplexing layer 3 packets in layer 3 packets?
- Multiplexing layer 3 packets in layer 4 datagrams?
=20
More options?
=20
Thanks!
=20
Fernando=20
=20
From: tsvwg [ <mailto:tsvwg-bounces@ietf.org> =
mailto:tsvwg-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: jueves, 11 de diciembre de 2014 11:11
To:  <mailto:tsvwg@ietf.org> tsvwg@ietf.org
Subject: [tsvwg] A new draft submitted to tsvwg: Simplemux
=20
Hi all,
=20
This is an Internet Draft I submitted yesterday to tsvwg:
 =
<http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?include_t=
ext=3D1> =
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?include_te=
xt=3D1
=20
Simplemux could be seen as a generic protocol for multiplexing any =
protocol on any other protocol. The initial idea was: could this be used =
instead of PPPMux in TCM? However, I think it may have more fields of =
application.
=20
The idea is similar to that of PPPMux (RFC3153). However, PPP, and L2TP =
in turn, are not required, thus reducing complexity:
=20
| Ext hdr || Mux hdr | packet || Mux hdr | packet || ...||
=20
It is different from TMux [RFC1692], because TMux  combines multiple =
short transport segments, but not full packets, so it works between the =
same pair of machines.  However, there are scenarios where a number of =
low-efficiency flows share a common path, but they do not travel between =
the same pair of machines. =20
=20
A =E2=80=9CProtocol=E2=80=9D number should be requested to IANA for =
saying in the external header that Simplemux is inside. Each Mux header =
would include another =E2=80=9CProtocol=E2=80=9D field, so it would =
permit the multiplexing of different packets in the same bundle: IPv4, =
IPv6, ROHC, etc.
=20
If you could have a look to the draft and send your comments, it would =
be fine.
=20
An implementation of Simplemux using IP/UDP as the multiplexing =
(external) protocol and IP or ROHC as the multiplexed protocol can be =
found here:
 <https://github.com/TCM-TF/simplemux> =
https://github.com/TCM-TF/simplemux
=20
=20
Thanks in advance!
=20
Jose
=20
=20
  _____ =20


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, =
puede contener informaci=C3=B3n privilegiada o confidencial y es para =
uso exclusivo de la persona o entidad de destino. Si no es usted. el =
destinatario indicado, queda notificado de que la lectura, =
utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede =
estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha recibido =
este mensaje por error, le rogamos que nos lo comunique inmediatamente =
por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.

The information contained in this transmission is privileged and =
confidential information intended only for the use of the individual or =
entity named above. If the reader of this message is not the intended =
recipient, you are hereby notified that any dissemination, distribution =
or copying of this communication is strictly prohibited. If you have =
received this transmission in error, do not read it. Please immediately =
reply to the sender that you have received this communication in error =
and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu =
destinat=C3=A1rio, pode conter informa=C3=A7=C3=A3o privilegiada ou =
confidencial e =C3=A9 para uso exclusivo da pessoa ou entidade de =
destino. Se n=C3=A3o =C3=A9 vossa senhoria o destinat=C3=A1rio indicado, =
fica notificado de que a leitura, utiliza=C3=A7=C3=A3o, =
divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=C3=A7=C3=A3o pode =
estar proibida em virtude da legisla=C3=A7=C3=A3o vigente. Se recebeu =
esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente =
por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o

------=_NextPart_000_00D2_01D019E5.F3C67860
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DProgId content=3DWord.Document><meta name=3DGenerator =
content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D019E5.EF7E6E70"><link rel=3DEdit-Time-Data =
href=3D"cid:editdata.mso"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>ES</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Texto sin formato Car";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Arial","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;
	mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"Texto de globo Car";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-font-family:Calibri;}
span.TextosinformatoCar
	{mso-style-name:"Texto sin formato Car";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Texto sin formato";
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#1F497D;
	mso-fareast-language:EN-US;}
span.TextodegloboCar
	{mso-style-name:"Texto de globo Car";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Texto de globo";
	mso-ansi-font-size:8.0pt;
	mso-bidi-font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-ascii-font-family:Tahoma;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Tahoma;
	mso-bidi-font-family:Tahoma;}
span.EstiloCorreo21
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:#1F497D;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;
	mso-style-unhide:no;}
span.EstiloCorreo23
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	color:#1F497D;}
span.EstiloCorreo24
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Arial","sans-serif";
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Tabla normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DES link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:35.4pt'><div =
class=3DWordSection1><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>Hi, Fernando.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><b style=3D'mso-bidi-font-weight:normal'><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>&gt; - Multiplexing layer =
3 packets in layer 2 frames?<o:p></o:p></span></b></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>My idea is that this is an IETF draft, =
so the protocols considered are those defined by IANA: <a =
href=3D"http://www.iana.org/assignments/protocol-numbers/protocol-numbers=
.xhtml">http://www.iana.org/assignments/protocol-numbers/protocol-numbers=
.xhtml</a><o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>The &quot;protocol&quot; field to be =
included in <span class=3DSpellE>Simplemux</span> would be 8 bits long, =
in my opinion. This would not be the =E2=80=9C<span =
class=3DSpellE>EtherType</span>=E2=80=9D field of the Ethernet frame (16 =
bits long): <a =
href=3D"http://en.wikipedia.org/wiki/EtherType">http://en.wikipedia.org/w=
iki/EtherType</a>.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>However, if someone thinks a 16 bytes =
protocol field could be interesting, we can also consider it as an =
option (with a bit indicating it in the first =
header).<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><b style=3D'mso-bidi-font-weight:normal'><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>&gt; - Multiplexing layer =
3 packets in layer 3 packets?<o:p></o:p></span></b></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>This would allow these kind of things, =
if the =E2=80=9Cmultiplexing protocol=E2=80=9D is =
IP:<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- encapsulating a number of IP packets =
in an IP packet: Encapsulated Protocol number=3D4 (IPv4 encapsulation, =
RFC2003)<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- Encapsulating a number of Transport =
Segments in an IP packet (this would be equivalent to <span =
class=3DSpellE>TMux</span>, RFC1692, <a =
href=3D"https://tools.ietf.org/html/rfc1692">https://tools.ietf.org/html/=
rfc1692</a> ). Encapsulated Protocol number=3D6 (TCP, =
RFC793)<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>- Encapsulating a number of Ethernet =
Frames in an IP datagram: Encapsulated Protocol number=3D97<span =
style=3D'mso-tab-count:1'>=C2=A0 </span>ETHERIP, Ethernet-within-IP =
Encapsulation, RFC3378<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><b style=3D'mso-bidi-font-weight:normal'><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'>&gt; Multiplexing layer 3 =
packets in layer 4 datagrams?<o:p></o:p></span></b></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>If the =E2=80=9Cmultiplexing =
protocol=E2=80=9D is UDP, it would also make sense: this would avoid the =
need for a new =E2=80=9Cprotocol=E2=80=9D number. The two extremes would =
just need to agree on a port number. In fact, this is what is done in =
the implementation. <a =
href=3D"https://github.com/TCM-TF/simplemux"><span lang=3DES =
style=3D'mso-ansi-language:ES'>https://github.com/TCM-TF/simplemux</span>=
</a></span><span lang=3DEN-US> </span><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
class=3DSpellE><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'>Best</span></span><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'> <span =
class=3DSpellE>regards</span>,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p =
class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-fareast-font-family:"Times =
New =
Roman";color:#1F497D;mso-no-proof:yes'>Jose<o:p></o:p></span></p></div><p=
 class=3DMsoNormal><span =
style=3D'font-family:"Arial","sans-serif";mso-bidi-font-family:"Times =
New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'mso-outline-level:1'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman"'>De:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman"'> FERNANDO PASCUAL BLANCO [<a =
href=3D"mailto:fernando.pascualblanco@telefonica.com">mailto:fernando.pas=
cualblanco@telefonica.com</a>] <br><b>Enviado el:</b> mi=C3=A9rcoles, 17 =
de diciembre de 2014 9:56<br><b>Para:</b> Jose Saldana; <a =
href=3D"mailto:tsvwg@ietf.org">tsvwg@ietf.org</a><br><b>Asunto:</b> RE: =
[<span class=3DSpellE>tsvwg</span>] A new draft <span =
class=3DSpellE>submitted</span> to <span class=3DSpellE>tsvwg</span>: =
<span =
class=3DSpellE>Simplemux</span><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D;mso-ansi-language:EN-US'>Hi =
Jose,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>What multiplexing and =
what multiplexed protocols are you considering here? Are you focused on =
a determined protocol layer options? Or maybe you are defining something =
generic?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>For =
example:<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>- Multiplexing layer 3 =
packets in layer 2 frames?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>- Multiplexing layer 3 =
packets in layer 3 packets?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>- Multiplexing layer 3 =
packets in layer 4 datagrams?<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>More =
options?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'>Thanks!<o:p></o:p></span>=
</p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><div><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'color:#4F81BD;mso-ansi-language:EN-US'>Fernando</span></b><span =
lang=3DEN-US style=3D'color:#1F497D;mso-ansi-language:EN-US'> =
<o:p></o:p></span></p></div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span><=
/p><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'mso-outline-level:1'><b><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'> <span class=3DSpellE>tsvwg</span> =
[</span><a href=3D"mailto:tsvwg-bounces@ietf.org"><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>mailto:tsvwg-bounces@ietf.org</span></a=
><span lang=3DEN-US style=3D'mso-ansi-language:EN-US'>] <b>On Behalf Of =
</b>Jose Saldana<br><b>Sent:</b> <span class=3DSpellE>jueves</span>, 11 =
de <span class=3DSpellE>diciembre</span> de 2014 11:11<br><b>To:</b> =
</span><a href=3D"mailto:tsvwg@ietf.org"><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'>tsvwg@ietf.org</span></a><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'><br><b>Subject:</b> =
[<span class=3DSpellE>tsvwg</span>] A new draft submitted to <span =
class=3DSpellE>tsvwg</span>: <span =
class=3DSpellE>Simplemux</span><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>Hi all,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>This is an Internet Draft I submitted yesterday to <span =
class=3DSpellE>tsvwg</span>:<o:p></o:p></span></p><p =
class=3DMsoNormal><a =
href=3D"http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?in=
clude_text=3D1"><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-ansi-language:EN-US'>http:/=
/datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?include_text=3D1=
</span></a><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
class=3DSpellE><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>Simplemux</span></span><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'> could be seen as a generic protocol for multiplexing any =
protocol on any other protocol. The initial idea was: could this be used =
instead of PPPMux in TCM? However, I think it may have more fields of =
application.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>The idea is similar to that of PPPMux (RFC3153). However, PPP, =
and L2TP in turn, are not required, thus reducing =
complexity:</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>&nbsp;</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-ansi-language:EN-US'>| Ext<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>|| Mux<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>| packet || Mux<span =
class=3Dapple-converted-space>&nbsp;</span><span =
class=3DSpellE>hdr</span><span =
class=3Dapple-converted-space>&nbsp;</span>| packet || ...||</span><span =
lang=3DEN-US style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>It is different from <span class=3DSpellE>TMux</span> [RFC1692], =
because <span class=3DSpellE>TMux</span>&nbsp; combines multiple short =
transport segments, but not full packets, so it works between the same =
pair of machines.&nbsp; However, there are scenarios where a number of =
low-efficiency flows share a common path, but they do not travel between =
the same pair of machines.&nbsp; <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>A =E2=80=9CProtocol=E2=80=9D number should be requested to IANA =
for saying in the external header that <span =
class=3DSpellE>Simplemux</span> is inside. Each Mux header would include =
another =E2=80=9CProtocol=E2=80=9D field, so it would permit the =
multiplexing of different packets in the same bundle: IPv4, IPv6, ROHC, =
etc.</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>If you could have a look to the draft and send your comments, it =
would be fine.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>An implementation of <span class=3DSpellE>Simplemux</span> using =
IP/UDP as the multiplexing (external) protocol and IP or ROHC as the =
multiplexed protocol can be found here:<o:p></o:p></span></p><p =
class=3DMsoNormal><a href=3D"https://github.com/TCM-TF/simplemux"><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";mso-ansi-language:EN-US'>https:=
//github.com/TCM-TF/simplemux</span></a><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>Thanks in advance!<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-family:"Arial","sans-serif";color:#1F497D;mso-ansi-language=
:EN-US'>Jose<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span></p><div =
class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span =
lang=3DEN-US style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-font-family:"Times New =
Roman";mso-ansi-language:EN-US'><hr size=3D2 width=3D"100%" =
align=3Dcenter></span></div><p class=3DMsoNormal><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";mso-fareast-fon=
t-family:"Times New Roman";color:gray'><br>Este mensaje y sus adjuntos =
se dirigen exclusivamente a su destinatario, puede contener =
informaci=C3=B3n privilegiada o confidencial y es para uso exclusivo de =
la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la lectura, utilizaci=C3=B3n, =
divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida =
en virtud de la legislaci=C3=B3n vigente. Si ha recibido este mensaje =
por error, le rogamos que nos lo comunique inmediatamente por esta misma =
v=C3=ADa y proceda a su destrucci=C3=B3n.<br><br></span><span =
lang=3DEN-US =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";mso-fareast-fon=
t-family:"Times New Roman";color:gray;mso-ansi-language:EN-US'>The =
information contained in this transmission is privileged and =
confidential information intended only for the use of the individual or =
entity named above. If the reader of this message is not the intended =
recipient, you are hereby notified that any dissemination, distribution =
or copying of this communication is strictly prohibited. If you have =
received this transmission in error, do not read it. Please immediately =
reply to the sender that you have received this communication in error =
and then delete it.<br><br></span><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";mso-fareast-fon=
t-family:"Times New Roman";color:gray'>Esta mensagem e seus anexos se =
dirigem exclusivamente ao seu destinat=C3=A1rio, pode conter =
informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9 para uso =
exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vossa =
senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura, =
utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem =
autoriza=C3=A7=C3=A3o pode estar proibida em virtude da =
legisla=C3=A7=C3=A3o vigente. Se recebeu esta mensagem por erro, =
rogamos-lhe que nos o comunique imediatamente por esta mesma via e =
proceda a sua destrui=C3=A7=C3=A3o</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-font-family:"Times New =
Roman"'><o:p></o:p></span></p></div></div></body></html>
------=_NextPart_000_00D2_01D019E5.F3C67860--


From nobody Wed Dec 17 09:05:02 2014
Return-Path: <lucy.yong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935D11A8F4D for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 09:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 a20tnLBkOsNF for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 09:04:47 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF97B1A8F44 for <tsvwg@ietf.org>; Wed, 17 Dec 2014 09:04:43 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNA49887; Wed, 17 Dec 2014 17:04:42 +0000 (GMT)
Received: from DFWEML705-CHM.china.huawei.com (10.193.5.142) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 17 Dec 2014 17:04:41 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml705-chm ([10.193.5.142]) with mapi id 14.03.0158.001; Wed, 17 Dec 2014 09:04:39 -0800
From: Lucy yong <lucy.yong@huawei.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
Thread-Index: AQHQGhuLOkioERr74EWgLNYT2IxKyw==
Date: Wed, 17 Dec 2014 17:04:39 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4542A453@dfweml701-chm>
References: <CE03DB3D7B45C245BCA0D2432779493606DC0C@MX104CL02.corp.emc.com> <2691CE0099834E4A9C5044EEC662BB9D453FF325@dfweml701-chm> <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk>
In-Reply-To: <201411211734.sALHY7vn010130@bagheera.jungle.bt.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.155.48]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/qsXboKmgHGc8H92Q_Xzrmxdkizo
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [tsvwg] partial review of draft-ietf-tsvwg-gre-in-udp-encap-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 17:04:52 -0000

Hi Bob,

Thank you very much for the review. Sorry for the very late response due to=
 my two week vacation and a pile of stuff to work on after that. =20

Please see inline below.

-----Original Message-----
From: Bob Briscoe [mailto:bob.briscoe@bt.com]=20
Sent: Friday, November 21, 2014 11:30 AM
To: Lucy yong
Cc: Black, David; tsvwg@ietf.org
Subject: partial review of draft-ietf-tsvwg-gre-in-udp-encap-03

Lucy,

I'll wait for David's promised proposal to the list before commenting on th=
e checksum issue.
[Lucy] We need some work in IPv6 zero-checksum. Please share your comments =
and suggestions.=20

1) Regarding congestion control, I do not share the position of some others=
 in tsvwg. Congestion responsiveness is determined by how the source spaces=
 out the packets (i.e. their instantaneous rate). Just because a tunnel ing=
ress encapsulates a packet with a UDP header does not suddenly make it unre=
sponsive to congestion. The spacing between packets is still determined by =
the source. So there is no need to even mention congestion control consider=
ations in a tunnelling document, except to say in the scoping at the start =
that the addition of tunnel headers is completely orthogonal to congestion =
avoidance and control.

[Lucy] does David's response make sense to you? The draft will not specify =
congestion control at the tunnel, rather gre-in-udp applicability where con=
gestion is not a concern for the tunnel and recommended filters to block tr=
affic from going where it should not.

2)
Please replace:
    Tunnel end points that support
    ECN MUST use the method described in [RFC6040] for ECN marking
    propagation.
With:
    Tunnel end points need to use the method described in [RFC6040] for ECN=
 marking
    propagation.
Rationale:
    i) There is no such thing as a tunnel end point that does not support E=
CN - it has to put something in the ECN field, and it would not be appropri=
ate to put anything in there other than what RFC6040 says.
   ii) Generally it is not a good idea to fill one draft with normative sta=
tements that repeat normative statements made in other drafts. Otherwise up=
dating an RFC gets very difficult - we have to update all the other RFCs th=
at gratuitously repeat what it says.
[Lucy] will take your suggestion.

3) Nit in section 3.1.
    Section 5 of RFC6936 [RFC6936] specifies the additional requirements
    that implementation of UDP zero-checksum over IPv6 MUST compliant
    with. To compliant with it, the following additional requirements
    apply
s/compliant/comply/ (twice)
[Lucy] Thx. will fix it in next version.

There are other nits, but they can be dealt with later.
[Lucy] will correct them.

Thanks,
Lucy


Cheers


Bob




________________________________________________________________
Bob Briscoe,                                                  BT=20


From nobody Thu Dec 18 08:08:24 2014
Return-Path: <braden@meritmail.isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6150D1A88D5 for <tsvwg@ietfa.amsl.com>; Tue, 25 Nov 2014 12:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Q7ukN8pscqpX for <tsvwg@ietfa.amsl.com>; Tue, 25 Nov 2014 12:37:00 -0800 (PST)
Received: from phx-p01.merit.edu (phx-p01.merit.edu [207.75.117.233]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BAFF1A88D2 for <tsvwg@ietf.org>; Tue, 25 Nov 2014 12:37:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-p01.merit.edu (Postfix) with ESMTP id 737BF401CE58; Tue, 25 Nov 2014 15:36:59 -0500 (EST)
X-Virus-Scanned: amavisd-new at phx-p01.merit.edu
Received: from phx-p01.merit.edu ([127.0.0.1]) by localhost (phx-p01.merit.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZKT8obm7Dmiv; Tue, 25 Nov 2014 15:36:59 -0500 (EST)
Received: from [128.9.160.107] (cat.isi.edu [128.9.160.107]) by phx-p01.merit.edu (Postfix) with ESMTPSA id 14ECD401CE57; Tue, 25 Nov 2014 15:36:59 -0500 (EST)
Message-ID: <5474E869.6070406@meritmail.isi.edu>
From: Bob Braden <braden@meritmail.isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk> <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
In-Reply-To: <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/tu_2pwH-ySNgOt1vHTljPK1IFAo
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:08:17 -0800
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Date: Tue, 25 Nov 2014 20:37:02 -0000
X-Original-Date: Tue, 25 Nov 2014 12:36:57 -0800
X-List-Received-Date: Tue, 25 Nov 2014 20:37:02 -0000

On 11/25/2014 11:53 AM, Becke, Martin wrote:
>
> - =93Heartbeats SHOULD be sent to PF destination(s) once per RTO. This =
means the sender MUST ignore HB.interval for PF destinations.=94
>  =20
How about: "Heartbeats are sent to PF destination(s) once per RTO" ? =20
There is no need to shout... ;-)

Bob Braden




> This sounds strange to me. Why is SHOULD used here and what are the alt=
ernatives, when I MUST ignore HB.interval for PF destinations. I guess a =
rephrase of this two lines can help.
>
> - A link is missing in Section 5.1: [RFC6458] defines the constants SCT=
P_ADDR_AVAILABLE,=85.
>
> Best
> ________________________________________
> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von &quot;gorry@er=
g.abdn.ac.uk [gorry@erg.abdn.ac.uk]
> Gesendet: Mittwoch, 29. Oktober 2014 15:01
> An: tsvwg@ietf.org
> Cc: gorry@erg.abdn.ac.uk
> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclu=
de 19th November, 2014
>
> TSVWG,
>
> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>
> This WGLC will last until Wednesday, 19th November, 2014, this includes
> the period of the coming IETF meeting.
>
> A good note to the list is "I have read this version of the draft,
> and I approve (or support) its progression to RFC". The chairs
> request notes to the list showing support to get a sense of the WG.
>
> Of course, you can ask for alternate text (where you supply the
> actual replacement text, or convey the meaning sufficiently to the
> authors) for anywhere in the document that you find unclear or troubles=
ome.
>
> James/Gorry/David
> TSVWG chairs
>
>


--=20
Robert Braden
Internet and Networked Systems Division
USC Information Sciences Institute
310.448.9173


From nobody Thu Dec 18 08:08:33 2014
Return-Path: <fernando.pascualblanco@telefonica.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC06E1A0366 for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 00:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level: 
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 MAd6vFruy2zi for <tsvwg@ietfa.amsl.com>; Wed, 17 Dec 2014 00:56:10 -0800 (PST)
Received: from smtpjc.telefonica.com (smtpjc.telefonica.com [81.47.204.76]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5C991A020B for <tsvwg@ietf.org>; Wed, 17 Dec 2014 00:56:09 -0800 (PST)
Received: from smtpjc.telefonica.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F3E76E016E; Wed, 17 Dec 2014 09:56:06 +0100 (CET)
Received: from ESTGVMSP110.EUROPE.telefonica.corp (unknown [10.92.4.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtpjc.telefonica.com (Postfix) with ESMTPS id EEAD0E014D; Wed, 17 Dec 2014 09:56:06 +0100 (CET)
Received: from emea01-db3-obe.outbound.protection.outlook.com (10.92.5.139) by tls.telefonica.com (10.93.6.53) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 17 Dec 2014 09:56:06 +0100
Received: from AM3PR06MB452.eurprd06.prod.outlook.com (10.242.112.152) by AM3PR06MB449.eurprd06.prod.outlook.com (10.242.112.140) with Microsoft SMTP Server (TLS) id 15.1.49.12; Wed, 17 Dec 2014 08:56:05 +0000
Received: from AM3PR06MB452.eurprd06.prod.outlook.com ([10.242.112.152]) by AM3PR06MB452.eurprd06.prod.outlook.com ([10.242.112.152]) with mapi id 15.01.0031.000; Wed, 17 Dec 2014 08:56:05 +0000
From: FERNANDO PASCUAL BLANCO <fernando.pascualblanco@telefonica.com>
To: Jose Saldana <jsaldana@unizar.es>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] A new draft submitted to tsvwg: Simplemux
Thread-Index: AdAVKsK/+8m9NwlIQQKdMNyO2VHjEQErBJeg
Date: Wed, 17 Dec 2014 08:56:04 +0000
Message-ID: <AM3PR06MB45275A79D2297EB88D0D6D0E06D0@AM3PR06MB452.eurprd06.prod.outlook.com>
References: <00fa01d0152a$c8f60340$5ae209c0$@unizar.es>
In-Reply-To: <00fa01d0152a$c8f60340$5ae209c0$@unizar.es>
Accept-Language: es-ES, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [195.235.92.36]
authentication-results: unizar.es; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:AM3PR06MB449;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:AM3PR06MB449;
x-forefront-prvs: 042857DBB5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(51874003)(41574002)(53754006)(199003)(189002)(99396003)(87936001)(77156002)(120916001)(16236675004)(19617315012)(62966003)(102836002)(76576001)(15975445007)(66066001)(97736003)(68736005)(33656002)(21056001)(74316001)(19625215002)(2501002)(101416001)(2656002)(31966008)(19580405001)(19580395003)(19609705001)(20776003)(40100003)(64706001)(86362001)(46102003)(105586002)(2900100001)(122556002)(19300405004)(106356001)(50986999)(2950100001)(92566001)(77096005)(4396001)(76176999)(54206007)(107046002)(54606007)(54356999)(107886001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR06MB449; H:AM3PR06MB452.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_AM3PR06MB45275A79D2297EB88D0D6D0E06D0AM3PR06MB452eurprd_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Dec 2014 08:56:04.9572 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR06MB449
X-OriginatorOrg: telefonica.com
X-TM-AS-MML: No
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/RxWdZmoMfNJpUx29pscg0sCZOOs
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:08:28 -0800
Subject: Re: [tsvwg] A new draft submitted to tsvwg: Simplemux
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 08:56:14 -0000

--_000_AM3PR06MB45275A79D2297EB88D0D6D0E06D0AM3PR06MB452eurprd_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Jose,

What multiplexing and what multiplexed protocols are you considering here? =
Are you focused on a determined protocol layer options? Or maybe you are de=
fining something generic?
For example:

- Multiplexing layer 3 packets in layer 2 frames?
- Multiplexing layer 3 packets in layer 3 packets?
- Multiplexing layer 3 packets in layer 4 datagrams?

More options?

Thanks!

Fernando

From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Jose Saldana
Sent: jueves, 11 de diciembre de 2014 11:11
To: tsvwg@ietf.org
Subject: [tsvwg] A new draft submitted to tsvwg: Simplemux

Hi all,

This is an Internet Draft I submitted yesterday to tsvwg:
http://datatracker.ietf.org/doc/draft-saldana-tsvwg-simplemux/?include_text=
=3D1

Simplemux could be seen as a generic protocol for multiplexing any protocol=
 on any other protocol. The initial idea was: could this be used instead of=
 PPPMux in TCM? However, I think it may have more fields of application.

The idea is similar to that of PPPMux (RFC3153). However, PPP, and L2TP in =
turn, are not required, thus reducing complexity:

| Ext hdr || Mux hdr | packet || Mux hdr | packet || ...||

It is different from TMux [RFC1692], because TMux  combines multiple short =
transport segments, but not full packets, so it works between the same pair=
 of machines.  However, there are scenarios where a number of low-efficienc=
y flows share a common path, but they do not travel between the same pair o=
f machines.

A =E2=80=9CProtocol=E2=80=9D number should be requested to IANA for saying =
in the external header that Simplemux is inside. Each Mux header would incl=
ude another =E2=80=9CProtocol=E2=80=9D field, so it would permit the multip=
lexing of different packets in the same bundle: IPv4, IPv6, ROHC, etc.

If you could have a look to the draft and send your comments, it would be f=
ine.

An implementation of Simplemux using IP/UDP as the multiplexing (external) =
protocol and IP or ROHC as the multiplexed protocol can be found here:
https://github.com/TCM-TF/simplemux


Thanks in advance!

Jose


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la lectura, utilizaci=C3=B3n, divulgaci=
=C3=B3n y/o copia sin autorizaci=C3=B3n puede estar prohibida en virtud de =
la legislaci=C3=B3n vigente. Si ha recibido este mensaje por error, le roga=
mos que nos lo comunique inmediatamente por esta misma v=C3=ADa y proceda a=
 su destrucci=C3=B3n.

The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination, distribution or copying of this co=
mmunication is strictly prohibited. If you have received this transmission =
in error, do not read it. Please immediately reply to the sender that you h=
ave received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a leitura=
, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem autoriza=
=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o vigent=
e. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imedi=
atamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o

--_000_AM3PR06MB45275A79D2297EB88D0D6D0E06D0AM3PR06MB452eurprd_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Arial",sans-serif;
	color:#1F497D;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Jose,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">What multiplexing and =
what multiplexed protocols are you considering here? Are you focused on a d=
etermined protocol layer options? Or maybe you are defining something gener=
ic?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">For example:<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Multiplexing layer 3=
 packets in layer 2 frames?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Multiplexing layer 3=
 packets in layer 3 packets?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">- Multiplexing layer 3=
 packets in layer 4 datagrams?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">More options?<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks!<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"color:#4F81BD">Fernand=
o</span></b><span lang=3D"ES" style=3D"color:#1F497D">
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> tsvwg [mailto:tsvwg-bounces@ietf.org] <=
b>On Behalf Of
</b>Jose Saldana<br>
<b>Sent:</b> jueves, 11 de diciembre de 2014 11:11<br>
<b>To:</b> tsvwg@ietf.org<br>
<b>Subject:</b> [tsvwg] A new draft submitted to tsvwg: Simplemux<o:p></o:p=
></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">This is an Internet Draft I submitted yesterday to tsvwg=
:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><a href=3D"http://datatracker.ietf.org/doc/draft-saldana=
-tsvwg-simplemux/?include_text=3D1">http://datatracker.ietf.org/doc/draft-s=
aldana-tsvwg-simplemux/?include_text=3D1</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">Simplemux could be seen as a generic protocol for multip=
lexing any protocol on any other protocol. The initial idea was: could this=
 be used instead of PPPMux in TCM? However, I
 think it may have more fields of application.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">The idea is similar to that of PPPMux (RFC3153). However=
, PPP, and L2TP in turn, are not required, thus reducing complexity:</span>=
<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">| Ext<span class=3D"apple-converted-space">&nbsp;</span>hd=
r<span class=3D"apple-converted-space">&nbsp;</span>|| Mux<span class=3D"ap=
ple-converted-space">&nbsp;</span>hdr<span class=3D"apple-converted-space">=
&nbsp;</span>|
 packet || Mux<span class=3D"apple-converted-space">&nbsp;</span>hdr<span c=
lass=3D"apple-converted-space">&nbsp;</span>| packet || ...||</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">It is different from TMux [RFC1692], because TMux&nbsp; =
combines multiple short transport segments, but not full packets, so it wor=
ks between the same pair of machines.&nbsp; However, there
 are scenarios where a number of low-efficiency flows share a common path, =
but they do not travel between the same pair of machines.&nbsp;
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">A =E2=80=9CProtocol=E2=80=9D number should be requested =
to IANA for saying in the external header that Simplemux is inside. Each Mu=
x header would include another =E2=80=9CProtocol=E2=80=9D field, so it woul=
d permit
 the multiplexing of different packets in the same bundle: IPv4, IPv6, ROHC=
, etc.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">If you could have a look to the draft and send your comm=
ents, it would be fine.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">An implementation of Simplemux using IP/UDP as the multi=
plexing (external) protocol and IP or ROHC as the multiplexed protocol can =
be found here:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><a href=3D"https://github.com/TCM-TF/simplemux">https://=
github.com/TCM-TF/simplemux</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">Thanks in advance!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#1F497D">Jose<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"ES"><o:p>&nbsp;</o:p></span></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, pu=
ede contener informaci=C3=B3n privilegiada o confidencial y es para uso exc=
lusivo de la persona o entidad de destino. Si no es usted. el destinatario =
indicado, queda notificado de que la
 lectura, utilizaci=C3=B3n, divulgaci=C3=B3n y/o copia sin autorizaci=C3=B3=
n puede estar prohibida en virtud de la legislaci=C3=B3n vigente. Si ha rec=
ibido este mensaje por error, le rogamos que nos lo comunique inmediatament=
e por esta misma v=C3=ADa y proceda a su destrucci=C3=B3n.<br>
<br>
The information contained in this transmission is privileged and confidenti=
al information intended only for the use of the individual or entity named =
above. If the reader of this message is not the intended recipient, you are=
 hereby notified that any dissemination,
 distribution or copying of this communication is strictly prohibited. If y=
ou have received this transmission in error, do not read it. Please immedia=
tely reply to the sender that you have received this communication in error=
 and then delete it.<br>
<br>
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinat=C3=A1=
rio, pode conter informa=C3=A7=C3=A3o privilegiada ou confidencial e =C3=A9=
 para uso exclusivo da pessoa ou entidade de destino. Se n=C3=A3o =C3=A9 vo=
ssa senhoria o destinat=C3=A1rio indicado, fica notificado de que a
 leitura, utiliza=C3=A7=C3=A3o, divulga=C3=A7=C3=A3o e/ou c=C3=B3pia sem au=
toriza=C3=A7=C3=A3o pode estar proibida em virtude da legisla=C3=A7=C3=A3o =
vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique=
 imediatamente por esta mesma via e proceda a sua destrui=C3=A7=C3=A3o<br>
</font>
</body>
</html>

--_000_AM3PR06MB45275A79D2297EB88D0D6D0E06D0AM3PR06MB452eurprd_--


From nobody Fri Dec 19 00:13:03 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 787CE1A1F01 for <tsvwg@ietfa.amsl.com>; Fri, 19 Dec 2014 00:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.815
X-Spam-Level: **
X-Spam-Status: No, score=2.815 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, RELAY_IS_203=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 43sAQb1nSe2d for <tsvwg@ietfa.amsl.com>; Fri, 19 Dec 2014 00:12:58 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9903B1A1B72 for <tsvwg@ietf.org>; Fri, 19 Dec 2014 00:12:58 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 9B0BD2781D1 for <tsvwg@ietf.org>; Fri, 19 Dec 2014 17:12:55 +0900 (JST)
Received: by mail-la0-f44.google.com with SMTP id gd6so414831lab.3 for <tsvwg@ietf.org>; Fri, 19 Dec 2014 00:12:52 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.152.206.1 with SMTP id lk1mr4920765lac.92.1418976772854; Fri, 19 Dec 2014 00:12:52 -0800 (PST)
Received: by 10.114.200.113 with HTTP; Fri, 19 Dec 2014 00:12:52 -0800 (PST)
In-Reply-To: <5474E869.6070406@meritmail.isi.edu>
References: <5d68d136cd87bde12faaf414b05167d3.squirrel@spey.erg.abdn.ac.uk> <A33D17830EBE774E8AEFAED600DD54E20180066A0A@ccr02.win.uni-due.de> <5474E869.6070406@meritmail.isi.edu>
Date: Fri, 19 Dec 2014 00:12:52 -0800
Message-ID: <CAO249yfKLEamhhyX4Z4HjhtscjxVNJnapPKWKJ2JUPCNx1FkMQ@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Bob Braden <braden@meritmail.isi.edu>
Content-Type: multipart/alternative; boundary=001a1133a44c7d9ca1050a8d46a2
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/hBt88-hkSNBaN_zTUANtIM-wBHU
Cc: tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To conclude 19th November, 2014
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 08:13:01 -0000

--001a1133a44c7d9ca1050a8d46a2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Bob,

Thank you so much for the feedback.

On Tue, Nov 25, 2014 at 12:36 PM, Bob Braden <braden@meritmail.isi.edu>
wrote:
>
> On 11/25/2014 11:53 AM, Becke, Martin wrote:
>
>>
>> - =E2=80=9CHeartbeats SHOULD be sent to PF destination(s) once per RTO. =
This
>> means the sender MUST ignore HB.interval for PF destinations.=E2=80=9D
>>
>>
> How about: "Heartbeats are sent to PF destination(s) once per RTO" ?
> There is no need to shout... ;-)
>

I think this is one of key points in PF as this affects the performance of
PF. The default value of HB.interval is 30 secs which is much longer than
RTO.
So, I personally prefer to use SHOULD here in order to make sure to ignore
HB.interval. I will update the text to clarify this point.

Regards,
--
Yoshi



>
>
>
>  This sounds strange to me. Why is SHOULD used here and what are the
>> alternatives, when I MUST ignore HB.interval for PF destinations. I gues=
s a
>> rephrase of this two lines can help.
>>
>> - A link is missing in Section 5.1: [RFC6458] defines the constants
>> SCTP_ADDR_AVAILABLE,=E2=80=A6.
>>
>> Best
>> ________________________________________
>> Von: tsvwg [tsvwg-bounces@ietf.org]&quot; im Auftrag von &
>> quot;gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
>> Gesendet: Mittwoch, 29. Oktober 2014 15:01
>> An: tsvwg@ietf.org
>> Cc: gorry@erg.abdn.ac.uk
>> Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-failover-08 - To
>> conclude 19th November, 2014
>>
>> TSVWG,
>>
>> This is the start of a WGLC on "Quick Failover Algorithm in SCTP".
>> https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08
>>
>> This WGLC will last until Wednesday, 19th November, 2014, this includes
>> the period of the coming IETF meeting.
>>
>> A good note to the list is "I have read this version of the draft,
>> and I approve (or support) its progression to RFC". The chairs
>> request notes to the list showing support to get a sense of the WG.
>>
>> Of course, you can ask for alternate text (where you supply the
>> actual replacement text, or convey the meaning sufficiently to the
>> authors) for anywhere in the document that you find unclear or
>> troublesome.
>>
>> James/Gorry/David
>> TSVWG chairs
>>
>>
>>
>
> --
> Robert Braden
> Internet and Networked Systems Division
> USC Information Sciences Institute
> 310.448.9173
>
>

--001a1133a44c7d9ca1050a8d46a2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Bob,<div><br></div><div><div class=3D"gmail_extra">T=
hank you so much for the feedback.</div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Tue, Nov 25, 2014 at 12:36 PM, Bob Braden <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:braden@meritmail.isi.edu" target=3D"_blank=
">braden@meritmail.isi.edu</a>&gt;</span> wrote:<blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><span class=3D"">On 11/25/2014 11:53 AM, Becke, Martin wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
- =E2=80=9CHeartbeats SHOULD be sent to PF destination(s) once per RTO. Thi=
s means the sender MUST ignore HB.interval for PF destinations.=E2=80=9D<br=
>
=C2=A0 <br>
</blockquote></span>
How about: &quot;Heartbeats are sent to PF destination(s) once per RTO&quot=
; ?=C2=A0 There is no need to shout... ;-)<br></blockquote><div><br></div><=
div>I think this is one of key points in PF as this affects the performance=
 of PF. The default value of HB.interval is 30 secs which is much longer th=
an RTO.</div><div>So, I personally prefer to use SHOULD here in order to ma=
ke sure to ignore HB.interval. I will update the text to clarify this point=
.</div><div><br></div><div>Regards,</div><div>--</div><div>Yoshi</div><div>=
<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOE=
nZb"><div class=3D"h5"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This sounds strange to me. Why is SHOULD used here and what are the alterna=
tives, when I MUST ignore HB.interval for PF destinations. I guess a rephra=
se of this two lines can help.<br>
<br>
- A link is missing in Section 5.1: [RFC6458] defines the constants SCTP_AD=
DR_AVAILABLE,=E2=80=A6.<br>
<br>
Best<br>
______________________________<u></u>__________<br>
Von: tsvwg [<a href=3D"mailto:tsvwg-bounces@ietf.org" target=3D"_blank">tsv=
wg-bounces@ietf.org</a>]&amp;quot; im Auftrag von &amp;<a href=3D"mailto:qu=
ot%3Bgorry@erg.abdn.ac.uk" target=3D"_blank">quot;gorry@erg.abdn.ac.uk</a> =
[<a href=3D"mailto:gorry@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abdn.a=
c.uk</a>]<br>
Gesendet: Mittwoch, 29. Oktober 2014 15:01<br>
An: <a href=3D"mailto:tsvwg@ietf.org" target=3D"_blank">tsvwg@ietf.org</a><=
br>
Cc: <a href=3D"mailto:gorry@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abd=
n.ac.uk</a><br>
Betreff: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-<u></u>failover-08 - To con=
clude 19th November, 2014<br>
<br>
TSVWG,<br>
<br>
This is the start of a WGLC on &quot;Quick Failover Algorithm in SCTP&quot;=
.<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-08" t=
arget=3D"_blank">https://tools.ietf.org/html/<u></u>draft-ietf-tsvwg-sctp-<=
u></u>failover-08</a><br>
<br>
This WGLC will last until Wednesday, 19th November, 2014, this includes<br>
the period of the coming IETF meeting.<br>
<br>
A good note to the list is &quot;I have read this version of the draft,<br>
and I approve (or support) its progression to RFC&quot;. The chairs<br>
request notes to the list showing support to get a sense of the WG.<br>
<br>
Of course, you can ask for alternate text (where you supply the<br>
actual replacement text, or convey the meaning sufficiently to the<br>
authors) for anywhere in the document that you find unclear or troublesome.=
<br>
<br>
James/Gorry/David<br>
TSVWG chairs<br>
<br>
<br>
</blockquote>
<br>
<br></div></div><span class=3D"HOEnZb"><font color=3D"#888888">
-- <br>
Robert Braden<br>
Internet and Networked Systems Division<br>
USC Information Sciences Institute<br>
310.448.9173<br>
<br>
</font></span></blockquote></div></div></div></div>

--001a1133a44c7d9ca1050a8d46a2--


From nobody Fri Dec 19 11:13:53 2014
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC06A1ACD5C; Fri, 19 Dec 2014 11:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4nXpw12sGIJp; Fri, 19 Dec 2014 11:13:47 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BDC01A8A06; Fri, 19 Dec 2014 11:13:47 -0800 (PST)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id sBJJDNhc001824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 19 Dec 2014 11:13:24 -0800 (PST)
Message-ID: <549478D3.2050202@isi.edu>
Date: Fri, 19 Dec 2014 11:13:23 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <9904FB1B0159DA42B0B887B7FA8119CA5C930602@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA5C930602@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/_6xr07AwpTY8n_3Yj3hbWE2N6R8
Cc: "draft-ietf-tsvwg-port-use.all@tools.ietf.org" <draft-ietf-tsvwg-port-use.all@tools.ietf.org>
Subject: Re: [tsvwg] Gen-ART review of draft-ietf-tsvwg-port-use-06.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 19:13:49 -0000

Hi, Dan,

Thank you for this review. I'm confident both comments can be clarified
in a minor revision.

However, I did have a question about the end at "Nits/editorial
comments:" -- was there additional feedback intended there, or was this
section intended to be empty?

Thanks,

Joe

On 12/15/2014 5:31 AM, Romascanu, Dan (Dan) wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> 
> Gen-ART, please see the FAQ at
> 
>  
> 
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.tools.ietf.org_area_gen_trac_wiki_GenArtfaq&d=AAICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=sITgTP84yGaHOlBBZiB9yr8yJ3saUDz_ezXr0_7zXR0&s=ToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&e=
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.tools.ietf.org_area_gen_trac_wiki_GenArtfaq&d=AAICAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=I4dzGxR31OcNXCJfQzvlsiLQfucBXRucPvdrphpBsFA&m=sITgTP84yGaHOlBBZiB9yr8yJ3saUDz_ezXr0_7zXR0&s=ToxyMtIhluT9g1P7ZBH2FQN1ysRhib5pmy7-QEPiUBo&e=%20>>.
> 
>  
> 
> Please resolve these comments along with any other Last Call comments
> 
> you may receive.
> 
>  
> 
> Document: draft-ietf-tsvwg-port-use-06.txt
> 
> Reviewer: Dan Romascanu
> 
> Review Date: 12/15/14
> 
> IETF LC End Date: 12/22/14
> 
> IESG Telechat date: not yet
> 
>  
> 
> Summary: Ready with issues
> 
>  
> 
> The document is very clear and well written. I suggest that the author
> addresses the couple of issues raised here which are not show stoppers
> but their resolution can further improve the quality of the document.
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> 1.       The abstract says:
> 
>  
> 
> Ø  This document provides recommendations to application and service
>    designers on how to use the transport protocol port number space.
> 
>  
> 
> Section 1. Introduction says:
> 
>  
> 
> Ø     This document provides information and advice to system designers on
>    the use of transport port numbers.
> 
>  
> 
> In Section 7.2 ‘system designers’ appears again:
> 
>  
> 
> Ø  … system designers cannot yet rely on their presence.
> 
> Ø   
> 
>  
> 
> I do not like ‘system designers’ because this term is vague and not
> defined. Beyond the inconsistency in terminology which is obvious in
> page 2, there is also room for confusion because ‘system’ is used with a
> completely different meaning as in ‘system port’.
> 
>  
> 
> I suspect that  in section 1 ‘system designers’ is meant to be an alias
> for the ‘application and service designers’ from the intro, while in
> section 7.2 it’s rather meant to be an alias for ‘network designers’. If
> I am right I suggest replacing in both places.
> 
>  
> 
> 2.       The privacy considerations are not mentioned at all in the
> document. It seems to me that detecting in clear the port numbers and
> mapping this information to the source/destination addresses can provide
> information about specific hosts running specific services. I believe
> that this aspect should be mentioned either in the security
> considerations section or in a separate privacy considerations section,
> and in section 5, together with the paragraphs that mentions the
> capability of intermediate devices to monitor available services,
> monitor or intercept traffic.
> 
>  
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
>  
> 
>  
> 
>  
> 
>  
> 


From nobody Wed Dec 24 00:50:26 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00D91AD008; Wed, 24 Dec 2014 00:50:21 -0800 (PST)
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] autolearn=ham
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 P8jlhzEOKDVp; Wed, 24 Dec 2014 00:50:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3311A1A1F; Wed, 24 Dec 2014 00:50:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141224085020.2467.2615.idtracker@ietfa.amsl.com>
Date: Wed, 24 Dec 2014 00:50:20 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/4BN4xGo-dXhM7dNTqMXZgY1rQF0
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-failover-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Dec 2014 08:50:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Transport Area Working Group Working Group of the IETF.

        Title           : SCTP-PF: Quick Failover Algorithm in SCTP
        Authors         : Yoshifumi Nishida
                          Preethi Natarajan
                          Armando Caro
                          Paul D. Amer
                          Karen E. E. Nielsen
	Filename        : draft-ietf-tsvwg-sctp-failover-09.txt
	Pages           : 18
	Date            : 2014-12-24

Abstract:
   One of the major advantages of SCTP is the support of multi-homed
   communication.  A multi-homed SCTP end-point has the ability to
   withstand network failures by migrating the traffic from an inactive
   network to an active one.  However, if the failover operation as
   specified in [RFC4960] is followed, there can be a significant delay
   in the migration to the active destination addresses, thus severely
   reducing the effectiveness of the SCTP failover operation.

   This memo complements [RFC4960] by the introduction of the
   Potentially Failed path state and the associated new failover
   operation called SCTP-PF to apply during a network failure.  In
   addition, the memo complements [RFC4960] by introducing of
   alternative switchover operation modes for the data transfer path
   management after the recovery of a failed primary path.  These modes
   offers for more performance optimal operation in some network
   environments.  The implementation of the additional switchover
   operation modes is optional.

   The procedures defined in the document require only minimal
   modifications to the current specification.  The procedures are
   sender-side only and do not impact the SCTP receiver.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-failover-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Dec 24 10:55:24 2014
Return-Path: <nishida@sfc.wide.ad.jp>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95561A1A5A for <tsvwg@ietfa.amsl.com>; Wed, 24 Dec 2014 10:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.821
X-Spam-Level: *
X-Spam-Status: No, score=1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, J_CHICKENPOX_28=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 hOcV2e6I6NGu for <tsvwg@ietfa.amsl.com>; Wed, 24 Dec 2014 10:55:20 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [IPv6:2001:200:0:8803::53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E04101A1A56 for <tsvwg@ietf.org>; Wed, 24 Dec 2014 10:55:19 -0800 (PST)
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com [209.85.215.49]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id C81D2278199 for <tsvwg@ietf.org>; Thu, 25 Dec 2014 03:55:16 +0900 (JST)
Received: by mail-la0-f49.google.com with SMTP id hs14so7085166lab.8 for <tsvwg@ietf.org>; Wed, 24 Dec 2014 10:55:14 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.152.23.164 with SMTP id n4mr34575710laf.77.1419447314418; Wed, 24 Dec 2014 10:55:14 -0800 (PST)
Received: by 10.114.200.113 with HTTP; Wed, 24 Dec 2014 10:55:14 -0800 (PST)
In-Reply-To: <20141224085020.2467.2615.idtracker@ietfa.amsl.com>
References: <20141224085020.2467.2615.idtracker@ietfa.amsl.com>
Date: Wed, 24 Dec 2014 10:55:14 -0800
Message-ID: <CAO249yf5yjwn0isEbtYi31C0Cdd9ZE8cypyPbqKtxzqFGhzz8g@mail.gmail.com>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary=089e0160b8a6f4150e050afad480
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/sUZjEtPidEAFyoPh-1UMNTlFnYU
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-failover-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Dec 2014 18:55:22 -0000

--089e0160b8a6f4150e050afad480
Content-Type: text/plain; charset=UTF-8

Hi,

We have submitted new version of failover draft to address the comments we
got during WGLC.

In order to address Michael's comment, we've changed the title of the draft
a bit and replace the notion of quick failover in the document by
"SCTP-PF".
In order to address Martin's comment, we've changed "destination(s)" to
"destination address(es)".

Also, we have received comments on "Heartbeats SHOULD be sent to PF
destination(s) once per RTO.." sentence from Martin and Bob.
In order to address this, we've changed the sentence to:

      HEARTBEAT chunks SHOULD be sent to PF destination(s) once per RTO,
which requires to ignore HB.interval for PF destinations.

I hope this sentence will clarify our intent and will work for everyone.
We've checked the link issue pointed out from Martin, but we couldn't find
a problem in our xml yet.

Finally, we've reflected many editorial suggestions from Michael.

We really appreciate folks who gave us a lots of useful comments. Thank you
so much!
Please let us know if you have more comments or suggestions on the draft.


Happy Holidays!
--
Yoshi


On Wed, Dec 24, 2014 at 12:50 AM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Transport Area Working Group Working
> Group of the IETF.
>
>         Title           : SCTP-PF: Quick Failover Algorithm in SCTP
>         Authors         : Yoshifumi Nishida
>                           Preethi Natarajan
>                           Armando Caro
>                           Paul D. Amer
>                           Karen E. E. Nielsen
>         Filename        : draft-ietf-tsvwg-sctp-failover-09.txt
>         Pages           : 18
>         Date            : 2014-12-24
>
> Abstract:
>    One of the major advantages of SCTP is the support of multi-homed
>    communication.  A multi-homed SCTP end-point has the ability to
>    withstand network failures by migrating the traffic from an inactive
>    network to an active one.  However, if the failover operation as
>    specified in [RFC4960] is followed, there can be a significant delay
>    in the migration to the active destination addresses, thus severely
>    reducing the effectiveness of the SCTP failover operation.
>
>    This memo complements [RFC4960] by the introduction of the
>    Potentially Failed path state and the associated new failover
>    operation called SCTP-PF to apply during a network failure.  In
>    addition, the memo complements [RFC4960] by introducing of
>    alternative switchover operation modes for the data transfer path
>    management after the recovery of a failed primary path.  These modes
>    offers for more performance optimal operation in some network
>    environments.  The implementation of the additional switchover
>    operation modes is optional.
>
>    The procedures defined in the document require only minimal
>    modifications to the current specification.  The procedures are
>    sender-side only and do not impact the SCTP receiver.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-09
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-failover-09
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>

--089e0160b8a6f4150e050afad480
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>We have submitted new ve=
rsion of failover draft to address the comments we got during WGLC.</div><d=
iv><br></div><div>In order to address Michael&#39;s comment, we&#39;ve chan=
ged the title of the draft a bit and replace the notion of quick failover i=
n the document by &quot;SCTP-PF&quot;.=C2=A0</div><div>In order to address =
Martin&#39;s comment, we&#39;ve changed &quot;destination(s)&quot; to &quot=
;destination address(es)&quot;.</div><div><br></div><div>Also, we have rece=
ived comments on &quot;<span style=3D"font-size:13px">Heartbeats SHOULD be =
sent to PF destination(s) once per RTO..&quot; sentence from Martin and Bob=
.</span></div><div>In order to address this, we&#39;ve changed the sentence=
 to:</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 HEARTBEAT chunks SHOULD =
be sent to PF destination(s) once per RTO, which requires to ignore HB.inte=
rval for PF destinations.</div><div><br></div><div>I hope this sentence wil=
l clarify our intent and will work for everyone.</div><div>We&#39;ve checke=
d the link issue pointed out from Martin, but we couldn&#39;t find a proble=
m in our xml yet.</div><div><br></div><div>Finally, we&#39;ve reflected man=
y editorial suggestions from Michael.</div><div><br></div><div>We really ap=
preciate folks who gave us a lots of useful comments. Thank you so much!<br=
></div><div>Please let us know if you have more comments or suggestions on =
the draft.</div><div><br></div><div><br></div><div>Happy Holidays!</div><di=
v>--</div><div>Yoshi</div><div><br></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Wed, Dec 24, 2014 at 12:50 AM,  <span dir=3D"ltr=
">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">interne=
t-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Transport Area Working Group Working=
 Group of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 SCTP-PF: Quick Failover Algorithm in SCTP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Yosh=
ifumi Nishida<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Preethi Natarajan<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Armando Caro<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Paul D. Amer<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Karen E. E. Nielsen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-tsvwg-sctp-failover-09.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 18<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2014-12-24<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0One of the major advantages of SCTP is the support of multi-ho=
med<br>
=C2=A0 =C2=A0communication.=C2=A0 A multi-homed SCTP end-point has the abil=
ity to<br>
=C2=A0 =C2=A0withstand network failures by migrating the traffic from an in=
active<br>
=C2=A0 =C2=A0network to an active one.=C2=A0 However, if the failover opera=
tion as<br>
=C2=A0 =C2=A0specified in [RFC4960] is followed, there can be a significant=
 delay<br>
=C2=A0 =C2=A0in the migration to the active destination addresses, thus sev=
erely<br>
=C2=A0 =C2=A0reducing the effectiveness of the SCTP failover operation.<br>
<br>
=C2=A0 =C2=A0This memo complements [RFC4960] by the introduction of the<br>
=C2=A0 =C2=A0Potentially Failed path state and the associated new failover<=
br>
=C2=A0 =C2=A0operation called SCTP-PF to apply during a network failure.=C2=
=A0 In<br>
=C2=A0 =C2=A0addition, the memo complements [RFC4960] by introducing of<br>
=C2=A0 =C2=A0alternative switchover operation modes for the data transfer p=
ath<br>
=C2=A0 =C2=A0management after the recovery of a failed primary path.=C2=A0 =
These modes<br>
=C2=A0 =C2=A0offers for more performance optimal operation in some network<=
br>
=C2=A0 =C2=A0environments.=C2=A0 The implementation of the additional switc=
hover<br>
=C2=A0 =C2=A0operation modes is optional.<br>
<br>
=C2=A0 =C2=A0The procedures defined in the document require only minimal<br=
>
=C2=A0 =C2=A0modifications to the current specification.=C2=A0 The procedur=
es are<br>
=C2=A0 =C2=A0sender-side only and do not impact the SCTP receiver.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover/=
" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-=
failover/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-09" ta=
rget=3D"_blank">http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-failover-0=
9</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-sctp-failove=
r-09" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg=
-sctp-failover-09</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
</blockquote></div><br></div></div>

--089e0160b8a6f4150e050afad480--


From nobody Fri Dec 26 09:01:51 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9820B1A9078 for <tsvwg@ietfa.amsl.com>; Fri, 26 Dec 2014 09:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 h3PofgXDDDOQ for <tsvwg@ietfa.amsl.com>; Fri, 26 Dec 2014 09:01:47 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E70F31A9073 for <tsvwg@ietf.org>; Fri, 26 Dec 2014 09:01:46 -0800 (PST)
Received: from [85.158.137.99] by server-2.bemta-3.messagelabs.com id 91/71-05632-9749D945; Fri, 26 Dec 2014 17:01:45 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-217.messagelabs.com!1419613304!24343172!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16223 invoked from network); 26 Dec 2014 17:01:45 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-2.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 26 Dec 2014 17:01:45 -0000
Received: from EXHY022V.surrey.ac.uk (131.227.201.104) by exht011p.surrey.ac.uk (131.227.200.31) with Microsoft SMTP Server (TLS) id 8.3.348.2; Fri, 26 Dec 2014 17:01:44 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY022v.surrey.ac.uk (131.227.201.104) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 26 Dec 2014 17:01:44 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB460.eurprd06.prod.outlook.com (10.141.238.24) with Microsoft SMTP Server (TLS) id 15.1.49.12; Fri, 26 Dec 2014 17:01:43 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0049.002; Fri, 26 Dec 2014 17:01:43 +0000
From: <l.wood@surrey.ac.uk>
To: <tsvwg@ietf.org>, <gorry@erg.abdn.ac.uk>, <lars@netapp.com>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
Thread-Index: AQHQGIiA7ep7+aI6xkCPD7T1km5VR5yiJMau
Date: Fri, 26 Dec 2014 17:01:43 +0000
Message-ID: <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com>
In-Reply-To: <20141215165838.31657.16907.idtracker@ietfa.amsl.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [78.105.8.76]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-forefront-prvs: 04371797A5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(377424004)(377454003)(21056001)(15198665003)(76576001)(86362001)(31966008)(92566001)(46102003)(76176999)(230783001)(120916001)(54206007)(40100003)(2501002)(4396001)(74482002)(99396003)(50986999)(33656002)(77096005)(19580395003)(54356999)(97736003)(54606007)(105586002)(106116001)(107886001)(15395725005)(106356001)(107046002)(87936001)(2656002)(122556002)(74316001)(1720100001)(68736005)(77156002)(101416001)(19580405001)(64706001)(62966003)(2950100001)(102836002)(20776003)(66066001)(15975445007); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB460; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: surrey.ac.uk does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Dec 2014 17:01:43.5267 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b902693-1074-40aa-9e21-d89446a2ebb5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB460
X-OrganizationHeadersPreserved: DB4PR06MB460.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY022v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/vuxZAqmOhiLECTrYZroX0ToOx7o
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Dec 2014 17:01:49 -0000

A comment pertaining to checksum use.

This draft does not discuss that the udp checksum is scoped end to end betw=
een hosts, unlike the stronger link layer checksums, and that a strong link=
 checksum is no substitute for that path functionality.

While recommending the UDP checksum SHOULD be used is a fine default, a ras=
h of tunnelling protocols have said 'we already have payload protection, we=
 don't need udp checksum compute overhead' and have used the mere existence=
 of RFC6395/RFC6396 as justification for turning the checksum off, nuance b=
e damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anywh=
ere point of view.

I would argue that using UDP Lite to only checksum your UDP/IP header field=
s is always preferable to a UDP zero checksum, in that then your payload ca=
n still be messed up and that's your problem, but having your corrupted pac=
kets injected anywhere else is prevented. A zero udp checksum should always=
 be the very last option. For IPv6, UDP Lite doing the pseudo header check =
is far far preferable to zero UDP checksum, and the draft should say as muc=
h.

Please reread the 'By default' paragraph (second para of 3.4.1) - greater s=
hould be lesser in this context, as default is full coverage, and you can o=
nly go down.

(What would it take to have UDP itself be changed to allow two okay values =
for the checksum - checksum is either just across UDP/IP pseudoheaders or f=
ull payload, and you can incrementally compute pseudoheader onthe way to fu=
ll, say 'we matched headers at this point, no need to check rest of payload=
'. I doubt it weakens the full payload check significantly, and is a more t=
ransparent ligtweight header check than UDP Lite. no clue what this ,ight d=
o to middleboxes, though.)

Lloyd Wood
http://about.me/lloydwood

________________________________________
From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.org =
<internet-drafts@ietf.org>
Sent: Tuesday, 16 December 2014 3:58:38 AM
To: i-d-announce@ietf.org
Cc: tsvwg@ietf.org
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Transport Area Working Group Working Grou=
p of the IETF.

        Title           : UDP Usage Guidelines
        Authors         : Lars Eggert
                          Godred Fairhurst
                          Greg Shepherd
        Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
        Pages           : 37
        Date            : 2014-12-15

Abstract:
   The User Datagram Protocol (UDP) provides a minimal message-passing
   transport that has no inherent congestion control mechanisms.
   Because congestion control is critical to the stable operation of the
   Internet, applications and other protocols that choose to use UDP as
   an Internet transport must employ mechanisms to prevent congestion
   collapse and to establish some degree of fairness with concurrent
   traffic.  They may also need to implement additional mechanisms,
   depending on how they use UDP.

   This document provides guidelines on the use of UDP for the designers
   of applications, tunnels and other protocols that use UDP.
   Congestion control guidelines are a primary focus, but the document
   also provides guidance on other topics, including message sizes,
   reliability, checksums, and middlebox traversal.

   If published as an RFC, this document will obsolete RFC5405.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Dec 26 20:52:52 2014
Return-Path: <david.black@emc.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46B51A1B93 for <tsvwg@ietfa.amsl.com>; Fri, 26 Dec 2014 20:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 hkF7TYAflbGe for <tsvwg@ietfa.amsl.com>; Fri, 26 Dec 2014 20:52:47 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB01C1A1B99 for <tsvwg@ietf.org>; Fri, 26 Dec 2014 20:52:46 -0800 (PST)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sBR4qgdB006707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Dec 2014 23:52:43 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com sBR4qgdB006707
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1419655963; bh=FA4PX9JbNsFFAIUoihkTK3i2LFc=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=B+aMsHF80vjB7+yN1Zwu7Dbj3GHsVVtMKIN82W4ouY7S0pF6H9zcerhxOCgNOOA0m obSa5s5YRFDCCZpOp0kxuN+RU47Abmg9iUk4zlrtgENS2g4R2RVeJTWYC+Kx+Ec+e1 pKCcR27IIiJ/RlUdONCgMZYrAI/V3nBWLi4CdVCA=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com sBR4qgdB006707
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd51.lss.emc.com (RSA Interceptor); Fri, 26 Dec 2014 23:52:36 -0500
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sBR4qatu004225 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 26 Dec 2014 23:52:37 -0500
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub04.corp.emc.com (10.254.141.106) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 26 Dec 2014 23:52:36 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.208]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Fri, 26 Dec 2014 23:52:36 -0500
From: "Black, David" <david.black@emc.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "lars@netapp.com" <lars@netapp.com>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
Thread-Index: AQHQGIhwF1PE/h1HfEWKR7Zupb3FXZyifgCAgABtbYA=
Date: Sat, 27 Dec 2014 04:52:35 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.251.42.79]
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: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/6eeiC2d1o35wRXoMJ8hg54aiAws
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 04:52:51 -0000

Lloyd,

<WG chair hat off>

> A comment pertaining to checksum use.
>=20
> This draft does not discuss that the udp checksum is scoped end to end be=
tween
> hosts, unlike the stronger link layer checksums, and that a strong link
> checksum is no substitute for that path functionality.

Thanks for a timely comment ...

> While recommending the UDP checksum SHOULD be used is a fine default, a r=
ash
> of tunnelling protocols have said 'we already have payload protection, we
> don't need udp checksum compute overhead' and have used the mere existenc=
e of
> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anywh=
ere
> point of view.

Indeed, and please have a look at Section 3.1 of draft-ietf-mpls-in-udp-09 =
as a
current cross-area (TSV/RTG) attempt to do better:

http://tools.ietf.org/html/draft-ietf-mpls-in-udp-09#section-3.1

> I would argue that using UDP Lite to only checksum your UDP/IP header fie=
lds
> is always preferable to a UDP zero checksum in that then your payload can
> still be messed up and that's your problem, but having your corrupted pac=
kets
> injected anywhere else is prevented.

In principle, sure, I agree, but in practice, there are "running code" prob=
lems
with network gear that passes UDP but not UDP-Lite (port-translating NATs a=
re
well-known offenders) and more importantly that load balances (ECMP or Ethe=
rnet
LAG) UDP traffic, but not UDP-Lite traffic :-(.

> A zero udp checksum should always be the
> very last option. For IPv6, UDP Lite doing the pseudo header check is far=
 far
> preferable to zero UDP checksum, and the draft should say as much.

No argument there in principle, but when UDP-Lite doesn't work in practice
(wrong protocol # in IP header), then what?

> (What would it take to have UDP itself be changed to allow two okay value=
s for
> the checksum - checksum is either just across UDP/IP pseudoheaders or ful=
l
> payload, and you can incrementally compute pseudoheader on the way to ful=
l, say
> 'we matched headers at this point, no need to check rest of payload'. I d=
oubt
> it weakens the full payload check significantly, and is a more transparen=
t
> lightweight header check than UDP Lite. no clue what this might do to
> middleboxes, though.)

A significant concern here is backwards compatibility - middleboxes, end sy=
stems,
and network mgt/ops tools, although this is something that some new uses of=
 UDP
could be encouraged to do with the next header inside UDP (use zero UDP che=
cksum
and insert a "shim" that includes a checksum of the UDP/IP pseudoheaders an=
d the
shim).

</WG chair hat off>

Thanks,
--David


> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.ac=
.uk
> Sent: Friday, December 26, 2014 12:02 PM
> To: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>=20
> A comment pertaining to checksum use.
>=20
> This draft does not discuss that the udp checksum is scoped end to end be=
tween
> hosts, unlike the stronger link layer checksums, and that a strong link
> checksum is no substitute for that path functionality.
>=20
> While recommending the UDP checksum SHOULD be used is a fine default, a r=
ash
> of tunnelling protocols have said 'we already have payload protection, we
> don't need udp checksum compute overhead' and have used the mere existenc=
e of
> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anywh=
ere
> point of view.
>=20
> I would argue that using UDP Lite to only checksum your UDP/IP header fie=
lds
> is always preferable to a UDP zero checksum, in that then your payload ca=
n
> still be messed up and that's your problem, but having your corrupted pac=
kets
> injected anywhere else is prevented. A zero udp checksum should always be=
 the
> very last option. For IPv6, UDP Lite doing the pseudo header check is far=
 far
> preferable to zero UDP checksum, and the draft should say as much.
>=20
> Please reread the 'By default' paragraph (second para of 3.4.1) - greater
> should be lesser in this context, as default is full coverage, and you ca=
n
> only go down.
>=20
> (What would it take to have UDP itself be changed to allow two okay value=
s for
> the checksum - checksum is either just across UDP/IP pseudoheaders or ful=
l
> payload, and you can incrementally compute pseudoheader onthe way to full=
, say
> 'we matched headers at this point, no need to check rest of payload'. I d=
oubt
> it weakens the full payload check significantly, and is a more transparen=
t
> ligtweight header check than UDP Lite. no clue what this ,ight do to
> middleboxes, though.)
>=20
> Lloyd Wood
> http://about.me/lloydwood
>=20
> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.or=
g
> <internet-drafts@ietf.org>
> Sent: Tuesday, 16 December 2014 3:58:38 AM
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Transport Area Working Group Working Gr=
oup
> of the IETF.
>=20
>         Title           : UDP Usage Guidelines
>         Authors         : Lars Eggert
>                           Godred Fairhurst
>                           Greg Shepherd
>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>         Pages           : 37
>         Date            : 2014-12-15
>=20
> Abstract:
>    The User Datagram Protocol (UDP) provides a minimal message-passing
>    transport that has no inherent congestion control mechanisms.
>    Because congestion control is critical to the stable operation of the
>    Internet, applications and other protocols that choose to use UDP as
>    an Internet transport must employ mechanisms to prevent congestion
>    collapse and to establish some degree of fairness with concurrent
>    traffic.  They may also need to implement additional mechanisms,
>    depending on how they use UDP.
>=20
>    This document provides guidelines on the use of UDP for the designers
>    of applications, tunnels and other protocols that use UDP.
>    Congestion control guidelines are a primary focus, but the document
>    also provides guidance on other topics, including message sizes,
>    reliability, checksums, and middlebox traversal.
>=20
>    If published as an RFC, this document will obsolete RFC5405.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Dec 27 09:42:18 2014
Return-Path: <therbert@google.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1C81A8AA0 for <tsvwg@ietfa.amsl.com>; Sat, 27 Dec 2014 09:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 boCPzG-kBgVz for <tsvwg@ietfa.amsl.com>; Sat, 27 Dec 2014 09:42:12 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 574501A8AB1 for <tsvwg@ietf.org>; Sat, 27 Dec 2014 09:42:11 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so10645053ier.32 for <tsvwg@ietf.org>; Sat, 27 Dec 2014 09:42:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vZ2dMm2LdCzpJae63w3nX9cx/C7ewD74eM/bSRvf1Sg=; b=GTMLdB1CM+DLyHfyOXJy1oMtSQubasbcSL8xzRaT42sPqe9jFCaPCistseLwZh20V6 9wTvAqOP2KXdvoleZBer6//EJ+f7Zw2ciJkmb+pbBxyEJNpPvl7prJ9vNJI7Xt+KkbPA gpGMaK+HJb/ruZOMzljUo4Z/SMxrr9ekCtuJxemkacnACCyPJKDjriDGVst49vrIcxjh RTRj1zrWbo6D/0m6ZXRXkMG8dDfo8ujlB1lePQPSi4KxOz9ruaq5tNmdrn4wvCiSBkuA kPweFXnI0jQp/cTjaUZxox5gTwfT8NQePKuLvZA453SrffyvHGnspPBCoVr/hwpWLRXo BkdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vZ2dMm2LdCzpJae63w3nX9cx/C7ewD74eM/bSRvf1Sg=; b=gEEwkcrP9M0pjsVW99fHKFLAGH12MCLf+Y70jDBhcO2h88cCjSbIyeefNvk6TIOyVw lRB1cjdUz9TeIm4M8HID5NTFa+w/1rl7pPJe9juVQkMrCPJgNrOAdRqYKKTXCJOsUj/w RCF7cvihiBn+Y8Pmqam99oiDdjD2NiW8CCjFa3hfvT2XtEeJ69n/YLqlPS38BFX6DrrB Ubo1rEGfq3razY4ytiFM8WqZ7cMTw7QhLnp4pXdxApquMYPm2+iwR5jNab+Feix/eRpO kCtTcbwbBjinVXVQHFOFhPtp7gq+SXYB/kIYKfDJ/HFuy8tQTAt48s83u1U6Is2k9RKJ csvw==
X-Gm-Message-State: ALoCoQlupMkTH9/KKaitO5RlbJ58qACXA5FeemWkG5shjT0WieqoKp5bqWGaNcCE1v9xAfGBzE4C
MIME-Version: 1.0
X-Received: by 10.42.107.83 with SMTP id c19mr36083847icp.48.1419702130367; Sat, 27 Dec 2014 09:42:10 -0800 (PST)
Received: by 10.64.98.167 with HTTP; Sat, 27 Dec 2014 09:42:10 -0800 (PST)
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com> <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com>
Date: Sat, 27 Dec 2014 09:42:10 -0800
Message-ID: <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ijdeNFPNj1FUPB1y5i9XDzmEEtA
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 17:42:14 -0000

Lloyd, David

Comments inline.

On Fri, Dec 26, 2014 at 8:52 PM, Black, David <david.black@emc.com> wrote:
> Lloyd,
>
> <WG chair hat off>
>
>> A comment pertaining to checksum use.
>>
>> This draft does not discuss that the udp checksum is scoped end to end between
>> hosts, unlike the stronger link layer checksums, and that a strong link
>> checksum is no substitute for that path functionality.
>
> Thanks for a timely comment ...
>
>> While recommending the UDP checksum SHOULD be used is a fine default, a rash
>> of tunnelling protocols have said 'we already have payload protection, we
>> don't need udp checksum compute overhead' and have used the mere existence of
>> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anywhere
>> point of view.
>
> Indeed, and please have a look at Section 3.1 of draft-ietf-mpls-in-udp-09 as a
> current cross-area (TSV/RTG) attempt to do better:
>
draft-ietf-mpls-in-udp-09 and RFC6936 are much more restrictive in the
use of zero UDP checksum in IPv6 than what is described here. Those
seem to require that IPv6 UDP checksum MUST be enabled unless certain
requirements are meant when using UDP tunnels.

It might be good to include the motivation for using zero UDP checksum.
Presumably, the core motivation is either performance cost of
computing full checksum or communicating with devices that can't
compute the checksum.

I would imagine that the majority of devices that terminate UDP are
end hosts which can already compute UDP checksum, and probably in the
majority of those there are NICs that offload the UDP checksum so it
is no performance impact. In these cases, UDP checksum should be
enabled. In some cases, enabling UDP checksum with tunnels can be a
performance win over using zero UDP checksum when properly leveraging
UDP checksum offload capability.

We do know that some devices, switches in particular, will be
terminating UDP (tunnels) and they may not have the capability to
compute a UDP checksum. For these, UDP zero checksums are useful (per
RFC6336), but the case where one of these devices receives a packet
with a non-zero UDP checksum must be considered. VXLAN (RFC7348) makes
checksum verification optional, but this seems to be inconsistent with
RFC1122. I would suggest a requirement something like: "If a UDP
datagram is received with a checksum that is non-zero and the node is
unable to verify the checksum, the node MUST discard the datagram."

Thanks,
Tom

> http://tools.ietf.org/html/draft-ietf-mpls-in-udp-09#section-3.1
>
>> I would argue that using UDP Lite to only checksum your UDP/IP header fields
>> is always preferable to a UDP zero checksum in that then your payload can
>> still be messed up and that's your problem, but having your corrupted packets
>> injected anywhere else is prevented.
>
> In principle, sure, I agree, but in practice, there are "running code" problems
> with network gear that passes UDP but not UDP-Lite (port-translating NATs are
> well-known offenders) and more importantly that load balances (ECMP or Ethernet
> LAG) UDP traffic, but not UDP-Lite traffic :-(.
>
>> A zero udp checksum should always be the
>> very last option. For IPv6, UDP Lite doing the pseudo header check is far far
>> preferable to zero UDP checksum, and the draft should say as much.
>
> No argument there in principle, but when UDP-Lite doesn't work in practice
> (wrong protocol # in IP header), then what?
>
>> (What would it take to have UDP itself be changed to allow two okay values for
>> the checksum - checksum is either just across UDP/IP pseudoheaders or full
>> payload, and you can incrementally compute pseudoheader on the way to full, say
>> 'we matched headers at this point, no need to check rest of payload'. I doubt
>> it weakens the full payload check significantly, and is a more transparent
>> lightweight header check than UDP Lite. no clue what this might do to
>> middleboxes, though.)
>
> A significant concern here is backwards compatibility - middleboxes, end systems,
> and network mgt/ops tools, although this is something that some new uses of UDP
> could be encouraged to do with the next header inside UDP (use zero UDP checksum
> and insert a "shim" that includes a checksum of the UDP/IP pseudoheaders and the
> shim).
>
> </WG chair hat off>
>
> Thanks,
> --David
>
>
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
>> Sent: Friday, December 26, 2014 12:02 PM
>> To: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>
>> A comment pertaining to checksum use.
>>
>> This draft does not discuss that the udp checksum is scoped end to end between
>> hosts, unlike the stronger link layer checksums, and that a strong link
>> checksum is no substitute for that path functionality.
>>
>> While recommending the UDP checksum SHOULD be used is a fine default, a rash
>> of tunnelling protocols have said 'we already have payload protection, we
>> don't need udp checksum compute overhead' and have used the mere existence of
>> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anywhere
>> point of view.
>>
>> I would argue that using UDP Lite to only checksum your UDP/IP header fields
>> is always preferable to a UDP zero checksum, in that then your payload can
>> still be messed up and that's your problem, but having your corrupted packets
>> injected anywhere else is prevented. A zero udp checksum should always be the
>> very last option. For IPv6, UDP Lite doing the pseudo header check is far far
>> preferable to zero UDP checksum, and the draft should say as much.
>>
>> Please reread the 'By default' paragraph (second para of 3.4.1) - greater
>> should be lesser in this context, as default is full coverage, and you can
>> only go down.
>>
>> (What would it take to have UDP itself be changed to allow two okay values for
>> the checksum - checksum is either just across UDP/IP pseudoheaders or full
>> payload, and you can incrementally compute pseudoheader onthe way to full, say
>> 'we matched headers at this point, no need to check rest of payload'. I doubt
>> it weakens the full payload check significantly, and is a more transparent
>> ligtweight header check than UDP Lite. no clue what this ,ight do to
>> middleboxes, though.)
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>>
>> ________________________________________
>> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.org
>> <internet-drafts@ietf.org>
>> Sent: Tuesday, 16 December 2014 3:58:38 AM
>> To: i-d-announce@ietf.org
>> Cc: tsvwg@ietf.org
>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the Transport Area Working Group Working Group
>> of the IETF.
>>
>>         Title           : UDP Usage Guidelines
>>         Authors         : Lars Eggert
>>                           Godred Fairhurst
>>                           Greg Shepherd
>>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>>         Pages           : 37
>>         Date            : 2014-12-15
>>
>> Abstract:
>>    The User Datagram Protocol (UDP) provides a minimal message-passing
>>    transport that has no inherent congestion control mechanisms.
>>    Because congestion control is critical to the stable operation of the
>>    Internet, applications and other protocols that choose to use UDP as
>>    an Internet transport must employ mechanisms to prevent congestion
>>    collapse and to establish some degree of fairness with concurrent
>>    traffic.  They may also need to implement additional mechanisms,
>>    depending on how they use UDP.
>>
>>    This document provides guidelines on the use of UDP for the designers
>>    of applications, tunnels and other protocols that use UDP.
>>    Congestion control guidelines are a primary focus, but the document
>>    also provides guidance on other topics, including message sizes,
>>    reliability, checksums, and middlebox traversal.
>>
>>    If published as an RFC, this document will obsolete RFC5405.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>


From nobody Sun Dec 28 00:35:06 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C909F1A6F17 for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 00:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ODGFKXN9-psH for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 00:35:01 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.151]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 595BF1A1F00 for <tsvwg@ietf.org>; Sun, 28 Dec 2014 00:35:00 -0800 (PST)
Received: from [85.158.136.51] by server-15.bemta-5.messagelabs.com id DE/20-01660-3B0CF945; Sun, 28 Dec 2014 08:34:59 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-49.messagelabs.com!1419755698!27315402!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20659 invoked from network); 28 Dec 2014 08:34:59 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 28 Dec 2014 08:34:59 -0000
Received: from EXHY012V.surrey.ac.uk (131.227.201.103) by EXHT022P.surrey.ac.uk (131.227.200.43) with Microsoft SMTP Server (TLS) id 8.3.342.0; Sun, 28 Dec 2014 08:34:58 +0000
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY012v.surrey.ac.uk (131.227.201.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sun, 28 Dec 2014 08:34:57 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) with Microsoft SMTP Server (TLS) id 15.1.49.12; Sun, 28 Dec 2014 08:34:57 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0049.002; Sun, 28 Dec 2014 08:34:57 +0000
From: <l.wood@surrey.ac.uk>
To: <therbert@google.com>, <david.black@emc.com>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
Thread-Index: AQHQGIiA7ep7+aI6xkCPD7T1km5VR5yiJMaugADMBYCAANcFAIAA9gnj
Date: Sun, 28 Dec 2014 08:34:57 +0000
Message-ID: <DB4PR06MB45712A7E15C95A9CAD769D6AD500@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com> <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com>, <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com>
In-Reply-To: <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [78.105.8.76]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB457;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB457;
x-forefront-prvs: 0439571D1D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(164054003)(13464003)(377424004)(377454003)(51704005)(24454002)(189002)(199003)(77156002)(33656002)(101416001)(54606007)(120916001)(106356001)(106116001)(15198665003)(2950100001)(76576001)(87936001)(97736003)(99396003)(230783001)(2900100001)(105586002)(107046002)(93886004)(4396001)(86362001)(40100003)(15975445007)(50986999)(77096005)(21056001)(62966003)(2656002)(31966008)(122556002)(74482002)(46102003)(19580395003)(1720100001)(19580405001)(68736005)(92566001)(15395725005)(54356999)(54206007)(74316001)(64706001)(20776003)(76176999)(102836002)(66066001)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB457; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: surrey.ac.uk does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Dec 2014 08:34:57.0812 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b902693-1074-40aa-9e21-d89446a2ebb5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB457
X-OrganizationHeadersPreserved: DB4PR06MB457.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY012v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Yit9PTod7_vIwpoBO5H3YfZxqgE
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2014 08:35:05 -0000

David,

an mpls-in-udp suggestion:

as motivation and context: "Across an Ethernet link, errors in transmission=
 of the MPLS stack and payload are detected and prevented from propagating =
further at the correct destination by the Ethernet frame CRC. Across a long=
er Internet path, the weaker UDP checksum provides the same important funct=
ionality for MPLS-in-UDP"

that is,the motivation should be why the checksum a good idea. not the reve=
rse of "oooh, faster"

Tom, a device that can't compute a UDP checksum (ones complement? not hard)=
 can't compute a TCP checksum either. What is it doing on the public intern=
et, and why is it the IETF's concern?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Tom Herbert <therbert@google.com>
Sent: Sunday, 28 December 2014 4:42:10 AM
To: Black, David
Cc: Wood L  Dr (Electronic Eng); tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars=
@netapp.com
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt

Lloyd, David

Comments inline.

On Fri, Dec 26, 2014 at 8:52 PM, Black, David <david.black@emc.com> wrote:
> Lloyd,
>
> <WG chair hat off>
>
>> A comment pertaining to checksum use.
>>
>> This draft does not discuss that the udp checksum is scoped end to end b=
etween
>> hosts, unlike the stronger link layer checksums, and that a strong link
>> checksum is no substitute for that path functionality.
>
> Thanks for a timely comment ...
>
>> While recommending the UDP checksum SHOULD be used is a fine default, a =
rash
>> of tunnelling protocols have said 'we already have payload protection, w=
e
>> don't need udp checksum compute overhead' and have used the mere existen=
ce of
>> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anyw=
here
>> point of view.
>
> Indeed, and please have a look at Section 3.1 of draft-ietf-mpls-in-udp-0=
9 as a
> current cross-area (TSV/RTG) attempt to do better:
>
draft-ietf-mpls-in-udp-09 and RFC6936 are much more restrictive in the
use of zero UDP checksum in IPv6 than what is described here. Those
seem to require that IPv6 UDP checksum MUST be enabled unless certain
requirements are meant when using UDP tunnels.

It might be good to include the motivation for using zero UDP checksum.
Presumably, the core motivation is either performance cost of
computing full checksum or communicating with devices that can't
compute the checksum.

I would imagine that the majority of devices that terminate UDP are
end hosts which can already compute UDP checksum, and probably in the
majority of those there are NICs that offload the UDP checksum so it
is no performance impact. In these cases, UDP checksum should be
enabled. In some cases, enabling UDP checksum with tunnels can be a
performance win over using zero UDP checksum when properly leveraging
UDP checksum offload capability.

We do know that some devices, switches in particular, will be
terminating UDP (tunnels) and they may not have the capability to
compute a UDP checksum. For these, UDP zero checksums are useful (per
RFC6336), but the case where one of these devices receives a packet
with a non-zero UDP checksum must be considered. VXLAN (RFC7348) makes
checksum verification optional, but this seems to be inconsistent with
RFC1122. I would suggest a requirement something like: "If a UDP
datagram is received with a checksum that is non-zero and the node is
unable to verify the checksum, the node MUST discard the datagram."

Thanks,
Tom

> http://tools.ietf.org/html/draft-ietf-mpls-in-udp-09#section-3.1
>
>> I would argue that using UDP Lite to only checksum your UDP/IP header fi=
elds
>> is always preferable to a UDP zero checksum in that then your payload ca=
n
>> still be messed up and that's your problem, but having your corrupted pa=
ckets
>> injected anywhere else is prevented.
>
> In principle, sure, I agree, but in practice, there are "running code" pr=
oblems
> with network gear that passes UDP but not UDP-Lite (port-translating NATs=
 are
> well-known offenders) and more importantly that load balances (ECMP or Et=
hernet
> LAG) UDP traffic, but not UDP-Lite traffic :-(.
>
>> A zero udp checksum should always be the
>> very last option. For IPv6, UDP Lite doing the pseudo header check is fa=
r far
>> preferable to zero UDP checksum, and the draft should say as much.
>
> No argument there in principle, but when UDP-Lite doesn't work in practic=
e
> (wrong protocol # in IP header), then what?
>
>> (What would it take to have UDP itself be changed to allow two okay valu=
es for
>> the checksum - checksum is either just across UDP/IP pseudoheaders or fu=
ll
>> payload, and you can incrementally compute pseudoheader on the way to fu=
ll, say
>> 'we matched headers at this point, no need to check rest of payload'. I =
doubt
>> it weakens the full payload check significantly, and is a more transpare=
nt
>> lightweight header check than UDP Lite. no clue what this might do to
>> middleboxes, though.)
>
> A significant concern here is backwards compatibility - middleboxes, end =
systems,
> and network mgt/ops tools, although this is something that some new uses =
of UDP
> could be encouraged to do with the next header inside UDP (use zero UDP c=
hecksum
> and insert a "shim" that includes a checksum of the UDP/IP pseudoheaders =
and the
> shim).
>
> </WG chair hat off>
>
> Thanks,
> --David
>
>
>> -----Original Message-----
>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.a=
c.uk
>> Sent: Friday, December 26, 2014 12:02 PM
>> To: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>
>> A comment pertaining to checksum use.
>>
>> This draft does not discuss that the udp checksum is scoped end to end b=
etween
>> hosts, unlike the stronger link layer checksums, and that a strong link
>> checksum is no substitute for that path functionality.
>>
>> While recommending the UDP checksum SHOULD be used is a fine default, a =
rash
>> of tunnelling protocols have said 'we already have payload protection, w=
e
>> don't need udp checksum compute overhead' and have used the mere existen=
ce of
>> RFC6395/RFC6396 as justification for turning the checksum off, nuance be
>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go anyw=
here
>> point of view.
>>
>> I would argue that using UDP Lite to only checksum your UDP/IP header fi=
elds
>> is always preferable to a UDP zero checksum, in that then your payload c=
an
>> still be messed up and that's your problem, but having your corrupted pa=
ckets
>> injected anywhere else is prevented. A zero udp checksum should always b=
e the
>> very last option. For IPv6, UDP Lite doing the pseudo header check is fa=
r far
>> preferable to zero UDP checksum, and the draft should say as much.
>>
>> Please reread the 'By default' paragraph (second para of 3.4.1) - greate=
r
>> should be lesser in this context, as default is full coverage, and you c=
an
>> only go down.
>>
>> (What would it take to have UDP itself be changed to allow two okay valu=
es for
>> the checksum - checksum is either just across UDP/IP pseudoheaders or fu=
ll
>> payload, and you can incrementally compute pseudoheader onthe way to ful=
l, say
>> 'we matched headers at this point, no need to check rest of payload'. I =
doubt
>> it weakens the full payload check significantly, and is a more transpare=
nt
>> ligtweight header check than UDP Lite. no clue what this ,ight do to
>> middleboxes, though.)
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>>
>> ________________________________________
>> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.o=
rg
>> <internet-drafts@ietf.org>
>> Sent: Tuesday, 16 December 2014 3:58:38 AM
>> To: i-d-announce@ietf.org
>> Cc: tsvwg@ietf.org
>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the Transport Area Working Group Working G=
roup
>> of the IETF.
>>
>>         Title           : UDP Usage Guidelines
>>         Authors         : Lars Eggert
>>                           Godred Fairhurst
>>                           Greg Shepherd
>>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>>         Pages           : 37
>>         Date            : 2014-12-15
>>
>> Abstract:
>>    The User Datagram Protocol (UDP) provides a minimal message-passing
>>    transport that has no inherent congestion control mechanisms.
>>    Because congestion control is critical to the stable operation of the
>>    Internet, applications and other protocols that choose to use UDP as
>>    an Internet transport must employ mechanisms to prevent congestion
>>    collapse and to establish some degree of fairness with concurrent
>>    traffic.  They may also need to implement additional mechanisms,
>>    depending on how they use UDP.
>>
>>    This document provides guidelines on the use of UDP for the designers
>>    of applications, tunnels and other protocols that use UDP.
>>    Congestion control guidelines are a primary focus, but the document
>>    also provides guidance on other topics, including message sizes,
>>    reliability, checksums, and middlebox traversal.
>>
>>    If published as an RFC, this document will obsolete RFC5405.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>>
>>
>> Please note that it may take a couple of minutes from the time of submis=
sion
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>


From nobody Sun Dec 28 00:43:33 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A03B1A1F00 for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 00:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 NIlvGzyKb03g for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 00:43:30 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 627EF1ACDB1 for <tsvwg@ietf.org>; Sun, 28 Dec 2014 00:43:30 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id sBS8hRxW023847; Sun, 28 Dec 2014 08:43:27 GMT
Received: from 950129200 (089144210161.atnat0019.highway.a1.net [89.144.210.161]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id sBS8hPIx023834 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 28 Dec 2014 08:43:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com> <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com>, <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com> <DB4PR06MB45712A7E15C95A9CAD769D6AD500@DB4PR06MB457.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB45712A7E15C95A9CAD769D6AD500@DB4PR06MB457.eurprd06.prod.outlook.com>
Date: Sun, 28 Dec 2014 08:43:27 -0000
Message-ID: <012a01d0227a$5b731e90$12595bb0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGCS1JsX84DsJPiQ2wIn2tw0hulbgHmbSbhAfIryLgCuxFKggG3QeKtnP4F2yA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21206.006
X-TM-AS-Result: No--2.920-10.0-31-10
X-imss-scan-details: No--2.920-10.0-31-10
X-TMASE-MatchedRID: pBwXUM+nCws4HKI/yaqRmxWCVBr+Ay98NU8z+tFJHR3VHyARSied1JnQ YgiFBiVF9gBmMI9oCMlHC4XEH4hznzoOKuJSTzbfk3rl+MaNgxBYuTsoeO+cJOQydRUvl3QTo/f XwzxROQXi8zVgXoAltlwtzewu2M63tuZmiwj/lnLdB/CxWTRRuwihQpoXbuXFu3srVsce5rCaD7 NeFXSPPnD/69kr69hJLXhRtcFNTBznJbuj3s5Apbc59PGSyJXvllhf0vq8pxtlqq1/FgwT3SwP+ 2v5XIp4CQKeQDeH+fUPvTV19UCLO5Iv06+1Rxr97r4PjzaceGueqD9WtJkSIw==
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/bzEPzdj8Blr42wPuUb9E_A6qX-I
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2014 08:43:32 -0000

Lloyd,

> Tom, a device that can't compute a UDP checksum (ones complement? not hard)
> can't compute a TCP checksum either. What is it doing on the public internet,
and
> why is it the IETF's concern?

This was my thought, too, but...
It has been observed that where UDP is being used as a tunnel the end points of
the tunnel are not end systems and will be processing traffic "at line speed".
It has been claimed that, for some of these, the additional overhead of
processing the UDP checksum will be a step too far.
Possibly this is because the tunnel end points will be in software not in
hardware.
I have no knowledge of these reported devices, but I am assured that they exist.

Adrian


From nobody Sun Dec 28 08:45:03 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91DFA1A8893 for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 08:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 rq6HkjTfDxmI for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 08:44:58 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B4F31A888D for <tsvwg@ietf.org>; Sun, 28 Dec 2014 08:44:58 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id gq1so38884388obb.9 for <tsvwg@ietf.org>; Sun, 28 Dec 2014 08:44:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=evCLtYz982gN3bpTjJfxrZQZZ1U8hWOCPNJgk2fHKYk=; b=Ht795Tcif1fYxfbWKu0DopwW66EPfiO/2uML+uKowYPrV1Urpjskf15KhPRnCLZsKo Uj80oqwXoDbT0N72SmsG8SG62JE0TOBGDPHmNAX6ctQP96VtPMLrI1wsirZJI6ykIlXe ZRrY8ukGRxe+w5P6JU3Kw4WeKvN26ukpoRKMmCLY38uE1C6PUSWFf4zWRm5Uh6P1G2k8 +5e1cUU6ipXjGUspduQ/MoEQm1d8aSNI6ddmrWrO5ssEnnLzEp6biLVRDeulWjF4f59C OTUXjkAqVDRG0OEZhWYkhkK7uIopZGgBYEI8ilx3whufbw7hkWTLOahghA8FSFNDuZ6u v6Ow==
MIME-Version: 1.0
X-Received: by 10.182.120.10 with SMTP id ky10mr30531815obb.68.1419785097928;  Sun, 28 Dec 2014 08:44:57 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Sun, 28 Dec 2014 08:44:57 -0800 (PST)
In-Reply-To: <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com> <CE03DB3D7B45C245BCA0D243277949362CDD5D@MX104CL02.corp.emc.com> <CA+mtBx-Lmgm_uK0PtcWzhmE3QCZsDrhN6eiZ8EZobhG9E6mBwA@mail.gmail.com>
Date: Sun, 28 Dec 2014 08:44:57 -0800
Message-ID: <CAA93jw5qsbxccWQ0KEOymJPvt5jSQScpdCYKTb+xtTFCt+fv6w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Tom Herbert <therbert@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/C9OXPR-ZdMW5q295m1CnKyepKGc
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2014 16:45:02 -0000

On Sat, Dec 27, 2014 at 9:42 AM, Tom Herbert <therbert@google.com> wrote:
> Lloyd, David
>
> Comments inline.
>
> On Fri, Dec 26, 2014 at 8:52 PM, Black, David <david.black@emc.com> wrote=
:
>> Lloyd,
>>
>> <WG chair hat off>
>>
>>> A comment pertaining to checksum use.
>>>
>>> This draft does not discuss that the udp checksum is scoped end to end =
between
>>> hosts, unlike the stronger link layer checksums, and that a strong link
>>> checksum is no substitute for that path functionality.
>>
>> Thanks for a timely comment ...
>>
>>> While recommending the UDP checksum SHOULD be used is a fine default, a=
 rash
>>> of tunnelling protocols have said 'we already have payload protection, =
we
>>> don't need udp checksum compute overhead' and have used the mere existe=
nce of
>>> RFC6395/RFC6396 as justification for turning the checksum off, nuance b=
e
>>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go any=
where
>>> point of view.
>>
>> Indeed, and please have a look at Section 3.1 of draft-ietf-mpls-in-udp-=
09 as a
>> current cross-area (TSV/RTG) attempt to do better:
>>
> draft-ietf-mpls-in-udp-09 and RFC6936 are much more restrictive in the
> use of zero UDP checksum in IPv6 than what is described here. Those
> seem to require that IPv6 UDP checksum MUST be enabled unless certain
> requirements are meant when using UDP tunnels.
>
> It might be good to include the motivation for using zero UDP checksum.
> Presumably, the core motivation is either performance cost of
> computing full checksum or communicating with devices that can't
> compute the checksum.
>
> I would imagine that the majority of devices that terminate UDP are
> end hosts which can already compute UDP checksum, and probably in the
> majority of those there are NICs that offload the UDP checksum so it
> is no performance impact. In these cases, UDP checksum should be
> enabled. In some cases, enabling UDP checksum with tunnels can be a
> performance win over using zero UDP checksum when properly leveraging
> UDP checksum offload capability.

As a reality injection note, I think tom is one of the authors of the new
"fou" (Foo over UDP) infrastructure in linux, which makes it possible
to hand off even
encapsulated checksumming/checking to hardware.

http://lwn.net/Articles/614348/

I have been struggling to find a mental model for how to use it generically=
,
(as in the tinc vpn, for instance)...

> We do know that some devices, switches in particular, will be
> terminating UDP (tunnels) and they may not have the capability to
> compute a UDP checksum. For these, UDP zero checksums are useful (per
> RFC6336), but the case where one of these devices receives a packet
> with a non-zero UDP checksum must be considered. VXLAN (RFC7348) makes
> checksum verification optional, but this seems to be inconsistent with
> RFC1122. I would suggest a requirement something like: "If a UDP
> datagram is received with a checksum that is non-zero and the node is
> unable to verify the checksum, the node MUST discard the datagram."
>
> Thanks,
> Tom
>
>> http://tools.ietf.org/html/draft-ietf-mpls-in-udp-09#section-3.1
>>
>>> I would argue that using UDP Lite to only checksum your UDP/IP header f=
ields
>>> is always preferable to a UDP zero checksum in that then your payload c=
an
>>> still be messed up and that's your problem, but having your corrupted p=
ackets
>>> injected anywhere else is prevented.
>>
>> In principle, sure, I agree, but in practice, there are "running code" p=
roblems
>> with network gear that passes UDP but not UDP-Lite (port-translating NAT=
s are
>> well-known offenders) and more importantly that load balances (ECMP or E=
thernet
>> LAG) UDP traffic, but not UDP-Lite traffic :-(.
>>
>>> A zero udp checksum should always be the
>>> very last option. For IPv6, UDP Lite doing the pseudo header check is f=
ar far
>>> preferable to zero UDP checksum, and the draft should say as much.
>>
>> No argument there in principle, but when UDP-Lite doesn't work in practi=
ce
>> (wrong protocol # in IP header), then what?
>>
>>> (What would it take to have UDP itself be changed to allow two okay val=
ues for
>>> the checksum - checksum is either just across UDP/IP pseudoheaders or f=
ull
>>> payload, and you can incrementally compute pseudoheader on the way to f=
ull, say
>>> 'we matched headers at this point, no need to check rest of payload'. I=
 doubt
>>> it weakens the full payload check significantly, and is a more transpar=
ent
>>> lightweight header check than UDP Lite. no clue what this might do to
>>> middleboxes, though.)
>>
>> A significant concern here is backwards compatibility - middleboxes, end=
 systems,
>> and network mgt/ops tools, although this is something that some new uses=
 of UDP
>> could be encouraged to do with the next header inside UDP (use zero UDP =
checksum
>> and insert a "shim" that includes a checksum of the UDP/IP pseudoheaders=
 and the
>> shim).
>>
>> </WG chair hat off>
>>
>> Thanks,
>> --David
>>
>>
>>> -----Original Message-----
>>> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.=
ac.uk
>>> Sent: Friday, December 26, 2014 12:02 PM
>>> To: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
>>> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>>
>>> A comment pertaining to checksum use.
>>>
>>> This draft does not discuss that the udp checksum is scoped end to end =
between
>>> hosts, unlike the stronger link layer checksums, and that a strong link
>>> checksum is no substitute for that path functionality.
>>>
>>> While recommending the UDP checksum SHOULD be used is a fine default, a=
 rash
>>> of tunnelling protocols have said 'we already have payload protection, =
we
>>> don't need udp checksum compute overhead' and have used the mere existe=
nce of
>>> RFC6395/RFC6396 as justification for turning the checksum off, nuance b=
e
>>> damned. Which is bad from a demultiplexed-corrupted-IPv6-packets go any=
where
>>> point of view.
>>>
>>> I would argue that using UDP Lite to only checksum your UDP/IP header f=
ields
>>> is always preferable to a UDP zero checksum, in that then your payload =
can
>>> still be messed up and that's your problem, but having your corrupted p=
ackets
>>> injected anywhere else is prevented. A zero udp checksum should always =
be the
>>> very last option. For IPv6, UDP Lite doing the pseudo header check is f=
ar far
>>> preferable to zero UDP checksum, and the draft should say as much.
>>>
>>> Please reread the 'By default' paragraph (second para of 3.4.1) - great=
er
>>> should be lesser in this context, as default is full coverage, and you =
can
>>> only go down.
>>>
>>> (What would it take to have UDP itself be changed to allow two okay val=
ues for
>>> the checksum - checksum is either just across UDP/IP pseudoheaders or f=
ull
>>> payload, and you can incrementally compute pseudoheader onthe way to fu=
ll, say
>>> 'we matched headers at this point, no need to check rest of payload'. I=
 doubt
>>> it weakens the full payload check significantly, and is a more transpar=
ent
>>> ligtweight header check than UDP Lite. no clue what this ,ight do to
>>> middleboxes, though.)
>>>
>>> Lloyd Wood
>>> http://about.me/lloydwood
>>>
>>> ________________________________________
>>> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.=
org
>>> <internet-drafts@ietf.org>
>>> Sent: Tuesday, 16 December 2014 3:58:38 AM
>>> To: i-d-announce@ietf.org
>>> Cc: tsvwg@ietf.org
>>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>  This draft is a work item of the Transport Area Working Group Working =
Group
>>> of the IETF.
>>>
>>>         Title           : UDP Usage Guidelines
>>>         Authors         : Lars Eggert
>>>                           Godred Fairhurst
>>>                           Greg Shepherd
>>>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>>>         Pages           : 37
>>>         Date            : 2014-12-15
>>>
>>> Abstract:
>>>    The User Datagram Protocol (UDP) provides a minimal message-passing
>>>    transport that has no inherent congestion control mechanisms.
>>>    Because congestion control is critical to the stable operation of th=
e
>>>    Internet, applications and other protocols that choose to use UDP as
>>>    an Internet transport must employ mechanisms to prevent congestion
>>>    collapse and to establish some degree of fairness with concurrent
>>>    traffic.  They may also need to implement additional mechanisms,
>>>    depending on how they use UDP.
>>>
>>>    This document provides guidelines on the use of UDP for the designer=
s
>>>    of applications, tunnels and other protocols that use UDP.
>>>    Congestion control guidelines are a primary focus, but the document
>>>    also provides guidance on other topics, including message sizes,
>>>    reliability, checksums, and middlebox traversal.
>>>
>>>    If published as an RFC, this document will obsolete RFC5405.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of submi=
ssion
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>
>



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sun Dec 28 19:06:35 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9DA1ACCE7 for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 19:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 yeam0VRQzxsa for <tsvwg@ietfa.amsl.com>; Sun, 28 Dec 2014 19:06:31 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 47DD11ACC86 for <tsvwg@ietf.org>; Sun, 28 Dec 2014 19:06:31 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id 0FA812B449C; Mon, 29 Dec 2014 03:06:29 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Mon, 29 Dec 2014 03:06:29 -0000
Message-ID: <f5f68738a01685f58d2026a7b49548f5.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>
Date: Mon, 29 Dec 2014 03:06:29 -0000
From: gorry@erg.abdn.ac.uk
To: l.wood@surrey.ac.uk
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/-Bln2cMMSFjUrd7j7OFjmfsuuPA
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 03:06:35 -0000

Hi Lloyd,

> A comment pertaining to checksum use.
>
> This draft does not discuss that the udp checksum is scoped end to end
> between hosts, unlike the stronger link layer checksums, and that a strong
> link checksum is no substitute for that path functionality.
>
> While recommending the UDP checksum SHOULD be used is a fine default, a
> rash of tunnelling protocols have said 'we already have payload
> protection, we don't need udp checksum compute overhead' and have used the
> mere existence of RFC6395/RFC6396 as justification for turning the
> checksum off, nuance be damned. Which is bad from a
> demultiplexed-corrupted-IPv6-packets go anywhere point of view.
>
> I would argue that using UDP Lite to only checksum your UDP/IP header
> fields is always preferable to a UDP zero checksum, in that then your
> payload can still be messed up and that's your problem, but having your
> corrupted packets injected anywhere else is prevented. A zero udp checksum
> should always be the very last option. For IPv6, UDP Lite doing the pseudo
> header check is far far preferable to zero UDP checksum, and the draft
> should say as much.
>
> Please reread the 'By default' paragraph (second para of 3.4.1) - greater
> should be lesser in this context, as default is full coverage, and you can
> only go down.
>
> (What would it take to have UDP itself be changed to allow two okay values
> for the checksum - checksum is either just across UDP/IP pseudoheaders or
> full payload, and you can incrementally compute pseudoheader onthe way to
> full, say 'we matched headers at this point, no need to check rest of
> payload'. I doubt it weakens the full payload check significantly, and is
> a more transparent ligtweight header check than UDP Lite. no clue what
> this might do to middleboxes, though.)
>
> Lloyd Wood
> http://about.me/lloydwood
>
I agree that the draft has to be updated to include better guidance on the
checksum position, and we'll try to do that. The text above seems like a
reasonable list of things to include.

As someone who would like to see UDP-Lite-style checksums in UDP, I'd
support your proposal to explore what would happen if UDP-Lite were to be
used over port 17 rather than just port 136. Is what you are proposing
similar to:
https://tools.ietf.org/html/draft-fairhurst-6man-tsvwg-udptt-03

Since  this was written in 2010, my research group has grown some tools
that could now be used to test deployability and I'm hoping we can do some
middlebox traversal experiments to explore how deployable this may be
early next year... thoughts and other ideas welcome.

Gorry


> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.org
> <internet-drafts@ietf.org>
> Sent: Tuesday, 16 December 2014 3:58:38 AM
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Transport Area Working Group Working
> Group of the IETF.
>
>         Title           : UDP Usage Guidelines
>         Authors         : Lars Eggert
>                           Godred Fairhurst
>                           Greg Shepherd
>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>         Pages           : 37
>         Date            : 2014-12-15
>
> Abstract:
>    The User Datagram Protocol (UDP) provides a minimal message-passing
>    transport that has no inherent congestion control mechanisms.
>    Because congestion control is critical to the stable operation of the
>    Internet, applications and other protocols that choose to use UDP as
>    an Internet transport must employ mechanisms to prevent congestion
>    collapse and to establish some degree of fairness with concurrent
>    traffic.  They may also need to implement additional mechanisms,
>    depending on how they use UDP.
>
>    This document provides guidelines on the use of UDP for the designers
>    of applications, tunnels and other protocols that use UDP.
>    Congestion control guidelines are a primary focus, but the document
>    also provides guidance on other topics, including message sizes,
>    reliability, checksums, and middlebox traversal.
>
>    If published as an RFC, this document will obsolete RFC5405.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>


From nobody Mon Dec 29 00:05:02 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3510D1A000C for <tsvwg@ietfa.amsl.com>; Mon, 29 Dec 2014 00:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 QFvdHFDz4GKx for <tsvwg@ietfa.amsl.com>; Mon, 29 Dec 2014 00:04:52 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.110]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE991A000B for <tsvwg@ietf.org>; Mon, 29 Dec 2014 00:04:52 -0800 (PST)
Received: from [193.109.255.147] by server-6.bemta-14.messagelabs.com id A8/18-03145-22B01A45; Mon, 29 Dec 2014 08:04:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-72.messagelabs.com!1419840290!15441426!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13034 invoked from network); 29 Dec 2014 08:04:50 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-4.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 29 Dec 2014 08:04:50 -0000
Received: from EXHY012V.surrey.ac.uk (131.227.201.103) by EXHT022P.surrey.ac.uk (131.227.200.43) with Microsoft SMTP Server (TLS) id 8.3.342.0; Mon, 29 Dec 2014 08:04:49 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY012v.surrey.ac.uk (131.227.201.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 29 Dec 2014 08:04:49 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB460.eurprd06.prod.outlook.com (10.141.238.24) with Microsoft SMTP Server (TLS) id 15.1.49.12; Mon, 29 Dec 2014 08:04:49 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0049.002; Mon, 29 Dec 2014 08:04:49 +0000
From: <l.wood@surrey.ac.uk>
To: <gorry@erg.abdn.ac.uk>
Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
Thread-Index: AQHQGIiA7ep7+aI6xkCPD7T1km5VR5yiJMaugAPTCoCAAEr+UA==
Date: Mon, 29 Dec 2014 08:04:49 +0000
Message-ID: <DB4PR06MB45782561FC8FF6E516EBE00AD510@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>, <f5f68738a01685f58d2026a7b49548f5.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <f5f68738a01685f58d2026a7b49548f5.squirrel@spey.erg.abdn.ac.uk>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [78.105.8.76]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-forefront-prvs: 0440AC9990
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(51704005)(377424004)(377454003)(15198665003)(2351001)(54606007)(97736003)(76576001)(230783001)(40100003)(76176999)(54206007)(110136001)(21056001)(120916001)(19580395003)(77096005)(92566001)(33656002)(4396001)(74482002)(54356999)(50986999)(106116001)(46102003)(99396003)(2501002)(106356001)(15395725005)(87936001)(2656002)(122556002)(74316001)(2900100001)(561944003)(1720100001)(68736005)(77156002)(101416001)(19580405001)(64706001)(2950100001)(102836002)(107046002)(86362001)(31966008)(20776003)(66066001)(62966003)(15975445007); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB460; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: surrey.ac.uk does not designate permitted sender hosts)
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Dec 2014 08:04:49.2194 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b902693-1074-40aa-9e21-d89446a2ebb5
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB460
X-OrganizationHeadersPreserved: DB4PR06MB460.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY012v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/1HHIrwjr8DKIcmW8QZkYAwXXf34
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 08:04:58 -0000

Gorry,

We agree that lite fuctionality is really only useful when it covers the ud=
p header, which is why you give a udp length field of 8. Partial payload co=
verage for additional headers and payloads is nice, but generally rarely us=
ed.

But code does rely on that udp length field, which is why udp lite wasn't a=
 simple in-place upgrade to port 17. Many years of reaching rough consensus=
 on udp lite was defeated by the running udp code.

My suggestion differs from your udptt: leave the length field as is, so sti=
ll full udp length, but the checksum can represent either the full payload =
check or the header length 8-byte check. No indication of which it is is gi=
ven - but the header 8-byte check is done on the way to computing the full =
payload check. If you know you only want to do the header check, if the 8-b=
yte header check passes, stop and you're good. If that doesn't pass, you ca=
n continue and do the full udp payload checksum if you want. The risk of a =
header checksum being corrupted to match a full-length checksum when a pack=
et is damaged is low - most middlebox damage is likely payload truncation. =
The added overhead of pausing at 8 and checking that value is low - and is =
only done by endhosts that care, and they gain in those cases from not doin=
g the full payload check.

My belief is that not messing with the udp length field at all will get eas=
ier access through middleboxes than flagging 8 bytes in that field, because=
 procssing can key off that length field, while incremental udp checksum fi=
xups after NAT etc will be preserved. Messing with the length field breaks =
the semantics of the UDP standard, and that's why Lite got booted to a diff=
erent port; subtly overloading the udp checksum field to have two acceptabl=
e values, one for fixed header length, one for full payload length, does no=
t.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: gorry@erg.abdn.ac.uk <gorry@erg.abdn.ac.uk>
Sent: Monday, 29 December 2014 2:06:29 PM
To: Wood L  Dr (Electronic Eng)
Cc: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt

Hi Lloyd,

> A comment pertaining to checksum use.
>
> This draft does not discuss that the udp checksum is scoped end to end
> between hosts, unlike the stronger link layer checksums, and that a stron=
g
> link checksum is no substitute for that path functionality.
>
> While recommending the UDP checksum SHOULD be used is a fine default, a
> rash of tunnelling protocols have said 'we already have payload
> protection, we don't need udp checksum compute overhead' and have used th=
e
> mere existence of RFC6395/RFC6396 as justification for turning the
> checksum off, nuance be damned. Which is bad from a
> demultiplexed-corrupted-IPv6-packets go anywhere point of view.
>
> I would argue that using UDP Lite to only checksum your UDP/IP header
> fields is always preferable to a UDP zero checksum, in that then your
> payload can still be messed up and that's your problem, but having your
> corrupted packets injected anywhere else is prevented. A zero udp checksu=
m
> should always be the very last option. For IPv6, UDP Lite doing the pseud=
o
> header check is far far preferable to zero UDP checksum, and the draft
> should say as much.
>
> Please reread the 'By default' paragraph (second para of 3.4.1) - greater
> should be lesser in this context, as default is full coverage, and you ca=
n
> only go down.
>
> (What would it take to have UDP itself be changed to allow two okay value=
s
> for the checksum - checksum is either just across UDP/IP pseudoheaders or
> full payload, and you can incrementally compute pseudoheader onthe way to
> full, say 'we matched headers at this point, no need to check rest of
> payload'. I doubt it weakens the full payload check significantly, and is
> a more transparent ligtweight header check than UDP Lite. no clue what
> this might do to middleboxes, though.)
>
> Lloyd Wood
> http://about.me/lloydwood
>
I agree that the draft has to be updated to include better guidance on the
checksum position, and we'll try to do that. The text above seems like a
reasonable list of things to include.

As someone who would like to see UDP-Lite-style checksums in UDP, I'd
support your proposal to explore what would happen if UDP-Lite were to be
used over port 17 rather than just port 136. Is what you are proposing
similar to:
https://tools.ietf.org/html/draft-fairhurst-6man-tsvwg-udptt-03

Since  this was written in 2010, my research group has grown some tools
that could now be used to test deployability and I'm hoping we can do some
middlebox traversal experiments to explore how deployable this may be
early next year... thoughts and other ideas welcome.

Gorry


> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of internet-drafts@ietf.or=
g
> <internet-drafts@ietf.org>
> Sent: Tuesday, 16 December 2014 3:58:38 AM
> To: i-d-announce@ietf.org
> Cc: tsvwg@ietf.org
> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Transport Area Working Group Working
> Group of the IETF.
>
>         Title           : UDP Usage Guidelines
>         Authors         : Lars Eggert
>                           Godred Fairhurst
>                           Greg Shepherd
>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>         Pages           : 37
>         Date            : 2014-12-15
>
> Abstract:
>    The User Datagram Protocol (UDP) provides a minimal message-passing
>    transport that has no inherent congestion control mechanisms.
>    Because congestion control is critical to the stable operation of the
>    Internet, applications and other protocols that choose to use UDP as
>    an Internet transport must employ mechanisms to prevent congestion
>    collapse and to establish some degree of fairness with concurrent
>    traffic.  They may also need to implement additional mechanisms,
>    depending on how they use UDP.
>
>    This document provides guidelines on the use of UDP for the designers
>    of applications, tunnels and other protocols that use UDP.
>    Congestion control guidelines are a primary focus, but the document
>    also provides guidance on other topics, including message sizes,
>    reliability, checksums, and middlebox traversal.
>
>    If published as an RFC, this document will obsolete RFC5405.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>


From nobody Mon Dec 29 00:37:57 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD42C1A0055 for <tsvwg@ietfa.amsl.com>; Mon, 29 Dec 2014 00:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vkTiC-7iTnhM for <tsvwg@ietfa.amsl.com>; Mon, 29 Dec 2014 00:37:48 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 78F0C1A00A2 for <tsvwg@ietf.org>; Mon, 29 Dec 2014 00:37:26 -0800 (PST)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 33) id CB8892B449D; Mon, 29 Dec 2014 08:37:25 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by spey.erg.abdn.ac.uk with HTTP; Mon, 29 Dec 2014 08:37:25 -0000
Message-ID: <d03cc434d6a9fd11bdf825ab5835eda2.squirrel@spey.erg.abdn.ac.uk>
In-Reply-To: <DB4PR06MB45782561FC8FF6E516EBE00AD510@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <20141215165838.31657.16907.idtracker@ietfa.amsl.com> <DB4PR06MB457E2947ABE51CBE5470217AD520@DB4PR06MB457.eurprd06.prod.outlook.com>, <f5f68738a01685f58d2026a7b49548f5.squirrel@spey.erg.abdn.ac.uk> <DB4PR06MB45782561FC8FF6E516EBE00AD510@DB4PR06MB457.eurprd06.prod.outlook.com>
Date: Mon, 29 Dec 2014 08:37:25 -0000
From: gorry@erg.abdn.ac.uk
To: l.wood@surrey.ac.uk
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/nb-pXSEBs_0F7OGT2R0fEoEjhAc
Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 08:37:52 -0000

OK - Lloyd, I recall part of the "history" was that at the time, UDP-Lite
was standardised people were advocating different "protocol" values for
different transports - at this point in Internet history it is entirely
possible a different approach may have made its way through the IESG.

I understand the proposal below, and agree that (like UDPTT) it will take
very few additional cycles to process.

Since these are targeted at the edge, I suggest we need to understand the
chances of middlebox traversal for either of the methods - and I will try
to look at these early next year.

Gorry

> Gorry,
>
> We agree that lite fuctionality is really only useful when it covers the
> udp header, which is why you give a udp length field of 8. Partial payload
> coverage for additional headers and payloads is nice, but generally rarely
> used.
>
> But code does rely on that udp length field, which is why udp lite wasn't
> a simple in-place upgrade to port 17. Many years of reaching rough
> consensus on udp lite was defeated by the running udp code.
>
> My suggestion differs from your udptt: leave the length field as is, so
> still full udp length, but the checksum can represent either the full
> payload check or the header length 8-byte check. No indication of which it
> is is given - but the header 8-byte check is done on the way to computing
> the full payload check. If you know you only want to do the header check,
> if the 8-byte header check passes, stop and you're good. If that doesn't
> pass, you can continue and do the full udp payload checksum if you want.
> The risk of a header checksum being corrupted to match a full-length
> checksum when a packet is damaged is low - most middlebox damage is likely
> payload truncation. The added overhead of pausing at 8 and checking that
> value is low - and is only done by endhosts that care, and they gain in
> those cases from not doing the full payload check.
>
> My belief is that not messing with the udp length field at all will get
> easier access through middleboxes than flagging 8 bytes in that field,
> because procssing can key off that length field, while incremental udp
> checksum fixups after NAT etc will be preserved. Messing with the length
> field breaks the semantics of the UDP standard, and that's why Lite got
> booted to a different port; subtly overloading the udp checksum field to
> have two acceptable values, one for fixed header length, one for full
> payload length, does not.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: gorry@erg.abdn.ac.uk <gorry@erg.abdn.ac.uk>
> Sent: Monday, 29 December 2014 2:06:29 PM
> To: Wood L  Dr (Electronic Eng)
> Cc: tsvwg@ietf.org; gorry@erg.abdn.ac.uk; lars@netapp.com
> Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>
> Hi Lloyd,
>
>> A comment pertaining to checksum use.
>>
>> This draft does not discuss that the udp checksum is scoped end to end
>> between hosts, unlike the stronger link layer checksums, and that a
>> strong
>> link checksum is no substitute for that path functionality.
>>
>> While recommending the UDP checksum SHOULD be used is a fine default, a
>> rash of tunnelling protocols have said 'we already have payload
>> protection, we don't need udp checksum compute overhead' and have used
>> the
>> mere existence of RFC6395/RFC6396 as justification for turning the
>> checksum off, nuance be damned. Which is bad from a
>> demultiplexed-corrupted-IPv6-packets go anywhere point of view.
>>
>> I would argue that using UDP Lite to only checksum your UDP/IP header
>> fields is always preferable to a UDP zero checksum, in that then your
>> payload can still be messed up and that's your problem, but having your
>> corrupted packets injected anywhere else is prevented. A zero udp
>> checksum
>> should always be the very last option. For IPv6, UDP Lite doing the
>> pseudo
>> header check is far far preferable to zero UDP checksum, and the draft
>> should say as much.
>>
>> Please reread the 'By default' paragraph (second para of 3.4.1) -
>> greater
>> should be lesser in this context, as default is full coverage, and you
>> can
>> only go down.
>>
>> (What would it take to have UDP itself be changed to allow two okay
>> values
>> for the checksum - checksum is either just across UDP/IP pseudoheaders
>> or
>> full payload, and you can incrementally compute pseudoheader onthe way
>> to
>> full, say 'we matched headers at this point, no need to check rest of
>> payload'. I doubt it weakens the full payload check significantly, and
>> is
>> a more transparent ligtweight header check than UDP Lite. no clue what
>> this might do to middleboxes, though.)
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>>
> I agree that the draft has to be updated to include better guidance on the
> checksum position, and we'll try to do that. The text above seems like a
> reasonable list of things to include.
>
> As someone who would like to see UDP-Lite-style checksums in UDP, I'd
> support your proposal to explore what would happen if UDP-Lite were to be
> used over port 17 rather than just port 136. Is what you are proposing
> similar to:
> https://tools.ietf.org/html/draft-fairhurst-6man-tsvwg-udptt-03
>
> Since  this was written in 2010, my research group has grown some tools
> that could now be used to test deployability and I'm hoping we can do some
> middlebox traversal experiments to explore how deployable this may be
> early next year... thoughts and other ideas welcome.
>
> Gorry
>
>
>> ________________________________________
>> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of
>> internet-drafts@ietf.org
>> <internet-drafts@ietf.org>
>> Sent: Tuesday, 16 December 2014 3:58:38 AM
>> To: i-d-announce@ietf.org
>> Cc: tsvwg@ietf.org
>> Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rfc5405bis-00.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the Transport Area Working Group Working
>> Group of the IETF.
>>
>>         Title           : UDP Usage Guidelines
>>         Authors         : Lars Eggert
>>                           Godred Fairhurst
>>                           Greg Shepherd
>>         Filename        : draft-ietf-tsvwg-rfc5405bis-00.txt
>>         Pages           : 37
>>         Date            : 2014-12-15
>>
>> Abstract:
>>    The User Datagram Protocol (UDP) provides a minimal message-passing
>>    transport that has no inherent congestion control mechanisms.
>>    Because congestion control is critical to the stable operation of the
>>    Internet, applications and other protocols that choose to use UDP as
>>    an Internet transport must employ mechanisms to prevent congestion
>>    collapse and to establish some degree of fairness with concurrent
>>    traffic.  They may also need to implement additional mechanisms,
>>    depending on how they use UDP.
>>
>>    This document provides guidelines on the use of UDP for the designers
>>    of applications, tunnels and other protocols that use UDP.
>>    Congestion control guidelines are a primary focus, but the document
>>    also provides guidance on other topics, including message sizes,
>>    reliability, checksums, and middlebox traversal.
>>
>>    If published as an RFC, this document will obsolete RFC5405.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-00
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>

