IETF Logo Mail Archive

Re: What CSRs Do

Frode Kileng <frodek@tele.no> Tue, 19 November 2019 06:42 UTC

Return-Path: <frodek@tele.no>
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 7912D1200A4 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:42:15 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tele.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 KWqH3eHgyzYw for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:42:14 -0800 (PST)
Received: from gorgon.tele.no (gorgon.tele.no [IPv6:2001:700:800::70]) (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 0F6D7120876 for <quic@ietf.org>; Mon, 18 Nov 2019 22:42:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tele.no; s=20180731; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=AOJrLZ2ZR811zJjBO+xhBxpicgWp1pcOojdsNitNyvs=; b=JRrxh0ZdimHXiV+TFWwVY6Hn+L yXaXoW3A1To2NL7wFwTeqYNVGa9qlquIzDxTAP7BCDm1n4j0bMBmIuBVQ+Sz4Qpc3Lpd++ypHGgtr pR6+l9f4X6GogNm1ElRd4yz6Qb5lelYaQNYZ3fw9OeYqdJ/1RthgI5jryVGqS2NjboF+tDc10OyT5 ksxZtODfFGFc4dyxDUaVGRKejOv8psC6gGo2xjQJFlDEdQw1QoaAc84zlWtBwTcwvY4eWoaEx7/qV KtewRq69NG5KhfM9IsbB2DB7Sf2NnGJXkyEnpRWQlZIt6H3Cp3ZnlDh3wH6zxyyieJRKtV/46B4/Z t9mG8cJA==;
Received: from pilt1.tele.no ([2001:700:800::20] helo=[127.0.0.1]) by gorgon.tele.no with esmtp (Exim 4.92) (envelope-from <frodek@tele.no>) id 1iWxDH-0004gm-KT for quic@ietf.org; Tue, 19 Nov 2019 07:42:12 +0100
Subject: Re: What CSRs Do
To: quic@ietf.org
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com>
From: Frode Kileng <frodek@tele.no>
Message-ID: <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
Date: Tue, 19 Nov 2019 07:42:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <1574144751435.15844@akamai.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xz9Saou6lrN0t3sVj9q2JkN9hGI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 Nov 2019 06:42:15 -0000

On 19/11/2019 07:25, Lubashev, Igor wrote:
>
> This is assuming there is a robust set of "other 'loss source'" available. This is far from reality for the vast majority of cases.

So then there's two alternatives: a) Standardize a "loss-signal" option 
in QUIC and hope this is implemented and supported. b) Network operators 
lacking a "robust set of other loss sources" obtain such sources.

frodek

v2.23.0 | Report a Bug | By Email