Subject: [Sipping] DPNSS MIME I-D .02

From: "Ranjith Mukundan" <[email-masked]>
Date: Wed, 2 Jul 2003 19:00:32 +0530

folks,

We've submitted .02 of the DPNSS MIME draft (see below). We've also
requested for an agenda slot at Vienna to Present this draft and elicit
your views on progressing this as a WG I-D.

The changes from .01 to .02 are all basically to incorporate inputs that
we received on this list; which are:

1-- Changing the Reference to Oftel's ND1301:2001/03 from BTNR 188 
2-- Explicit Statment of DPNSS as private-NNI.
3-- Reference to the similarity of the semantics of DPNSS signalling
messages to SIP messages.
4-- Restricting the Buffering option to segmented DPNSS messages alone.
5-- Rationale for retention of Buffering as an option rather than as a
mandatory requirement.
6-- Correcting the example that illustrates the buffering options (221
octets instead of 225).
7-- Reference to Indication Field and Selection Field as part of the
buffering option explation.
8-- Reference to a Segmentation Timer for realizing the buffering
option.
9-- Additional clarifications in the section on Buffering.
10-- A new Section mandating the functioning of the SIP-DPNSS gateway as
a 'Transit DPNSS PBX'.
11-- A new Section explicitly stating carraige of one DPNSS call per SIP
dialogue.
12-- Explicity Reference to the Content-Disposition Header defined in
RFC3204 instead of defining a new one.
13-- Inclusion of version 7.00 in the Version parameter description.
14-- Updating the description of the Version parameter description
(e.g., reference to decimal instead of floating point etc; removal of
phrases like "contiguously incrementing").
15-- Rationale for inclusing of the version parameter.
16-- Updating the Reference Section to include Oftel's ND1301:2001/03.
17-- Updating the Acknowledgement section.

Cheers,
-- ranjith..

>-----Original Message-----
>From: [email-masked] 
>[mailto:[email-masked]] On Behalf Of 
>[email-masked]
>Sent: Wednesday, July 02, 2003 4:23 PM
>To: IETF-Announce:
>Subject: I-D ACTION:draft-mukundan-sipping-dpnss-02.txt
>
>
>A New Internet-Draft is available from the on-line 
>Internet-Drafts directories.
>
>
>	Title		: MIME media types for DPNSS Objects
>	Author(s)	: R. Mukundan et al.
>	Filename	: draft-mukundan-sipping-dpnss-02.txt
>	Pages		: 11
>	Date		: 2003-7-1
>	
>This document describes Multipart Internet Mail Extensions 
>(MIME) type for application/Digital Private Network Signaling 
>System (DPNSS) objects for use in Session Initiation Protocol 
>(SIP) applications, according to the rules defined in RFC 
>2048. These types can be used to identify Digital Private 
>Network Signaling System 1 (DPNSS 1) objects within a SIP 
>message such as INVITE or INFO, as might be implemented when 
>using SIP in an environment where part of the call involves 
>interworking to DPNSS 1 based Private Networks. RFC 3204 
>addresses a similar need for Integrated Service Digital 
>Network User Part (ISUP) and Q Signaling (QSIG).
>
>A URL for this Internet-Draft is: 
>http://www.ietf.org/internet-drafts/draft->mukundan-sipping-dpnss-02.tx
t
>
>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-mukundan-sipping-dpnss-02.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-mukundan-sipping-dpnss-02.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