RFC 8917 on The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag
rfc-editor@rfc-editor.org Thu, 22 October 2020 21:10 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2EA93A1053 for <ietf-announce@ietfa.amsl.com>; Thu, 22 Oct 2020 14:10:26 -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=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 neL8N4QqNesO for <ietf-announce@ietfa.amsl.com>; Thu, 22 Oct 2020 14:10:24 -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 8F0DD3A104C for <ietf-announce@ietf.org>; Thu, 22 Oct 2020 14:10:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6DA8AF4071A; Thu, 22 Oct 2020 14:10:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8917 on The LoST-Validation Straightforward-Naming Authority PoinTeR (S-NAPTR) Application Service Tag
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201022211018.6DA8AF4071A@rfc-editor.org>
Date: Thu, 22 Oct 2020 14:10:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/L_zZ6t7kF0OqiUkCq8JsydmtKFM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 22 Oct 2020 21:10:27 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8917
Title: The LoST-Validation Straightforward-Naming Authority
PoinTeR (S-NAPTR) Application Service Tag
Author: R. Gellens, B. Rosen
Status: Standards Track
Stream: IETF
Date: October 2020
Mailbox: rg+ietf@coretechnologyconsulting.com,
br@brianrosen.net
Pages: 7
Updates: RFC 5222
I-D Tag: draft-gellens-lost-validation-09.txt
URL: https://www.rfc-editor.org/info/rfc8917
DOI: 10.17487/RFC8917
This document adds the 'LoST-Validation' service tag to the
Straightforward-Naming Authority PoinTeR (S-NAPTR) Application
Service Tag IANA registry. This tag can appear in a Naming Authority
Pointer (NAPTR) Domain Name System (DNS) record to assist clients of
the Location-to-Service Translation (LoST) Protocol in identifying
LoST servers designated for location validation. This tag and the
information about its use update RFC 5222, which enables the explicit
discovery of a server that supports location validation.
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