RFC 9665 on Service Registration Protocol for DNS-Based Service Discovery

rfc-editor@rfc-editor.org Thu, 12 June 2025 01:26 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 51B2033F1855; Wed, 11 Jun 2025 18:26:52 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 2DDEC263712; Wed, 11 Jun 2025 18:26:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9665 on Service Registration Protocol for DNS-Based Service Discovery
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250612012652.2DDEC263712@rfcpa.rfc-editor.org>
Date: Wed, 11 Jun 2025 18:26:52 -0700
Message-ID-Hash: T2UOMFYNSU2ZSUTGMBFRCVLWUNBYZRTH
X-Message-ID-Hash: T2UOMFYNSU2ZSUTGMBFRCVLWUNBYZRTH
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnssd@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6wRuZWNBwE036mkdKb1qzbdS5E0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9665

        Title:      Service Registration Protocol for DNS-Based 
                    Service Discovery 
        Author:     T. Lemon,
                    S. Cheshire
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2025
        Mailbox:    mellon@fugue.com,
                    cheshire@apple.com
        Pages:      36
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnssd-srp-25.txt

        URL:        https://www.rfc-editor.org/info/rfc9665

        DOI:        10.17487/RFC9665

The Service Registration Protocol (SRP) for DNS-based Service
Discovery (DNS-SD) uses the standard DNS Update mechanism to enable
DNS-SD using only unicast packets.  This makes it possible to deploy
DNS-SD without multicast, which greatly improves scalability and
improves performance on networks where multicast service is not an
optimal choice, particularly IEEE 802.11 (Wi-Fi) and IEEE 802.15.4
networks.  DNS-SD Service registration uses public keys and SIG(0) to
allow services to defend their registrations.

This document is a product of the Extensions for Scalable DNS Service Discovery Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team