IETF Logo Mail Archive

Re: What CSRs Do

Frode Kileng <frodek@tele.no> Tue, 19 November 2019 07:44 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 71E1512087C for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:44:26 -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 4_3G6BPbt9TK for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:44:24 -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 8552A12084A for <quic@ietf.org>; Mon, 18 Nov 2019 23:44:24 -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=zGx50eJW2O6+cNETe6a88pkXKJMFJTQuRoCyUR+FJyI=; b=Wo9p0v4s+APFcQxNa4YlKZq6rn nLYxpoX7uYtFb2hShWHVojR98H4bCqzzTYx8tz8oryiPvBiAOUE1H3mqMRhQpRiLQWgevtmv98Utv Fjq8K87adgqwwBNjqCVjeI7ZKYFrM+juGM4PdlCGmPR1AhT/tFm0MgT9B/qtgFp5hphy37NzWlh4P vHmbNCBPUmTz5zUba2xxsvQnnxNncf8lQdfYuH/6qGa6BmJ+EJZQfyl2AtjRFCuXYYnekAfU3UtYn 3tECITJpnOvOTS+FEOaJDPiBU+Li3Qh8DMBlY8HZKjjA8e4rLgWpwZYefhr2aL+g7OQh+GkJim79Q 8oOJ6fMw==;
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 1iWyBQ-0004ic-Tc; Tue, 19 Nov 2019 08:44:21 +0100
Subject: Re: What CSRs Do
To: quic@ietf.org, w@1wt.eu
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> <20191119073220.GA5824@1wt.eu>
From: Frode Kileng <frodek@tele.no>
Message-ID: <f40867ba-37ba-1be9-a00b-e61dfb23187e@tele.no>
Date: Tue, 19 Nov 2019 08:44:17 +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: <20191119073220.GA5824@1wt.eu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7jTflU24Q25it976ryC1bfUtE0w>
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 07:44:26 -0000

On 19/11/2019 08:32, Willy Tarreau wrote:
> On Tue, Nov 19, 2019 at 06:57:07AM +0100, Frode Kileng wrote:
>> On 19/11/2019 05:29, Willy Tarreau wrote:
>>> The only known alternative is to claim "we have no loss here" and point the
>>> finger at the next step in the chain operated by someone else.
>> What additional value can "loss bit(s)" provide beyond confirming that the
>> source is within your network domain or somewhere else, i.e. information
>> that is available from other "loss sources". How would network operators use
>> this loss bit(s) signal when providing such "excellent customer support"
>> when the problem source is external?
> I find your condescending tone inappropriate to discuss technical matters.

I'm very surprised as this was questions I asked trying to understand 
the benefits of the loss bit(s). As a non-native speaker, and after 
having looked  up the word "condescending", I understand that I should 
avoid further discussion on this topic in fear of being misinterpreted.

frodek

v2.23.0 | Report a Bug | By Email