RFC 7480 on HTTP Usage in the Registration Data Access Protocol (RDAP)
rfc-editor@rfc-editor.org Wed, 25 March 2015 20:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF7241A8ACA; Wed, 25 Mar 2015 13:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 bBe9YEr2Vgti; Wed, 25 Mar 2015 13:53:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 836461A8869; Wed, 25 Mar 2015 13:53:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A4E00180472; Wed, 25 Mar 2015 13:51:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7480 on HTTP Usage in the Registration Data Access Protocol (RDAP)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150325205134.A4E00180472@rfc-editor.org>
Date: Wed, 25 Mar 2015 13:51:34 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/E4l71tx9IsNjfs-1FGYYguXjAjI>
Cc: drafts-update-ref@iana.org, weirds@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2015 20:53:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7480
Title: HTTP Usage in the Registration
Data Access Protocol (RDAP)
Author: A. Newton, B. Ellacott,
N. Kong
Status: Standards Track
Stream: IETF
Date: March 2015
Mailbox: andy@arin.net,
bje@apnic.net,
nkong@cnnic.cn
Pages: 16
Characters: 34671
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-weirds-using-http-15.txt
URL: https://www.rfc-editor.org/info/rfc7480
This document is one of a collection that together describes the
Registration Data Access Protocol (RDAP). It describes how RDAP is
transported using the Hypertext Transfer Protocol (HTTP). RDAP is a
successor protocol to the very old WHOIS protocol. The purpose of
this document is to clarify the use of standard HTTP mechanisms for
this application.
This document is a product of the Web Extensible Internet Registration Data Service 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/rfc.html
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