A new Request for Comments is now available in online RFC libraries.
RFC 5115
Title: Telephony Routing over IP (TRIP)
Attribute for Resource Priority
Author: K. Carlberg, P. O'Hanlon
Status: Standards Track
Date: January 2008
Mailbox: carlberg@g11.org.uk,
p.ohanlon@cs.ucl.ac.uk
Pages: 8
Characters: 17194
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-carlberg-trip-attribute-rp-04.txt
URL: http://www.rfc-editor.org/rfc/rfc5115.txt
This document defines a new attribute for the Telephony Routing over
IP (TRIP) protocol. The attribute associates protocols/services in
the PSTN offering authorized prioritization during call setup that are
reachable through a TRIP gateway. Current examples of preferential
service in the Public Switched Telephone Network (PSTN) are Government
Emergency Telecommunications Service (GETS) in the U.S. and Government
Telephone Preference Scheme (GTPS) in the U.K. The proposed attribute
for TRIP is based on the NameSpace.Value tuple defined for the SIP
Resource-Priority field. [STANDARDS TRACK]
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
