100 likes | 190 Views
SIP WG Monday Session,. 1300 Agenda Bash 1305 WG Status, Organization, Charters, Milestones -- Dean Willis 1345 2543bis Issues -- Jonathan Rosenberg 1430 SIP Events -- Adam Roach 1500 Break for a Cookie. SIPWG Tuesday Session. 0900 Agenda Bash – Pick a Note Taker
E N D
SIP WG Monday Session, • 1300 Agenda Bash • 1305 WG Status, Organization, Charters, Milestones -- Dean Willis • 1345 2543bis Issues -- Jonathan Rosenberg1430 SIP Events -- Adam Roach • 1500 Break for a Cookie
SIPWG Tuesday Session • 0900 Agenda Bash – Pick a Note Taker • 0905 REFER Issues and Call Control -- Robert Sparks • 0930 ISUP Mapping and Overlap Dialing Issues -- Gonzalo Camarillo • 0950 H.323 Interworking Requirements Issues – H.323 authors. • 1000 Privacy Issues -- Flemming Andreasen • 1030 3GPP Requirements – Keith Drage • 1100 Open Issues from List -- Jonathan Rosenberg • 1130 Break for Lunch
SIP WG Friday Session • 0900 Agenda Bash • 0905 Making SIP Nat Friendly -- Jonathan Rosenberg • 0930 MLPP Issues -- James Polk • 0940 3PCC -- Frans Haerens • 0950 3PCC -- Jonathan Rosenberg • 1030 Open Issues -- Jonathan Rosenberg • 1130 Brake for Airplanes
SIP WG Charter Items • 1. bis: A draft standard version of SIP.2. callcontrol: Completion of the SIP call control specifications, which enables multiparty services, such as transfer and bridged sessions.3. callerpref: Completion of the SIP caller preferences extensions, which enables intelligent call routing services.4. mib: Define a MIB for SIP nodes .5. precon: Completion of the SIP extensions needed to assure satisfaction of external preconditions such as QoS establishment.
SIP WG Charter Cont • 6. state: Completion of the SIP extensions needed to manage state within signaling, aka SIP "cookies".7. telpriv: Completion of SIP extensions for security and privacy.8. security: Assuring generally adequate security and privacy mechanisms within SIP.9. provrel: Completion of the SIP extensions needed for reliability of provisional messages.10. servfeat: Completion of the SIP extensions needed for negotiation of server features.
SIP WG Charter Cont • 11. sesstimer: Completion of the SIP Session Timer extension.12. events: Completion of the SIP Events extensions (Subscribe/Notify).13. security: Requirements for Privacy and Security.
SIPPING Charter Items • 1. sipt: Requirements and Practices for interaction with telephony systems (SIP-T, Telephony Call Flows).2. hearing: Requirements and Practices for providing support for hearing impaired users.3. aaa: Requirements and Practices for interaction with AAA systems.4. H.323: Requirements and Practices for interaction with H.323 systems.5. 3g: Requirements and Practices for interaction with third-generation wireless systems.
SIPPING, Cont. • 6. firewall: Requirements and Practices for interaction with firewall systems.7. regspec: Requirements, Practices and Registration Specifications for interworking with other descriptive specifications, such as MIME, DNS, DHCP, ENUM, etc..8. general: Discussion and Guidelines on the general usage of SIP.9. multiparty: Requirements and Practices for multiparty conferencing.
SIPPING, Cont. • 10. fax: Requirements, Practices, and Registrations Specifications for using SIP with FAX. 11. mwi: Requirements and Practices for Message Waiting Indicator.12. media: Requirements and Practices for usage of SIP in media servers, messagingservers, conferencing servers, and similar applications.13. regpay: Practices for Registration Payload. 14. callcontrol: Requirements for Call Control.
Open Charter Questions • What to do with IN Interworking? • Firewall Passage • Control is clearly MIDCOM • What else?