Thanks for this update! I think this is an improvement. I do think there are still some changes needed, perhaps related to some ambiguity in one of my suggestions.
I imagined "bg-priority" as a uint16 that overrides SvcPriority when in Background mode. The connection sequence would look like: 1. Collect SVCB records 2. If in background mode, replace SvcPriority by bg-priority in any record where it is present 3. Sort by SvcPriority. 4. Proceed with connection establishment. The current proposal is not a replacement priority. Instead, it is a filter. I would call it "background-use" or simply "background". These proposals have notably distinct properties: "replacement priority" cannot represent "background-only" or "foreground-only" records, but a "background-use=0/1" filter creates a footgun that can make a service partially unreachable. I can see some appeal in both approaches, but I wonder: do we really want clients to fail hard if the designated background endpoints are unreachable? And will clients actually obey this directive when they are holding a potentially valid, functional endpoint? --Ben ________________________________ From: Gautam Akiwate <[email protected]> Sent: Tuesday, July 1, 2025 6:23 PM To: DNSOP Working Group <[email protected]> Cc: Tommy Pauly <[email protected]>; Ben Schwartz <[email protected]> Subject: New Version Notification for draft-gakiwate-dnsop-svcb-bg-priority-parameter (Previously draft-gakiwate-dnsop-svcb-sla-parameter) Greetings, We have updated our draft to "Service Binding Mapping for Background Requests”. Based on the feedback for the first draft, we renamed and narrowed the scope of the draft. The SvcParamKey is now called “bg-priority” which indicates Greetings, We have updated our draft to "Service Binding Mapping for Background Requests”. Based on the feedback for the first draft, we renamed and narrowed the scope of the draft. The SvcParamKey is now called “bg-priority” which indicates if a service endpoint is optimized (in most cases it is because it is cheaper) for background requests (latency-tolerant requests). The client can dynamically use their local context to decide if a specific requests is appropriate for background handling. We would greatly appreciate the working group’s continued feedback on the updated proposal. Thanks Gautam Begin forwarded message: From: [email protected] Subject: New Version Notification for draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.txt Date: June 25, 2025 at 11:05:35 AM PDT To: Gautam Akiwate <[email protected]>, Tommy Pauly <[email protected]> A new version of Internet-Draft draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.txt has been successfully submitted by Gautam Akiwate and posted to the IETF repository. Name: draft-gakiwate-dnsop-svcb-bg-priority-parameter Revision: 00 Title: Service Binding Mapping for Background Requests Date: 2025-06-25 Group: Individual Submission Pages: 7 URL: https://www.ietf.org/archive/id/draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.txt<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.txt__;!!Bt8RZUm9aw!7DXTC_0fWDyPUl-2YhsOFgcqrSijwrl3mT2rfDZc04roHWRtRAZDu5srpbHzgOm8tbST6AoJ4r56$> Status: https://datatracker.ietf.org/doc/draft-gakiwate-dnsop-svcb-bg-priority-parameter/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-gakiwate-dnsop-svcb-bg-priority-parameter/__;!!Bt8RZUm9aw!7DXTC_0fWDyPUl-2YhsOFgcqrSijwrl3mT2rfDZc04roHWRtRAZDu5srpbHzgOm8tbST6PyRXpUg$> HTML: https://www.ietf.org/archive/id/draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.html<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-gakiwate-dnsop-svcb-bg-priority-parameter-00.html__;!!Bt8RZUm9aw!7DXTC_0fWDyPUl-2YhsOFgcqrSijwrl3mT2rfDZc04roHWRtRAZDu5srpbHzgOm8tbST6Idd79Wz$> HTMLized: https://datatracker.ietf.org/doc/html/draft-gakiwate-dnsop-svcb-bg-priority-parameter<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-gakiwate-dnsop-svcb-bg-priority-parameter__;!!Bt8RZUm9aw!7DXTC_0fWDyPUl-2YhsOFgcqrSijwrl3mT2rfDZc04roHWRtRAZDu5srpbHzgOm8tbST6P_5m5dE$> Abstract: This document defines a new SvcParamKey for use in Service Binding (SVCB) and HTTPS DNS resource records which enables authoritative DNS servers to indicate that a client can use an alternative endpoint for "background" requests. By providing this information, clients can make informed decisions about which service endpoints to use based on their specific applications needs at the time of making connections. The IETF Secretariat
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
