RFC 8602 on Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses
rfc-editor@rfc-editor.org Tue, 09 July 2019 23:11 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 24CBF1200F6 for <ietf-announce@ietfa.amsl.com>; Tue, 9 Jul 2019 16:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 UoRb8CFvGUFN for <ietf-announce@ietfa.amsl.com>; Tue, 9 Jul 2019 16:11:06 -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 690CC1200C3 for <ietf-announce@ietf.org>; Tue, 9 Jul 2019 16:11:06 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B8207B812B2; Tue, 9 Jul 2019 16:11:03 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8602 on Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses
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: <20190709231103.B8207B812B2@rfc-editor.org>
Date: Tue, 09 Jul 2019 16:11:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/BlX4Z-u5wCRWM-ZD_TXjt5J2Pag>
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: Tue, 09 Jul 2019 23:11:08 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8602 Title: Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses Author: J. Arkko, T. Hardie Status: Standards Track Stream: IETF Date: July 2019 Mailbox: jari.arkko@piuha.net, ted.ietf@gmail.com Pages: 3 Characters: 4619 Updates: RFC 3219 I-D Tag: draft-arkko-trip-registry-update-01.txt URL: https://www.rfc-editor.org/info/rfc8602 DOI: 10.17487/RFC8602 This memo updates the IANA registry rules for the Telephony Routing over IP (TRIP) protocol, by no longer requiring that postal addresses be included in contact information. This memo updates RFC 3219. 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