IETF Logo Mail Archive

Re: FIN + RST behavior

Subodh Iyengar <subodh@fb.com> Thu, 23 March 2017 17:09 UTC

Return-Path: <prvs=4255290284=subodh@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB001294BD for <quic@ietfa.amsl.com>; Thu, 23 Mar 2017 10:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=lDlA1gfN; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=WDh/Su5l
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 eHfpbMKbwDnJ for <quic@ietfa.amsl.com>; Thu, 23 Mar 2017 10:09:17 -0700 (PDT)
Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D60D012998C for <quic@ietf.org>; Thu, 23 Mar 2017 10:09:16 -0700 (PDT)
Received: from pps.filterd (m0109332.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2NH3Iss008333; Thu, 23 Mar 2017 10:09:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=4xydGK5qKjapcZt3kU3d6YGR6qoUdSlhx8JFpORA/k8=; b=lDlA1gfN0J65777byzhVlzCF3Hdu5I9+nZMsxyBM6JHaUQ03Ef8Y9PDi3bIrhIcm9Pmw GEAtvpATX3XU0XYGa7ok8epJEVQGkbK3rKIJWAjHQsoL39MFVTlwevtBcon5m2JX9HZa hqRZGPD5qJzQqRfMs0a9zFlhvxdNRErZq5E=
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 29ca0tjc8k-2 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Mar 2017 10:09:15 -0700
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.14) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 23 Mar 2017 10:09:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=4xydGK5qKjapcZt3kU3d6YGR6qoUdSlhx8JFpORA/k8=; b=WDh/Su5lpCVFu1m1AEudX1vN8QcUMISuUaXD0GVoH36r3wNoEe6OVAeySnYDYYoJUwmvNfTxNOHJFU3Sc74vy4Augq4CN7qJXA5qOujo3/ZyrGzCs9SaKC1bhMMxnguQG/9Gt2uovRBF1+qIBTQiOsuWRiCD6QQu6sRNyxcvZ9Q=
Received: from MWHPR15MB1455.namprd15.prod.outlook.com (10.173.234.145) by MWHPR15MB1454.namprd15.prod.outlook.com (10.173.234.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.977.11; Thu, 23 Mar 2017 17:09:11 +0000
Received: from MWHPR15MB1455.namprd15.prod.outlook.com ([10.173.234.145]) by MWHPR15MB1455.namprd15.prod.outlook.com ([10.173.234.145]) with mapi id 15.01.0977.021; Thu, 23 Mar 2017 17:09:11 +0000
From: Subodh Iyengar <subodh@fb.com>
To: Martin Thomson <martin.thomson@gmail.com>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: Re: FIN + RST behavior
Thread-Topic: FIN + RST behavior
Thread-Index: AQHSo1zPcZTZN/tlZkuJR+NHZURtjKGhltKAgAAu7CCAAH4YAIAAZDLN
Date: Thu, 23 Mar 2017 17:09:11 +0000
Message-ID: <MWHPR15MB1455956FFF7AB6730C1E345CB63F0@MWHPR15MB1455.namprd15.prod.outlook.com>
References: <MWHPR15MB1455B5E6D4F4FAC8411927E4B63C0@MWHPR15MB1455.namprd15.prod.outlook.com> <CABkgnnVRo_mT7sPO=xvmMdS-6wAJoSpARp+FG1R8i-RQWqE8Lg@mail.gmail.com> <MWHPR15MB145521D729498455F923679EB63F0@MWHPR15MB1455.namprd15.prod.outlook.com>, <CABkgnnVZCp8QBVPe81_9=JsrsAYLpy2KkWtfgY9pWcspoKBMSw@mail.gmail.com>
In-Reply-To: <CABkgnnVZCp8QBVPe81_9=JsrsAYLpy2KkWtfgY9pWcspoKBMSw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-Mentions: martin.thomson@gmail.com
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=fb.com;
x-originating-ip: [25.173.47.4]
x-microsoft-exchange-diagnostics: 1; MWHPR15MB1454; 7:QlRUqPgjdHzr1T5Gmw+/sKhHTA3fdWtlat0u1yGZaKl3lBGMrsviT6nZzYCXJSfmhnSmp2OHnj2T9O5+ksMPUackNczO0ml487I7eOVBm803i03nH8oi+Ullr+ARWk3bCREZjsSNAKHlDFhTIc3DFIUqo6EDYq7LzbAHSYbwX+FN2fbeSByPM/K4n/QPeFF7FxDKZeH0cgfkYx751jyGIV89OamqaSkeNWwqjo+kUcOwZANieggjWPBnDVSsdJj1R8V4r8L0BgoZItKF+DgC/hie7M8+gxUPRl0nUBrsZzv5sSEQceam/QP4WzwuUEH8/jWAmnrKBfXCEi1l2d/z6g==; 20:uNmhlm11M36iJRqMXEOaSwNkxShi7vh8FkJicpfPJ8M3OXRWRSyhxQ/p2kIMI0TrfH06Zq3aTyaOKvPowSlkL1b3j4WrNkyikdFBOxtLbyu/RM0Jnoyd6eeDsT3GxGtTH88vI3WzVV24Fy/Nsk8/4kx3mfjo+CV1ECwczGK+KCo=
x-ms-office365-filtering-correlation-id: c0734e48-41a7-48f1-3300-08d4720f53a2
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075); SRVR:MWHPR15MB1454;
x-microsoft-antispam-prvs: <MWHPR15MB1454A825A946D3B2322A11BFB63F0@MWHPR15MB1454.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(67672495146484);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123560025)(20161123562025)(20161123558025)(6072148); SRVR:MWHPR15MB1454; BCL:0; PCL:0; RULEID:; SRVR:MWHPR15MB1454;
x-forefront-prvs: 0255DF69B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39410400002)(39450400003)(39830400002)(377454003)(24454002)(3846002)(54896002)(236005)(122556002)(39060400002)(99286003)(55016002)(102836003)(9686003)(6116002)(110136004)(6246003)(6506006)(6436002)(4326008)(8936002)(8676002)(25786009)(81166006)(53936002)(53546009)(77096006)(38730400002)(3280700002)(93886004)(86362001)(2900100001)(74316002)(3660700001)(7736002)(2906002)(561944003)(54356999)(76176999)(33656002)(50986999)(66066001)(5660300001)(6916009)(2950100002)(189998001)(7696004)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR15MB1454; H:MWHPR15MB1455.namprd15.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR15MB1455956FFF7AB6730C1E345CB63F0MWHPR15MB1455namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Mar 2017 17:09:11.8016 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR15MB1454
X-OriginatorOrg: fb.com
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-23_15:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NNcG42mVX8mcWCy9cqJhLBjTrtg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 17:09:19 -0000

>  The client can consider its own resources to be available for use by
the server as soon as it receives the FIN and processes it.  If this
were a server resource, then you are right, it's not that simple
because the client can't assume that the server has released state
yet.

Ya in the case of the previous example, it is a server resource since it's a client initiated stream.
@Martin Thomson<mailto:martin.thomson@gmail.com> I'm starting to like your proposal of unidirectional streams more and more :)


Subodh


________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson <martin.thomson@gmail.com>
Sent: Thursday, March 23, 2017 4:04:46 AM
To: Subodh Iyengar
Cc: quic@ietf.org
Subject: Re: FIN + RST behavior

On 23 March 2017 at 15:10, Subodh Iyengar <subodh@fb.com> wrote:
> How does the client know when the server has released a slot in it's
> concurrency limit? The server can't immediately release this when it sends
> out the FIN because it still must keep state until it receives all the
> ACKs for the stream. I think the client need to keep track of the ACK of the
> ACKs of all the server sent bytes in the stream, which would be a bit sad.


The client can consider its own resources to be available for use by
the server as soon as it receives the FIN and processes it.  If this
were a server resource, then you are right, it's not that simple
because the client can't assume that the server has released state
yet.

v2.23.0 | Report a Bug | By Email