[Ecrit] Reference to real-time text in draft-rosen-ecrit-framework-00.txt

Gunnar Hellstrom <gunnar.hellstrom@omnitor.se> Wed, 19 July 2006 04:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G33Jd-0006A9-DL; Wed, 19 Jul 2006 00:05:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G33Jc-0006A1-I0 for ecrit@ietf.org; Wed, 19 Jul 2006 00:05:40 -0400
Received: from pne-smtpout2-sn1.fre.skanova.net ([81.228.11.159]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G33Jb-0005t3-6O for ecrit@ietf.org; Wed, 19 Jul 2006 00:05:40 -0400
Received: from Misan (213.64.228.153) by pne-smtpout2-sn1.fre.skanova.net (7.2.075) id 44A135F100452544; Wed, 19 Jul 2006 06:05:32 +0200
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
To: "Brian Rosen(br)" <br@brianrosen.net>, "Ecrit@Ietf. Org" <ecrit@ietf.org>
Date: Wed, 19 Jul 2006 06:05:25 +0100
Message-ID: <CCEIKIABCPCLIACIPNMKGEIMCFAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-Reply-To: <E1Ft8i9-0003ly-Ns@stiedprstage1.ietf.org>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc:
Subject: [Ecrit] Reference to real-time text in draft-rosen-ecrit-framework-00.txt
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ecrit.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
Errors-To: ecrit-bounces@ietf.org

I have some small comments on the good draft draft-rosen-ecrit-framework-00

1. In section 12, Media, there is a reference to RFC2793bis that now can be
changed to the published RFC 4103 "RTP Payload for Text Conversation".

Also change "interactive text" to "real-time text" as IETF nomenclature has
now settled for this feature.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Old text in section 12:
PSAPs should accept interactive text [I-D.ietf-avt-
   rfc2793bis].

New text:
PSAPs should accept real-time text [RFC4103].
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


2. In section 18.1 , references, replace reference to rfc2793bis with rfc
4103
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Old text in section 18.1:
   [I-D.ietf-avt-rfc2793bis]
              Hellstrom, G., "RTP Payload for Text Conversation",
              draft-ietf-avt-rfc2793bis-09 (work in progress),
              August 2004.
New text:
   [RFC4103]  Hellstrom, G. and Jones, P. "RTP Payload for Text
              Conversation", RFC 4103, May 2005.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Gunnar Hellstrom
----------------------------------------------------------------------------
-
Gunnar Hellstrom, Omnitor
gunnar.hellstrom@omnitor.se
www.omnitor.se


-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Wednesday, June 21, 2006 8:50 PM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-rosen-ecrit-framework-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Framework for Emergency Calling in Internet
                          Multimedia
	Author(s)	: B. Rosen, et al.
	Filename	: draft-rosen-ecrit-framework-00.txt
	Pages		: 32
	Date		: 2006-6-21

   Summoning emergency help by the public is a core feature of telephone
   networks.  This document describes a framework of how various IETF
   protocols are combined to place emergency calls.  This includes how
   these calls are routed to the correct Public Safety Answering Point
   (PSAP) based on the physical location of the caller, while providing
   the call taker the necessary information to dispatch a first
   responder to that location.  This document explains how location
   mapping, call identification and end system behavior are combined to
   allow multimedia emergency calls.  It describes at a high level how
   the pieces (recognizing a call as an emergency call, marking it as
   such, determining the location of the caller, routing the call based
   on location) go together, and references the Internet standards that
   define the details of these mechanisms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-rosen-ecrit-framework-00.txt




_______________________________________________
Ecrit mailing list
Ecrit@ietf.org
https://www1.ietf.org/mailman/listinfo/ecrit