[rfc-dist] STD 95, RFC 7481 on Security Services for the Registration Data Access Protocol (RDAP)

rfc-editor@rfc-editor.org Tue, 23 March 2021 05:32 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7903A1E60 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Mar 2021 22:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 v_z1wpSeJkTo for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Mar 2021 22:32:49 -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 DAFF03A1E90 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 22 Mar 2021 22:32:48 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DD638F40775; Mon, 22 Mar 2021 22:32:40 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 5C17FF40774; Mon, 22 Mar 2021 22:32:40 -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
Message-Id: <20210323053240.5C17FF40774@rfc-editor.org>
Date: Mon, 22 Mar 2021 22:32:40 -0700
Subject: [rfc-dist] STD 95, RFC 7481 on Security Services for the Registration Data Access Protocol (RDAP)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, weirds@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

RFC 7481 has been elevated to Internet Standard.

        STD 95        
        RFC 7481

        Title:      Security Services for the Registration 
                    Data Access Protocol (RDAP) 
        Author:     S. Hollenbeck,
                    N. Kong
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2015
        Pages:      13
        See Also:   STD 95

        I-D Tag:    draft-ietf-weirds-rdap-sec-12.txt

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

        DOI:        10.17487/RFC7481

The Registration Data Access Protocol (RDAP) provides "RESTful" web
services to retrieve registration metadata from Domain Name and
Regional Internet Registries.  This document describes information
security services, including access control, authentication,
authorization, availability, data confidentiality, and data integrity
for RDAP.

This document is a product of the Web Extensible Internet Registration Data Service Working Group of the IETF.

This is now an Internet 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org