[salud] Fwd: RFC 8433 on A Simpler Method for Resolving Alert-Info URNs]

worley@ariadne.com (Dale R. Worley) Thu, 30 August 2018 02:06 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090B1130EE8 for <salud@ietfa.amsl.com>; Wed, 29 Aug 2018 19:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level:
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 VtN-2-gCmeOk for <salud@ietfa.amsl.com>; Wed, 29 Aug 2018 19:06:33 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BBFF130EE0 for <salud@ietf.org>; Wed, 29 Aug 2018 19:06:32 -0700 (PDT)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id vBW8f8Kd4PUIwvCLufbRyd; Thu, 30 Aug 2018 02:06:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1535594790; bh=QDYaSKoPz6jPgU2kwtOt+26fP4s7jnOa5btTkTpITJ4=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Iq0SUJ/7mpb2sdEvnRpidrfanYwA9X2u7Ihkh6KHIcQUVljBVgsFkmed6P1PFh9RP QNzPQ0cSFTEKaa30mN/91LJMq6KX8h6qgTZffzrK/gZz3RmhNZPi/5GoPjtTnAzAGm ZHyIjArquE7nrPBdaZDp1BZRIB26SOAo50Gv89tgh2ZXV2fn7RYuB3b4PU30KQrQRM xn8+oqy1iq6aNpLKew+ALxgWDbb0kGtPXzKxw0+Yq16kQplb+2S1z/bUSlmQBaq98J j9fM9jy7lJYknHjyteiA+a7F2yzhtnZAckTrtfoskAttQiZ0Xfn930Wl9DhB5hOb+4 y45o0XCUlcvuw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-07v.sys.comcast.net with ESMTPA id vCLsfr9zKnlxFvCLtfLIWu; Thu, 30 Aug 2018 02:06:30 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w7U26RNC018103 for <salud@ietf.org>; Wed, 29 Aug 2018 22:06:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w7U26R9L018098; Wed, 29 Aug 2018 22:06:27 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: salud@ietf.org
Sender: worley@ariadne.com (Dale R. Worley)
Date: Wed, 29 Aug 2018 22:06:27 -0400
Message-ID: <874lfc4nh8.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfHXXVpCcVNSgEaJyRK6QDUwZv9xnD0vujm/Rm7QnFqRSgRnsDFpjda/oR4HUd7w3G6UJ5dfsdh1tL2SfXGrc0/jEiA4tCkY4VkQnkEInKHdo81KhbM90 1/56kiUe0li8yDe/0yuJNMV0Cz3Zp7ts4DfpAV/Tq6Nv5cb0z1PZnq89ulLItTcwcFL5m2QicqAaHrtnABDWAjuV5BZO3JIZj6U9zZmlTUHstKUUbuKFH9zf Sf8bM8LPZ5fcQAm5RrtrOw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/salud/LOkyIDDB4uL-24ZjyIKsRlxZJ4Q>
Subject: [salud] Fwd: RFC 8433 on A Simpler Method for Resolving Alert-Info URNs]
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/salud/>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2018 02:06:43 -0000

-------- Forwarded Message --------
Subject: RFC 8433 on A Simpler Method for Resolving Alert-Info URNs
Date: Mon, 27 Aug 2018 12:02:31 -0700 (PDT)
From: rfc-editor@rfc-editor.org
Reply-To: ietf@ietf.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org

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