[rfc-dist] RFC 4730 on A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Nov 14 16:22:15 PST 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4730

        Title:      A Session Initiation Protocol (SIP) 
                    Event Package for Key Press Stimulus 
        Author:     E. Burger, M. Dolly
        Status:     Standards Track
        Date:       November 2006
        Mailbox:    eburger at cantata.com, 
                    mdolly at att.com
        Pages:      56
        Characters: 120186
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-kpml-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4730.txt

This document describes a SIP Event Package "kpml" that enables
monitoring of Dual Tone Multi-Frequency (DTMF) signals and uses
Extensible Markup Language (XML) documents referred to as Key Press
Markup Language (KPML).  The kpml Event Package may be used to
support applications consistent with the principles defined in the
document titled "A Framework for Application Interaction in the
Session Initiation Protocol (SIP)".  The event package uses SUBSCRIBE
messages and allows for XML documents that define and describe filter
specifications for capturing key presses (DTMF Tones) entered at a
presentation-free User Interface SIP User Agent (UA).  The event
package uses NOTIFY messages and allows for XML documents to report
the captured key presses (DTMF tones), consistent with the filter
specifications, to an Application Server.  The scope of this package
is for collecting supplemental key presses or mid-call key presses
(triggers).  [STANDARDS TRACK]

This document is a product of the Session Initiation Proposal 
Investigation Working Group of the IETF.

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 

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list