Subject: [Sipping] RE: I-D ACTION:draft-sinnreich-sipdev-req-07.txt

From: "Gunnar Hellstrom" <[email-masked]>
Date: Mon, 13 Jun 2005 23:21:16 +0200

Henry,
This is a good specification.
I would like to make you aware of that the revision of RFC 2793 RTP Payload for text
conversation, now is ready and published as RFC 4103 RTP Payload for text conversation. It
has made RFC 2793 obsolete. During the work it was called draft-ietf-avt-rfc2793bis

This publication influences the issued sip device requirements draft and any other
specification being specific about codecs for general SIP conversational sessions.

It influences draft-sinnreich-sipdev-req-07.txt in the following way:

1. In references, delete reference [70]

2. In reference 56,  change "draft-ietf-avt-rfc2793bis-09.txt, IETF, August 2004,
   work in progress." To "RFC 4103, IETF, June 2005."

3. In REQ-52, delete reference [70]

4. In Req 55, Req 56, Req 57, change "2793" to "4103"

Regards

Gunnar

-------------------------------------------
Gunnar Hellstrom
Omnitor AB
Renathvagen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
[email-masked]
--------------------------------------------

>-----Original Message-----
>From: [email-masked]
>[mailto:[email-masked]]On Behalf Of
>[email-masked]
>Sent: Monday, June 13, 2005 9:39 PM
>To: [email-masked]
>Subject: I-D ACTION:draft-sinnreich-sipdev-req-07.txt
>
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>	Title		: SIP Telephony Device Requirements and Configuration
>	Author(s)	: H. Sinnreich, et al.
>	Filename	: draft-sinnreich-sipdev-req-07.txt
>	Pages		: 37
>	Date		: 2005-6-13
>
>This document describes the requirements for SIP telephony devices,
>   based on the deployment experience of large numbers of SIP phones and
>   PC clients using different implementations in various networks.  The
>   objectives of the requirements are a well defined set of
>   interoperability and multi-vendor supported core features, so as to
>   enable similar ease of purchase, installation and operation as found
>   for PCs, PDAs analog feature phones or mobile phones.
>
>   We present a glossary of the most common settings and some of the
>   more widely used values for some settings.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-07.txt
>
>To remove yourself from the I-D Announcement list, send a message to
>[email-masked] with the word unsubscribe in the body of the message.
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
>
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>	"get draft-sinnreich-sipdev-req-07.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>	[email-masked].
>In the body type:
>	"FILE /internet-drafts/draft-sinnreich-sipdev-req-07.txt".
>
>NOTE:	The mail server at ietf.org can return the document in
>	MIME-encoded form by using the "mpack" utility.  To use this
>	feature, insert the command "ENCODING mime" before the "FILE"
>	command.  To decode the response(s), you will need "munpack" or
>	a MIME-compliant mail reader.  Different MIME-compliant mail readers
>	exhibit different behavior, especially when dealing with
>	"multipart" MIME messages (i.e. documents which have been split
>	up into multiple messages), so check your local documentation on
>	how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP