RE: Spin bit discussion - where we're at - use case exsist!!!
Roni Even <roni.even@huawei.com> Thu, 23 November 2017 06:13 UTC
Return-Path: <roni.even@huawei.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 4F7F4120721 for <quic@ietfa.amsl.com>; Wed, 22 Nov 2017 22:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 G-4kBeZEQw-2 for <quic@ietfa.amsl.com>; Wed, 22 Nov 2017 22:13:32 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 178ED1205F1 for <quic@ietf.org>; Wed, 22 Nov 2017 22:13:32 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 2B5604888C527 for <quic@ietf.org>; Thu, 23 Nov 2017 06:13:29 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 23 Nov 2017 06:13:29 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.96]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0361.001; Thu, 23 Nov 2017 14:13:26 +0800
From: Roni Even <roni.even@huawei.com>
To: Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>
CC: Lars Eggert <lars@netapp.com>
Subject: RE: Spin bit discussion - where we're at - use case exsist!!!
Thread-Topic: Spin bit discussion - where we're at - use case exsist!!!
Thread-Index: AdNkIisC9xIKNWiHQVCTDxaJDE0Wug==
Date: Thu, 23 Nov 2017 06:13:25 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD8464CB@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.203.55]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WXKit4CNcz44cFg2KmBbwEUVqpg>
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 Nov 2017 06:13:33 -0000
<snip> > > 1) A description of the use case(s) that motivate this proposal. We > understand that the goal is to measure RTT, but some people are still unclear > as to why that's necessary to operate a network. Detailed scenarios and > ideally real-world examples (e.g., from TCP) would help tremendously. > Saying "I need to debug the network" is not enough detail. > [Roni Even] I submitted such a document but I assume that nobody read it since I would expect that this bullet will at least mention it !!! See https://tools.ietf.org/id/draft-even-quic-troubleshooting-video-delivery-00.tx Please read the document Roni