RFC 8433 on A Simpler Method for Resolving Alert-Info URNs
rfc-editor@rfc-editor.org Mon, 27 August 2018 19:02 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 B407112F1AB for <ietf-announce@ietfa.amsl.com>; Mon, 27 Aug 2018 12:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 QA_kQ26iumJZ for <ietf-announce@ietfa.amsl.com>; Mon, 27 Aug 2018 12:02: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 367AC130EDE for <ietf-announce@ietf.org>; Mon, 27 Aug 2018 12:02:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 75379B80C3A; Mon, 27 Aug 2018 12:02:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8433 on A Simpler Method for Resolving Alert-Info URNs
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: <20180827190231.75379B80C3A@rfc-editor.org>
Date: Mon, 27 Aug 2018 12:02:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/un-IdCGWMBshq73R273ObQqP4Nk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 27 Aug 2018 19:02:51 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8433
Title: A Simpler Method for Resolving
Alert-Info URNs
Author: D. Worley
Status: Informational
Stream: Independent
Date: August 2018
Mailbox: worley@ariadne.com
Pages: 45
Characters: 89902
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-worley-alert-info-fsm-10.txt
URL: https://www.rfc-editor.org/info/rfc8433
DOI: 10.17487/RFC8433
The "alert" namespace of Uniform Resource Names (URNs) can be used in
the Alert-Info header field of Session Initiation Protocol (SIP)
requests and responses to inform a voice over IP (VoIP) telephone
(user agent) of the characteristics of the call that the user agent
has originated or terminated. The user agent must resolve the URNs
into a signal; that is, it must select the best available signal to
present to its user to indicate the characteristics of the call.
RFC 7462 describes a non-normative algorithm for signal selection.
This document describes a more efficient alternative algorithm: a
user agent's designer can, based on the user agent's signals and
their meanings, construct a finite state machine (FSM) to process the
URNs to select a signal in a way that obeys the restrictions given in
the definition of the "alert" URN namespace.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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