[SIPForum-techwg] IP PBX / SIP Interoperability draft version 4

Fri Jan 27 14:35:28 EST 2006

Also, I forgot to mention that I will be on vacation next week (Jan 30 -
Feb 3) without access to email. Of course, please don't hold up the
discussions on my account - I'll just catch up with the group upon my
return.

Thanks!

--Chris

  _____  

From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org]
On Behalf Of Chris Sibley
Sent: Friday, January 27, 2006 2:11 PM
To: SIP Forum Tech WG
Subject: [SIPForum-techwg] IP PBX / SIP Interoperability draft version 4

IP PBX / SP Interop WG team members,

Draft version four of the IP PBX / SP Interoperability specification is
now available online for your review at the following URL:

http://data.memberclicks.com/bbattach/123566/sf-draft-twg-IP_PBX_SP_Inte
rop-sibley-v4.pdf

(Jay, FYI I tried to upload the file to the SIP Forum Wiki but it
appears to no longer allow uploads of .pdf files..)

This release contains a significant number of changes (see below) so
please give it another "top-to-bottom" review when you get the chance.

Also, I wanted to take this opportunity to thank all of you for your
hard work and dedication to this activity. I think we're getting close!
Also, I took the liberty of adding the list's active contributors to the
'Contributors and Contact Information' section of the document. I did
this because I feel that these folks deserve some recognition for all of
the work they've put into this document. Of course, please let me know
if you would like your name removed (don't worry, it won't hurt my
feelings <g>) or your contact information modified. 

Looking forward to your comments!

--Chris

------------------------------------------------------------------------
-------------

Draft version 4 changes include:

* Note: Some reordering of the document content was performed in this
release. The section numbers below refer to the ORIGINAL section numbers
from the version 3 draft. 

- Removed all references and standards support requirements for RFC 2560
(OCSP).

- Removed all references and standards support requirements for RFC 2617
(HTTP Authentication: Basic and Digest Access Authentication).

- Removed section 12 (Call Forwarding and Transfer considerations).

- Removed paragraph recommending screening based on Enterprise identity
contained in the 'From: or 'P-Asserted-Identity:' fields.

- Removed mapping table from section 15.2 (ISUP / Q.931 Cause Code
Mapping).

- Removed subsection headings 16.1 (Normative References) and 16.2
(Informative References). All references are now under the main section
16 (i.e. no distinction is made between normative and informative.)

- Added standard SIP Forum copyright, disclaimer, and IPR notices.

- Added names / contact information for active contributors to the
section 17 (Contributors and Contact Information).

- Added support requirements for use of tel: URLs in the To: field from
Enterprise -> SP.

- Added support requirements for ITU-T Recommendation E.164.

- Added support requirements for the SIP UPDATE method (M-SAS, R-PBX).

- Added support requirements for use of RFC 3398 to section 15.2 (ISUP /
Q.931 Cause Code Mapping).

- Added URI examples for SP formatting of 'To:' field.

- Added paragraph to section 4 (Key Assumptions and Limitations of
Scope) to indicate that this specification is not a profile of SIP.

- Added support requirements for reception of SDP containing 'c=IN IPV4
0.0.0.0' to section 14.1 (Media Capability Negotiation).

- Added frequency/duration requirements for Special Information Tones to
section 15.1 (Call Progress Tones and Early Media).

- Added requirement to convert between u-Law to A-Law in section 14.2
(CODEC Support and Media Transport).

- Added requirement for G.711 A-Law to section 14.2 (Codec Support and
Media Transport). 

- Changed all references of 'P-Preferred-Identity' to
'P-Asserted-Identity'.

- Changed all references of "RFC 3824 E.164 format" to "ITU-T E.164
format".

- Changed all references of "ITU" to "ITU-T".

- Changed all references of "HIGHLY RECOMMENDED" to "RECOMMENDED".

- Changed standards table to use dashes instead of blanks.

- Changed recommended DSCP values in section 13 (Quality of Service
Considerations). Also clarified that these are only RECOMMENDED values.

- Changed recommended method of passing PSTN identity from Enterprise
--> SP to utilize the 'P-Asserted-Identity:' method (vs. 'From:' field
only).

- Changed section 15.1 (Call Progress Tones and Early Media) to reflect
use of Special Information Tones where applicable.

- Corrected examples in section 11.4 ('To' Field -- Emergency Services
Destinations). Incorrect placement of ';user=phone' parameter.

- Corrected examples in section 11.1.1 (Option 1: Utilizing the 'From'
SIP Header Field Exclusively). Improper use of ';user=phone' parameter
on second option.

- Corrected examples in section 11.1.2 (Option 2: Utilizing the 'From'
and 'P-Preferred-Identity' SIP Header Fields). Improper use of
';user=phone' parameter on second option.

- Multiple updates to the text in section 3 (Definitions).

- Multiple updates to the text in section 7 (Signaling Security).

- Multiple updates to the text in section 9.1 (Authentication of the PBX
by the Service Provider).

- Multiple updates to the text in section 9.2 (Authentication of the
Service Provider by the PBX).

- Minor wording updates to the text in section 4 (Key Assumptions and
Limitations of Scope).

- Minor wording updates to the text in section 14.1 (Media Capability
Negotiation).

- Minor wording updates to the text in section 14.5 (Fax and Modem
Calls).

- Minor wording updates to the text in section 14.2 (Codec Support and
Media Transport).

- Reordered list of RFCs/ITU-T standards in section 5 (Standards
Support) and section 16 (References). Ordering is now by RFC number.

- Broke out section 11 (URI Formatting and Addressing Rules) into
separate Enterprise and Service Provider sections.

  _____  

This email may contain confidential information. If you are not the
intended recipient, please advise by return email and delete immediately
without reading or forwarding to others. - Cbeyond 

  _____  

**********************************************************************
This email may contain confidential information. If you are not
the intended recipient, please advise by return email and delete
immediately without reading or forwarding to others.
 - Cbeyond 
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20060127/ec695ff9/attachment.html 