[DNSOP] Re: Comments on "Service Binding Mapping for Service Levels"

Joe Abley <jabley@strandkip.nl> Fri, 25 July 2025 10:40 UTC

Return-Path: <jabley@strandkip.nl>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 38E8A4B05BA9 for <dnsop@mail2.ietf.org>; Fri, 25 Jul 2025 03:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=strandkip.nl
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7A3A_9R2IHK9 for <dnsop@mail2.ietf.org>; Fri, 25 Jul 2025 03:40:04 -0700 (PDT)
Received: from dane.soverin.net (dane.soverin.net [185.233.34.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 58FDA4B05B9F for <dnsop@ietf.org>; Fri, 25 Jul 2025 03:40:04 -0700 (PDT)
Received: from smtp.soverin.net (unknown [10.10.4.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by dane.soverin.net (Postfix) with ESMTPS id 4bpPX34YCKz13rF; Fri, 25 Jul 2025 10:40:03 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.100]) by soverin.net (Postfix) with ESMTPSA id 4bpPX324SJzNG; Fri, 25 Jul 2025 10:40:03 +0000 (UTC)
Authentication-Results: smtp.soverin.net; dkim=pass (2048-bit key; unprotected) header.d=strandkip.nl header.i=@strandkip.nl header.a=rsa-sha256 header.s=soverin1 header.b=QR2QGQtk; dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=strandkip.nl; s=soverin1; t=1753440003; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2eTqfPA44JvzCDwTXPdqjuBYdRKUgadBCZg1Q2KSmT4=; b=QR2QGQtkkjtRMrDQhXEUg0oWdIsCt455ouRD2CISaQnoattrTqfdzt12SEn3ON9qElbdbU 8eFFZ10iw5SnU8P2sOq2PHi5HDL9RKbYctjfEEiqf8E8nYopHiE0/PpN5vgKdcHObUOmvD Px1nUFYzfYoDeIYDWp7+mrn2Suw3+hqyuwZzdRlP2SCujBCGbmzYYyAxPPnI1teE3zdX6V BcVsfbl3hr/7IfLABLOCwTRt96tNnSSEtqRRUtsGAYpyf+e9CoC7cU5gfex0R6VNj6R2nE YdK/TnYQuk7xxe8BbQuXFKJ0kfiI8SqCCuI396d2BCxsFGMRPFYHOZr7xiS6kw==
X-CM-Analysis: v=2.4 cv=UsCZN/wB c=1 sm=1 tr=0 ts=68835f03 a=uZw_3lL1AAAA:8 a=WME33P67j9hwcfhD7ysA:9 a=CjuIK1q_8ugA:10 a=V-d8IvcW_LCoMwBhdcUA:9 a=nWF8hKChnjVN5yUX:21 a=_W_S_7VecoQA:10 a=QEXdDO2ut3YA:10 a=izJwDFX-b3pl2plFB0Pf:22
Content-Type: multipart/alternative; boundary="Apple-Mail-46BABBA2-CB90-43B2-845D-36F59E812B9B"
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@strandkip.nl>
Mime-Version: 1.0 (1.0)
Date: Fri, 25 Jul 2025 12:39:52 +0200
Message-Id: <7AC9BE70-79C7-483B-B302-8E414FC2C818@strandkip.nl>
References: <CAKC-DJggUeEMNMXsSsG4DD1vksrvCeGwknXLGRPzrmBozPqZgg@mail.gmail.com>
In-Reply-To: <CAKC-DJggUeEMNMXsSsG4DD1vksrvCeGwknXLGRPzrmBozPqZgg@mail.gmail.com>
To: Erik Nygren <erik+ietf@nygren.org>
X-Spampanel-Class: ham
Message-ID-Hash: NWWSSOTRYIQMXULI2MBBUJ2QZEZAUNAA
X-Message-ID-Hash: NWWSSOTRYIQMXULI2MBBUJ2QZEZAUNAA
X-MailFrom: jabley@strandkip.nl
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Working Group DNSOP <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: Comments on "Service Binding Mapping for Service Levels"
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oHT33b2BQ1ov9dzs-d4G4ddN4zo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

On 25 Jul 2025, at 12:21, Erik Nygren <erik+ietf@nygren.org> wrote:

> As another top-level comment on this draft:
> 
> For at least some operators, deploying safely will also require having a way for clients to signal which SVCB record was used.  For example, load reporting, debugging/diagnostics, and other operational use-cases would need to know whether the background or interactive SVCB endpoint was used.  

From the server side, presumably you know whether a particular client's connection followed the background route because it will land on the background target. But this is also the case if you use a different name.


Joe