ned.freed | 4 Apr 2002 20:47

IESG review of draft-ietf-vpim-address-02.txt

The IESG reviewed this document today and had some comments:

(1) The term "RHS" needs to be defined in addition to "LHS" in section
    2. (Missed this one, sorry.)

(2) The term "onramp" is used but not defined. A definition or a reference
    needs to be included in the document.

(3) The RFC Editor is pushing back on acronyms in titles and abstracts.
    "VPIM" should be expanded in both places.

(4) References need to be split into two groups: Normative and non-normative.

(5) The address iana <at> isi.edu needs to be changed to iana <at> iana.org throughout.

That's it!

				Ned
----------------------------------------------------------
This message was sent to you, since you are subscribed to
vpim <at> lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo

Áö¿µ | 5 Apr 2002 02:44

Re: ..

미성년 출입금지구역

한국성인입장

[ 수신거부 ]

---------------------------------------------------------- This message was sent to you, since you are subscribed to vpim <at> lists.neystadt.org. You can manage your subscription at http://www.neystadt.org/cgi-bin/majordomo

Vidhu Bennie | 8 Apr 2002 10:24
Picon
Favicon

Plz Help

Hi,

I wouls like to know from where will I get the floating point code for GSM-AMR Decoder..??

Please help me..

- Vidhu.

 

 


Do You Yahoo!?
Get personalised at My Yahoo!.
Glenn Parsons | 8 Apr 2002 14:33

IETF 53 VPIM WG minutes

Folks,

Please review the attached minutes from our meeting at IETF 53.

Many thanks to Greg White for being our scribe.

Let me know if you have any comments on these by Thursday, as I will be
sending them in to the IETF on Friday.

Cheers,

Glenn.

Attachment (IETF53 VPIM WG minutes.txt): application/msword, 10 KiB
Internet-Drafts | 9 Apr 2002 14:40
Picon
Favicon

I-D ACTION:draft-ema-vpim-clid-04.txt

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

	Title		: Calling Line Identification for Voice Mail Messages
	Author(s)	: G. Parsons, J. Maruszak
	Filename	: draft-ema-vpim-clid-04.txt
	Pages		: 9
	Date		: 08-Apr-02
	
This document describes a method for identifying the originating   calling party in the headers of a stored
voice mail message.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ema-vpim-clid-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ema-vpim-clid-04.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:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ema-vpim-clid-04.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.
Attachment: message/external-body, 131 bytes
Attachment (draft-ema-vpim-clid-04.txt): message/external-body, 67 bytes
Glenn Parsons | 9 Apr 2002 15:10

WG Last Call #2 on Calling Line ID

Folks,

This is a two week Working Group last call notice for the Calling Line Identification for Voice Mail Messages draft to end on April 23rd.  This draft is to go to Proposed Standard RFC status.  

A notable change confirmed at the IETF 53 discussions (i.e., allowance for a structured telephone number), resulted in the latest draft.  At the WG we agreed to hold a second WG last call. 

The intent of this draft is to provide a minimal header for CLID information received over a telephone line.  It was agreed that if a more complicated header (that would get information from SS7 or ISUP) is desired, then it would be documented in a future separate draft.   I would encourage you to review this latest draft and provide any comments to the list.

The draft is in the Internet repositories:

http://www.ietf.org/internet-drafts/draft-ema-vpim-clid-04.txt

Thanks in advance for your help in reviewing this draft.

Cheers,
Glenn Parsons
VPIM WG co-chair

Internet-Drafts | 15 Apr 2002 13:29
Picon
Favicon

I-D ACTION:draft-ietf-vpim-cc-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Voice Profile for Internet Mail Working Group of the IETF.

	Title		: Critical Content MIME Parameter
	Author(s)	: E. Burger
	Filename	: draft-ietf-vpim-cc-06.txt
	Pages		: 18
	Date		: 12-Apr-02
	
This document describes the use of a mechanism for identifying body 
parts that a sender deems critical in a multi-part Internet mail 
message.  The mechanism described is a parameter to Content-
Disposition, as described by RFC 3204. 
By knowing what parts of a message the sender deems critical, a 
content gateway can intelligently handle multi-part messages when 
providing gateway services to systems of lesser capability.  
Critical content can help a content gateway to decide what parts to 
forward.  It can indicate how hard a gateway should try to deliver a 
body part.  It can help the gateway to pick body parts that are safe 
to silently delete when a system of lesser capability receives a 
message.  In addition, critical content can help the gateway chose 
the notification strategy for the receiving system.  Likewise, if 
the sender expects the destination to do some processing on a body 
part, critical content allows the sender to mark body parts that the 
receiver must process.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-vpim-cc-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ietf-vpim-cc-06.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:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-vpim-cc-06.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.
Attachment: message/external-body, 130 bytes
Attachment (draft-ietf-vpim-cc-06.txt): message/external-body, 67 bytes
James Salsman | 17 Apr 2002 18:06

Audio/AMR MIME type registration?

AMR is the mandatory format for voice message audio email attachments 
according to the MMS (Multimedia Messaging System) ETSI cellular 
telephone specification (ETSI 123 140), which incorporates the IETF MIME 
and VPIM specifications in large part.  

The MIME type registration for Audio/AMR is presently at:
  http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amr-13.txt

The AMR specification is:  3GPP TS 26.101:
  http://www.3gpp.org/ftp/tsg_sa/tsg_sa/TSGS_06/Docs/PDF/SP-99562.pdf

My question is:  What is the difference between Audio/AMR and GSM 6.10?
Are they the same?

Best wishes,
James
----------------------------------------------------------
This message was sent to you, since you are subscribed to
vpim <at> lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo

Glenn Parsons | 17 Apr 2002 19:12

RE: VPIM - Voice to Text Processing Requirements

The ability to add the email address already exists.  But the messages would all be VPIM messages

I presume you are looking for some voice-to-text functionality?

ASR requirements are not on the VPIM charter or are they planned.

There is work underway in W3C on VoiceXML and multimodal, and in the IETF SIP spinoffs (e.g., CATS), that deal with generic access to ASR systems.

Glenn.

    ----------
    From:   Jason Michael Canon
    Sent:   Wednesday, April 17, 2002 12:25 PM
    To:     jwn2 <at> qualcomm.com; Parsons, Glenn [CAR:6L81:EXCH]
    Subject:        VPIM - Voice to Text Processing Requirements

    Greetings,

    A firm I am working with has an in-place AVAYA voice messaging system
    that they would like to integrate with Internet mail such that they can
    add an SMTP mailing
    list as an addressee on outgoing voice messages.  I've not scanned the
    VPIM specs but wonder if your WG or any other is addressing this
    interoperability?

    Thanks



James Salsman | 17 Apr 2002 20:29

Re: Audio/AMR

I have almost convinced myself that Audio/AMR is not the same as GSM 6.10 
-- can anyone please confirm or deny this?

Here is an Audio/AMR reference implementation for x86 PCs:

http://www.3gpp.org/ftp/tsg_sa/WG4_CODEC/AMR-Wideband/AMR-WB_Characterization_Phase/Executables/g7221%26amrnb400_exe.zip

Does anyone have source to an AMR codec?  I can't find it.

> AMR is the mandatory format for voice message audio email attachments 
> according to the MMS (Multimedia Messaging System) ETSI cellular 
> telephone specification (ETSI 123 140), which incorporates the IETF MIME 
> and VPIM specifications in large part.  
> 
> The MIME type registration for Audio/AMR is presently at:
>   http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-amr-13.txt
> 
> The AMR specification is:  3GPP TS 26.101:
>   http://www.3gpp.org/ftp/tsg_sa/tsg_sa/TSGS_06/Docs/PDF/SP-99562.pdf

Best wishes,
James
----------------------------------------------------------
This message was sent to you, since you are subscribed to
vpim <at> lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo


Gmane