R. Mahay, Cisco, Message Waiting Indication,
draft-mahy-sip-message-waiting-00.txt
C. Look at POP Queries
Q. Why do we need this? More interested in email than vmail.
A. VMail might not be in a unified messaging system
Q. Why mix mail SP with telephony SP
A. Proposal allows subscription for this service from any mail SP, not
limited to the SIP server. MW server may aggregate multiple messaging
servers.
Q. Is this out of scope and/or part of the presence issues
A. Take to list
Q. Need more flexibility in what variables are presented. Some data object,
like a MIB is needed. Can we find one?
A. Agree, need to contact VPIM
C. Look at Megaco work done on MWI
C. Keep issues of what info is available vs. how it is presented
C. Nee explicit text in draft dealing with more than vmail. Maybe even
MWI for combined mail services
C. Issues of Presence for People vs. Presence for Services.
Palawat, SIP-H.323 Interworking Requirements,
draft-agrawal-sip-h323-interworking-reqs-00.txt
Q. What about tunneling things like Q.SIG
A. Not trying to do like SIP-T with tunneling. End system to end system
only
C. Don't go near operational issues like who owns things, QoS, etc. Just
drop them.
Johnston, Worldcom, Call Flows, draft-ietf-sip-call-flows-01.txt
C. Include a multiple proxy, multiple UA proxy torture test
Q. Is this something for interoperability testing?
A. Sure, it could be of use
Thomas, OSP Authorization Token, draft-johnston-sip-osp-token-00.txt &
draft-Thomas-sip-mime-osp-token-00.txt
C. If mucked about with by a proxy, it has to be a header
C. Most likely to be backwards compatible with a header rather than
multipart mime
Q. Could it be an indirect reference with a digest or something
A. Token has a short lifetime
C. Might be okay, take to list
Cabe, Intervoice, DTMF For Apps
Ed bottom line - need universal key input mechanism. RTP is not reliable,
SIP signalling
goes to wrong place (not end user to app). Need new session (& maybe new
protocol) to
transport DTMF reliably from UA to app.
Culpepper, InterVoice, Using INFO for DTMF,
draft-culpepper-sip-info-event-00.txt
C. DTMF for RTP was DESIGNED for user apps, not transport across packet nets
C. DTMF for RTP CAN be sent in a different session (to a different address)
with as good reliability as PSTN
C. SDP may need a way to specify purpose for signalling for endpoints to
know
C. Commend presentation for DTMF for user input
C. Use subscribe/notify to keypad input
C. DTMF is a way to pass comments in an audio channel, voice recognition may
replace
the DTMF and should be treated the same way. Does not belong to signalling,
it belongs
to the audio path
C. Mistake to reinvent telnet by RTP or INFO
C. Limited capability user interaction is useful
C. Don't want to support multiple methods. Need DTMF in RTP for other
reasons,
want to then use it everywhere.
Q. Who gets the digits changes as the call progresses. Reinvites for the
digits
is not a good thing.
A. May have multiple listeners
C. First app might forward
C. Terminating device must get RTP. 3rd party might need it. For 3rd party
use SUBSCRIBE/NOTIFY.
Shultzrine, Columbia, 911 Services, draft-schulzrinne-sip-911-00.txt
C. Report has technical error in SLP. SLP is possible
Q. Would the PSAP have to be IP connected
A. Variations possible, need a gateway for existing PSAPs that don't have
this new
capability
Q. DNS would not be able to supply a translator caller info
A. It would send a spatial loc, which would use the mobile phone mechanisms.
C. Need to deal with data capable devices. Also need to deal with POTS
plugged
into a SIP gateway
C. This issues are beyond SIP - could even be a web "call"
C. Have to deal with lots of SPs in the path
Moyer, Telcordia, SIP for Network Appliances,
draft-moyer-sip-appliances-framework-00.txt
No comments accepted
Calhoun, Sun, AAA Rqmts, draft-calhoun-sip-aaa-reqs-00.txt
C. Must take into account discussions in the AAA group
C. Problem space must include use of services other than Internet Access
logon
C. Get discussion on sip rqmts onto the list
Camarillo, Ericsson, 3rd Party Call Control with SDP preconditions,
draft-camarillo-3pcc-qos-00.txt
No comments, two open issues will be taken to the list
Iizuka, Fujitsu, CC/PP exchange, draft-nishigaya-sip-ccpp-00.txt
C. Not sure SIP is the right answer, using only use the Register and
Subscribe/Notify
C. Pay attention to the SIP Extension's Guidelines, this appears to not be
appropriate
Sijben, Lucent, TIPHON work on SIP, draft-tiphon-background-00.txt, and
draft-tiphon-architecture-00.txt
No comments
Peterson, Level(3), SIP Firewall Policy mechanisms,
draft-jfp-sipfw-policy-00.txt
No Comments
Sparks, dynamicSoft, Call Control Transfer, draft-sip-cc-transfer-00.txt
C. Refer is not just for INVITES