IETF Logo Mail Archive

Re: What CSRs Do

Frode Kileng <frodeki@gmail.com> Tue, 19 November 2019 05:57 UTC

Return-Path: <frodeki@gmail.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 94CF3120801 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 21:57:14 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 bpbYedeZhMfw for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C795120046 for <quic@ietf.org>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id az9so11145645plb.11 for <quic@ietf.org>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=zJtEqTO7GC43oJvbpUgxkumHXB6RxC86xdSXcOZXhj8=; b=D3+R1eW96UtDhxeN0yqV0fLrXLYtGz+HvSXBynXznhnRAOC2z+pJnQYMUG40DuiqPt 2OSyHqSucj05rellaMtOMQXzVb0Md2Y+mDfUjUa4LWQGOPs4jHaYMAuYmt/xz+QVwfKB nQGcNPcE/syWThCM9Ro/sFX4LLcBETizkM1mqvo9WsSLU5q0XM7Fu1jtm4Aycg2Mh/eo 9MqLTYOg8hr9pYdWGQl9MKP18KObxG1mpCpRTWa/QsdrOrju3bfBU8SwZZznMvpndDmx lSvDuOu9pZzFDVUqcnifaR1QcJOMYRy/IN8JcceOVf/5zw8Muo7anP6PCVph7FIOc7+n ypjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=zJtEqTO7GC43oJvbpUgxkumHXB6RxC86xdSXcOZXhj8=; b=FMZ3A4fudAQ94YDayodpI/kNMXRk0mxekWoV7F3d2kZsG9sCVm1qEkEdEVNHdSWJzM X/phliYT8pvfmb4/BIFUgzHelOV4LtDsIhwveze/gynhNqyGTw8Ek25FKCYN/VMRwT8z SNY7oGYSU0jh4DYCtzZcdCVzrAyiYXGUBh27a1h4vIqkCtbFTC+JzSnu+dLn64KJtml5 TeIay9VYc1y/80CLDanWOnF1dBbtYTwJHlNOUPl8Dq1VqEj+5h1R7FH0ekCwc9E2yQAZ 9+SbrCpzvyg3RCpHg4c2TfCnPxFMCGdUIdQ3RO0huXHWoXvNXWMXMFPWp44zvI+0tszY IRYQ==
X-Gm-Message-State: APjAAAW4zWla5m5EVBC+AOTHmikUtB5x9LIbaEzh9aDPWXfuGtniABME C2Pp6Kx6Dxe7L3bUgL4QXIFChtQ4
X-Google-Smtp-Source: APXvYqyn2pLkAiZNFyMpS959+HyPPimBLu6uqtsA3xMVd/I/6uTbSF23ytjQC8QTOGio3geZc+BD0w==
X-Received: by 2002:a17:902:74c6:: with SMTP id f6mr33674062plt.167.1574143031151; Mon, 18 Nov 2019 21:57:11 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:deb:727b:9d2c:94c1? ([2001:67c:370:128:deb:727b:9d2c:94c1]) by smtp.googlemail.com with ESMTPSA id c9sm25493105pfb.114.2019.11.18.21.57.09 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Nov 2019 21:57:10 -0800 (PST)
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>
From: Frode Kileng <frodeki@gmail.com>
Message-ID: <4003626d-8966-6772-7df0-e76549320430@gmail.com>
Date: Tue, 19 Nov 2019 06:57:07 +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: <20191119042904.GC5602@1wt.eu>
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/ejHl4v7S-56hhd94e9hQ2sb7Pyo>
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 05:57:15 -0000

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?

frodek

v2.23.0 | Report a Bug | By Email