[dnssd] RFC 8765 on DNS Push Notifications

rfc-editor@rfc-editor.org Tue, 23 June 2020 04:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAC2A3A1739; Mon, 22 Jun 2020 21:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 f3g_quP0cUJZ; Mon, 22 Jun 2020 21:29:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF31C3A1796; Mon, 22 Jun 2020 21:29:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 27D0AF407A2; Mon, 22 Jun 2020 21:29:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnssd@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200623042912.27D0AF407A2@rfc-editor.org>
Date: Mon, 22 Jun 2020 21:29:12 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/ljhVXNnMEaI9pfPVKEpMXDC4xhw>
Subject: [dnssd] =?utf-8?q?RFC_8765_on_DNS_Push_Notifications?=
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2020 04:30:04 -0000

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

        
        RFC 8765

        Title:      DNS Push Notifications 
        Author:     T. Pusateri,
                    S. Cheshire
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    pusateri@bangj.com, 
                    cheshire@apple.com
        Pages:      32
        Updates/Obsoletes/SeeAlso:   None

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

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

        DOI:        10.17487/RFC8765

The Domain Name System (DNS) was designed to return matching records
efficiently for queries for data that are relatively static.  When
those records change frequently, DNS is still efficient at returning
the updated results when polled, as long as the polling rate is not
too high. But, there exists no mechanism for a client to be
asynchronously notified when these changes occur.  This document
defines a mechanism for a client to be notified of such changes to
DNS records, called DNS Push Notifications.

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
Association Management Solutions, LLC