Notes from IETF Meeting SIP WG
* Karen ODonouhue taking notes
* Scott and his IPR notice
* my blabbering
Aparna Vemuri
-------------
SIP-T Context and Architectures
Purpose
feature transparency
Issues
* SIP MIME type negotiation - standard 415
* Want to be able to tell a UAS to ignore certain MIME types
- ISUP repitition problem
* not all ISUP parameters are needed; many will contain information
from origination side
Bill Marshall
-------------
Packetcable DCS work
changes in current version - all six now in compliance with rfc2026.
Manyfolks
---------
* handling of case where UAS wants preconditions, but UAC didn't
indicate support for it
Privacy
-------
* Needed to add proxy-require
* removed authentication ?? sip security task force will handle
* OSPS removed
* editorial changes
State
-----
* Usage of Supported/Require added
* interaction with Hide. If Via headers hidden, then state headers
need to be hidden -> resulting in Proxy-Require
* will change syntax to include port number
Call Authorization
------------------
* only minor editorial changes
Architectural Draft
-------------------
* much larger in size
Proxy-Proxy
-----------
* DCS Specific extensions
tracing of obsence and harassing calls
resource coordination for packetcable
call transfer and three way calling
OSPS
Billing-Info
Require and Proxy-Require used
Next steps
* design complete
* maybe issues for inter-domain operation
* 4 documents for proposed
Consensus was achieved on adding four proposed drafts as wg items.
Informational draft will be on hold until proposed documents are
complete.
Henning Schulzrinne
-------------------
update on rfc2543bis
nothing thats not backwards compatible
not SIP/2.1
lots of clarifications
* ACK Forwarding
* consistencies between tables and texts
* e-e vs. h-h distinction has been deprecated, different table
which describes what proxies are allowed to do
* headers tentatively added
* separate call and transaction state machines
* cancel/invite are separable
(will need to add note on need for timer in cancel, since you may
not get a 487)
* addition of spirals
* split spec in half - framework and methods draft
MIB Draft
---------
* partition of MIB -
SIP common
UA
Server (proxy and redirect)
Registrar
support modules
* added support for multiple instances in the same system
* throttling
* some security things in there
Wednesday meeting
-----------------
MWI
+++
Henning: should check out POP and compare with that
Christian: why are you assuming that this is just voicemail?
Rohan: we're not?
Christian: but you assume I have the same address for voice and email?
Ch: this is an application of presence, no? You should wait for presence
work to be complete
Scott: why not use snmp?
henning: don't be specific to voicemail
SIP-H.323 requirements
++++++++++++++++++++++
OSP Token
+++++++++
consensus was to include it as a header
question: can you include a reference to the token instead of the actual token?
question: maybe recommend tcp since the tokens are large
DTMF
++++
skip proposes that there are two problems - dtmf transport, readily
covered by RTP, and key input, which is a different problem.
Donovan proposes SUBSCRIBE/NOTIFY.
No conclusion.