Session Initiation Protocol Discussion Archive - Date Index

• Dec 06 2001
• RE: [Sip] Open Issue #164: Proxy-Authentication-Info, James Undery
• RE: [Sip] Major Open Issue #113: Overlapping Transactions, Mark Watson
• RE: [Sip] Open Issue #203: transport related params in To/From, Jo Hornsby
• RE: [Sip] MAJOR Open Issue #184: Message size limitations, Jo Hornsby
• RE: [Sip] Open Issue #144: Branch ID + isCancel() as transaction ID, Jo Hornsby
• RE: [Sip] Open Issue #88: Addressing OPTIONS to a proxy/redirect server, Jo Hornsby
• [Sip] Report to Recipient(s), NAMASMTP01
• Re: [Sip] Open Issue #164: Proxy-Authentication-Info, Jari Arkko
• RE: [Sip] Open Issue #164: Proxy-Authentication-Info, Peterson, Jon
• [Sip] Open Issue #203: transport related params in To/From, Jonathan Rosenberg
• No Subject, No Author
• RE: [Sip] Open Issue #140: use only tags for Call-leg ID, Jonathan Rosenberg
• [Sip] Open Issue #197: URLs in OPTIONS, Jonathan Rosenberg
• [Sip] whats up 224321068, Nobody
• [Sip] Open Issue #188: Reply-To, Jonathan Rosenberg
• [Sip] MAJOR Open Issue #184: Message size limitations, Jonathan Rosenberg
• No Subject, No Author
• [Sip] Open Issue #181: Forking OPTIONS, Jonathan Rosenberg
• [Sip] Open Issue #179: Multicast to unicast REGISTER, Jonathan Rosenberg
• [Sip] Open Issue #178: Deprecate absolute times absolutely: SPEAK UP IFYOU USE THEM IN YOUR PRODUCT!!!!!!!!!!, Jonathan Rosenberg
• Re: [Sip] Open Issue #128: 503 and SRV, Dean Willis
• [Sip] Open Issue #150: too many ways of saying "don't send me media", Jonathan Rosenberg
• [Sip] Open Issue #164: Proxy-Authentication-Info, Jonathan Rosenberg
• [Sip] Open Issue #145: SRV Processing in stateless proxies part I, Jonathan Rosenberg
• Re: [Sip] Open Issue #140: use only tags for Call-leg ID, Arunachalam Venkatraman
• Re: [Sip] Open Issue #128: 503 and SRV, Henning Schulzrinne
• No Subject, No Author
• No Subject, No Author
• [Sip] Open Issue #144: Branch ID + isCancel() as transaction ID, Jonathan Rosenberg
• [Sip] Open Issue #140: use only tags for Call-leg ID, Jonathan Rosenberg
• [Sip] Open Issue #139: re-INVITE Glare, Jonathan Rosenberg
• [Sip] Open Issue #131: Meaning of challenge when UAC is a gateway, Jonathan Rosenberg
• [Sip] InterScan NT Alert, isv01
• [Sip] Open Issue #128: 503 and SRV, Jonathan Rosenberg
• [Sip] question about Dialog ID, 陈善学
• [Sip] Virus Notification: A virus has been detected in a message in which you where a recipient, Nemx Power Tools for MS Exchange Server_SS8MAIL1_0
• [Sip] ScanMail Message: To Recipient virus found and action taken., System Attendant
• [Sip] Open Issue #126: ACK never received for 2xx to re-INVITE, Jonathan Rosenberg
• [Sip] Major Open Issue #113: Overlapping Transactions, Jonathan Rosenberg
• [Sip] Virus Notification: A virus has been detected in a message in which you where a recipient, Nemx Power Tools for MS Exchange Server_SS8MAIL1_0
• [Sip] Virus Alert, Postmaster
• [Sip] Antigen found =*.scr file, ANTIGEN_CONITAMAIL
• [Sip] Antigen found Win32/PSW.Hooker 2.4.Trojan (CA(InoculateIT)) virus, Antigen
• [Sip] ScanMail Message: To Recipient virus found and action taken., System Attendant
• [Sip] ScanMail Message: To Recipient virus found and action taken., System Attendant
• [Sip] Re:, chhz
• [Sip] Open Issue #109: Allow in non-INVITE, Jonathan Rosenberg
• RE: [Sip] (no subject), Chiou, Mark
• [Sip] Room assigment for SIP Security ad-hoc -- Murano, Dean Willis
• Dec 05 2001
• [Sip] [SIP}: Comments on draft-ietf-sip-overlap-01, Chiou, Mark
• Re: [Sip] bis-05: transport mechanisms, Dean Willis
• [Sip] bis-05: transport mechanisms, Michael Thomas
• [Sip] bis-05: transport mechanisms, Drage, Keith (Keith)
• [Sip] (no subject), Mpierce1
• [Sip] Open Issue #88: Addressing OPTIONS to a proxy/redirect server, Jonathan Rosenberg
• [Sip] Open Issue #81: caching of proxy credentials, Jonathan Rosenberg
• [Sip] Some comments on rfc2543bis-05 - RESEND, Terry L Anderson
• [Sip] Open Issue #146: reuse of disabled media streams, Jonathan Rosenberg
• [Sip] More on meeting formats for SIP and SIPPING at IETF 52., Dean Willis
• [Sip] resolving open issues in bis!, Jonathan Rosenberg
• [Sip] Reading list error in published agenda -- draft-sen-sip-earlymedia, Dean Willis
• RE: [Sip] Negotiating audio mixing capabilities, Jonathan Rosenberg
• [Sip] RE: [Sipping] Immediate NOTIFIES change in sip-events-01, Jonathan Rosenberg
• [Sip] RE: Comment on draft-ietf-sip-rfc2543bis-05, Jonathan Rosenberg
• RE: [Sip] Session Timer - Timeout on Refresh, Jonathan Rosenberg
• RE: [Sip] Clarification on methods-param in caller preferences, Jonathan Rosenberg
• [Sip] RE: [Simple] New I-D on IM transport, Jonathan Rosenberg
• RE: [Sip] The Future of SIP Call Control, Jonathan Rosenberg
• RE: [Sip] re: the future of call control, Jonathan Rosenberg
• RE: [Sip] Problem with bis05 state machine, Jonathan Rosenberg
• RE: [Sip] Missing Call-ID header, Jonathan Rosenberg
• RE: [Sip] bis: A draft standard version of SIP., Jonathan Rosenberg
• [Sip] changing of media types allowed in offer/answer and SIP open issue #24, Jonathan Rosenberg
• [Sip] Multi-Media SIP Scenario, Purcell Michael-QA3001
• [Sip] bis: A draft standard version of SIP., Purcell Michael-QA3001
• No Subject, No Author
• RE: [Sip] Problem with bis05 state machine, Brian Quinlan
• [Sip] Agenda, SIP WG, IETF 52, Dean Willis
• Re: [Sip] Problem with bis05 state machine, pkamath
• Dec 04 2001
• Re: [Sip] Missing Call-ID header, Mohamed Elsewe
• Re: [Sip] Missing Call-ID header, Mohamed Elsewe
• [Sip] [정보제공 ] ★ 무료로 팔아 드립니다.., 한일우
• [Sip] Re: Proposed Change to Security adhoc timing, Jari Arkko
• [Sip] RE: Proposed Change to Security adhoc timing, Mary Barnes
• [Sip] Revised SIP WG draft agenda posted for IETF52, Dean Willis
• [Sip] Proposed Change to Security adhoc timing, Dean Willis
• Re: [Sip] Draft Agenda SIP WG at IETF 52, Dean Willis
• RE: [Sip] Draft Agenda SIP WG at IETF 52, Mary Barnes
• RE: [Sip] re: refer-to header, Hisham Khartabil
• [Sip] Problem with bis05 state machine, Chris Mills
• RE: [Sip] re: the future of call control, Robert Sparks
• [Sip] Draft Agenda SIP WG at IETF 52, Dean Willis
• Re: [Sip] re: refer-to header, Dean Willis
• Dec 03 2001
• [Sip] comment on SIP draft " draft-agrawal-sip-H.323-Interworking-01.txt ", Chiou, Mark
• RE: [Sip] re: the future of call control, Roy, Radhika R, ALCTA
• Re: [Sip] re: the future of call control, Mpierce1
• [Sip] I-D ACTION:draft-ietf-sip-nat-01.txt, Internet-Drafts
• [Sip] I-D ACTION:draft-ietf-sip-message-00.txt, Internet-Drafts
• Re: [Sip] question about 180 Ringing, pkamath
• [Sip] question about stateful proxy and TCP, 陈善学
• [Sip] question about 180 Ringing, 陈善学
• [Sip] Missing Call-ID header, Gabriel Velo
• Dec 02 2001
• RE: [Sip] re: refer-to header, Robert Sparks
• Re: [Sip] re: refer-to header, Dean Willis
• RE: [Sip] re: refer-to header, Robert Sparks
• [Sip] re: refer-to header, Rohan Mahy
• [Sip] re: the future of call control, Rohan Mahy
• Nov 30 2001
• RE: [Sip] AT&T IPR Notices on SIP drafts, Jonathan Rosenberg
• RE: [Sip] AT&T IPR Notices on SIP drafts, Jonathan Rosenberg
• Nov 29 2001
• [Sip] Some comments on rfc2543bis-05, Terry L Anderson
• Re: [Sip] AT&T IPR Notices on SIP drafts, William Marshall
• [Sip] Re: [Sipping] AT&T IPR Notices on SIP drafts, Chip Sharp
• Re: [Sip] if receive two invite at the same time., Gonzalo Camarillo
• [Sip] Re: [Simple] New I-D on IM transport, Paul Kyzivat
• [Sip] AT&T IPR Notices on SIP drafts, Dean Willis
• No Subject, No Author
• RE: [Sip] Refer-To header and method-param, Sriram Parameswar
• Re: [Sip] The Future of SIP Call Control, Dean Willis
• [Sip] A comment on "sip-service-examples-03.txt", Victor Paulsamy
• Re: [Sip] The Future of SIP Call Control, Dean Willis
• RE: [Sip] Refer-To header and method-param, Robert Sparks
• [Sip] Clarification on methods-param in caller preferences, Hisham Khartabil
• [Sip] New I-D on Gateway Registration Using SIP, Shan Lu
• [Sip] I-D ACTION:draft-ietf-sip-callerprefs-05.txt, Internet-Drafts
• [Sip] I-D ACTION:draft-ietf-sip-dhcp-05.txt, Internet-Drafts
• [Sip] Refer-To header and method-param, Hisham Khartabil
• Nov 28 2001
• Re: [Sip] Service Examples - Single Line Extensions, Alan Johnston
• Re: [Sip] The Future of SIP Call Control, William Marshall
• RE: [Sip] Session Timer - Timeout on Refresh, Brett Tate
• RE: [Sip] The Future of SIP Call Control, Roy, Radhika R, ALCTA
• Re: [Sip] The Future of SIP Call Control, Mpierce1
• [Sip] Service Examples - Single Line Extensions, Mpierce1
• Re: [Sip] SIP security requirements (this might mean you!), Mpierce1
• RE: [Sip] multicast conference service of SIP, Roy, Radhika R, ALCTA
• RE: [Sip] multicast conference service of SIP, Roy, Radhika R, ALCTA
• RE: [Sip] multicast conference service of SIP, Agboh, Charles
• RE: [Sip] one open issue in Models for Multi Party Conferencing in SIP, Lei Liang
• RE: [Sip] multicast conference service of SIP, Lei Liang
• RE: [Sip] one open issue in Models for Multi Party Conferencing in SIP, Roy, Radhika R, ALCTA
• RE: [Sip] multicast conference service of SIP, Roy, Radhika R, ALCTA
• [Sip] one open issue in Models for Multi Party Conferencing in SIP, Lei Liang
• [Sip] Re: Comment on draft-ietf-sip-rfc2543bis-05, Paul Kyzivat
• [Sip] SUBSCRIBE & NOTIFY mechanism, Lei Liang
• [Sip] [±ä±Þ°øÁö] µåµð¾î ¿ÀǵǾú½À´Ï´Ù., admin
• [Sip] I-D ACTION:draft-ietf-sip-service-examples-03.txt, Internet-Drafts
• [Sip] I-D ACTION:draft-ietf-sip-sctp-01.txt, Internet-Drafts
• RE: [Sip] multicast conference service of SIP, Lei Liang
• [Sip] RE: Request merging, Jonathan Rosenberg
• RE: [Sip] Record routing primary and secondary locations, Jonathan Rosenberg
• RE: [Sip] Session Timer - Timeout on Refresh, Jonathan Rosenberg
• [Sip] RE: Comment on draft-ietf-sip-rfc2543bis-05, Jonathan Rosenberg
• RE: [Sip] Possible interop issues due to BNF of digest auth, Jonathan Rosenberg
• [Sip] RE: [Simple] New I-D on IM transport, Jonathan Rosenberg
• RE: [Sip] The Future of SIP Call Control, Jonathan Rosenberg
• [Sip] RE: Session Timer Questions., Jonathan Rosenberg
• [Sip] Session Timer Questions., Padhye, Chinmay
• Nov 27 2001
• RE: [Sip] The Future of SIP Call Control, Roy, Radhika R, ALCTA
• Re: [Sip] The Future of SIP Call Control, Mpierce1
• [Sip] SIP security requirements (this might mean you!), Michael Thomas
• RE: [Sip] Bis-05: Diaglog establishment ambiguity, Jonathan Rosenberg
• RE: [Sip] multicast conference service of SIP, Jonathan Rosenberg
• RE: [Sip] multicast conference service of SIP, Mark Zezren
• RE: [Sip] Nit: grammar for display-name, Jonathan Rosenberg
• RE: [Sip] Proposed change to callerprefs, Jonathan Rosenberg
• RE: [Sip] The Future of SIP Call Control, Roy, Radhika R, ALCTA
• RE: [Sip] REFER issues, Jonathan Rosenberg
• RE: [Sip] To-Tag, Jonathan Rosenberg
• RE: [Sip] multicast conference service of SIP, Jonathan Rosenberg
• RE: [Sip] The Future of SIP Call Control, Jonathan Rosenberg
• RE: [Sip] The Future of SIP Call Control, Roy, Radhika R, ALCTA
• [Sip] multicast conference service of SIP, Lei Liang
• Re: [Sip] The Future of SIP Call Control, Mpierce1
• RE: [Sip] Reg draft-ietf-avt-rtp-mime-05.txt, Sharma Kanchinadham
• RE: [Sip] To-Tag, Robert Sparks
• Re: [Sip] Reg draft-ietf-avt-rtp-mime-05.txt, Colin Perkins
• [Sip] To-Tag, Buettner Werner
• [Sip] Reg draft-ietf-avt-rtp-mime-05.txt, Sharma Kanchinadham
• [Sip] I-D ACTION:draft-ietf-sip-call-auth-03.txt, Internet-Drafts
• [Sip] I-D ACTION:draft-ietf-sip-manyfolks-resource-03.txt, Internet-Drafts
• Nov 26 2001
• [Sip] new I-D: Redirection Service capability in SIP, Sanjoy Sen
• RE: [Sip] REFER issues, Robert Sparks
• Re: [Sip] REFER issues, Bob Penfield
• Re: [Sip] REFER issues, Christer Holmberg
• RE: [Sip] REFER issues, Robert Sparks
• Re: [Sip] REFER issues, Christer Holmberg
• RE: [Sip] The Future of SIP Call Control, Robert Sparks
• RE: [Sip] REFER issues, Robert Sparks
• [Sip] The Future of SIP Call Control, Rohan Mahy
• Re: [Sip] Proposed change to callerprefs, Paul Kyzivat
• [Sip] Re: [Simple] New I-D on IM transport, Paul Kyzivat
• [Sip] REFER issues, Christer Holmberg
• Re: [Sip] SCTP address in draft-ietf-sip-sctp-00, Gonzalo Camarillo
• [Sip] New version of "Early Media Issues and Scenarios" draft - (draft-sen-sip-earlymedia), Chris Hogg
• Re: [Sip] REFER security, Daniel G. Petrie
• RE: [Sip] Translate header in draft-ietf-sip-nat-00.txt, Jonathan Rosenberg
• Re: [Sip] if receive two invite at the same time., Gonzalo Camarillo
• RE: [Sip] if receive two invite at the same time., John . Hearty
• [Sip] SCTP address in draft-ietf-sip-sctp-00, Cullen Jennings
• [Sip] Review of draft-ietf-sip-refer-02, Bob Penfield
• [Sip] [±¤°í]°¡Àå Àú·ÅÇÑ Ç×°ø±ÇÀº Ç×°ø±Ç°æ¸Å¸¦ ÀÌ¿ëÇϼ¼¿ä., ÁÖ
• Re: [Sip] if receive two invite at the same time., Lei Liang
• [Sip] Info : L'Annuaire Francais par Departement facilite vos recherches, annuaire
• RE: [Sip] if receive two invite at the same time., Robert Sparks
• RE: [Sip] if receive two invite at the same time., Inmaculada . Espigares
• Re: [Sip] if receive two invite at the same time., Lei Liang
• [Sip] I-D ACTION:draft-ietf-sip-guidelines-03.txt, Internet-Drafts
• Nov 25 2001
• Re: [Sip] REFER security, Michael Thomas
• Re: [Sip] REFER security, Henning G. Schulzrinne
• Re: [Sip] REFER security, Henning G. Schulzrinne
• Nov 24 2001
• Re: [Sip] New version of SIP DHCP draft, Henning G. Schulzrinne
• Re: [Sip] New version of SIP DHCP draft, Henning Schulzrinne
• Nov 23 2001
• RE: [Sip] New version of SIP DHCP draft, Drage, Keith (Keith)
• [Sip] Nit: grammar for display-name, Anders Kristensen
• Re: [Sip] New version of SIP DHCP draft, Henning Schulzrinne
• Re: [Sip] New version of SIP DHCP draft, Miguel A. Garcia
• Nov 22 2001
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Bob Penfield
• RE: [Sip] Bis-05: Diaglog establishment ambiguity, Tan Ya-Ching ICM N PG U ID A 1
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Gonzalo Camarillo
• RE: [Sip] Bis-05: Diaglog establishment ambiguity, Mark Watson
• RE: [Sip] Bis-05: Diaglog establishment ambiguity, Tan Ya-Ching ICM N PG U ID A 1
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Christer Holmberg
• RE: [Sip] Bis-05: Diaglog establishment ambiguity, Tan Ya-Ching ICM N PG U ID A 1
• Nov 21 2001
• Re: [Sip] if receive two invite at the same time., Gonzalo Camarillo
• Re: [Sip] bis-05: Terminating a session, Gonzalo Camarillo
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Gonzalo Camarillo
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Gonzalo Camarillo
• [Sip] Thought experiement - capturing all responses to a fork, Robert Sparks
• Re: [Sip] Resource-Priority Header, Mpierce1
• Re: [Sip] Proposed change to callerprefs, Paul Kyzivat
• [Sip] results of WGLC for draft-ietf-sip-callerprefs-04.txt, Jonathan Rosenberg
• [Sip] Note to all new I-D authors - BNF conventions HAVE CHANGED, Rosen, Brian
• [Sip] I-D ACTION:draft-mahy-sip-cc-models-01.txt, Internet-Drafts
• [Sip] New version of SIP DHCP draft, Henning G. Schulzrinne
• [Sip] if receive two invite at the same time., Lei Liang
• Re: [Sip] Resource-Priority Header, Henning G. Schulzrinne
• Re: [Sip] Resource-Priority Header - comparison, James M. Polk
• RE: [Sip] Resource-Priority Header, Rosen, Brian
• Re: [Sip] Resource-Priority Header, Mpierce1
• Re: [Sip] Resource-Priority Header, Mpierce1
• Re: [Sip] Resource-Priority Header, Mpierce1
• RE: [Sip] Proposed change to callerprefs, Jonathan Rosenberg
• [Sip] Libros GRATIS, LibrosDigitales
• [Sip] I-D ACTION:draft-mahy-sip-cc-models-01.txt, Internet-Drafts
• RE: [Sip] bis-05: Terminating a session, Tan Ya-Ching ICM N PG U ID A 1
• [Sip] RE: [Sip-implementors] Need clarification on callerprefs, Jonathan Rosenberg
• Re: [Sip] 482 handling by proxies, Christer Holmberg
• RE: [Sip] 482 handling by proxies, Jonathan Rosenberg
• [Sip] RE: [Simple] New I-D on IM transport, Jonathan Rosenberg
• Re: [Sip] 482 handling by proxies, Christer Holmberg
• Nov 20 2001
• [Sip] REFER security, Michael Thomas
• [Sip] SIP WG - 6 - Last Call Open Discussion CLOSED - draft-ietf-sip-call-auth-02.txt, Rakesh Shah
• RE: [Sip] Use of Expires in Refer., Robert Sparks
• Re: [Sip] bis-05: Terminating a session, Bob Penfield
• [Sip] Use of Expires in Refer., Padhye, Chinmay
• RE: [Sip] bis-05: use of 100 Trying, Tom-PT Taylor
• RE: [Sip] REFER security, Robert Sparks
• RE: [Sip] under-the-wire comments for caller-prefs, Jonathan Rosenberg
• RE: [Sip] SIP Caller Preferences - Does registration contain 'Priority' inf ormation?, Jonathan Rosenberg
• Re: [Sip] Resource-Priority Header, James M. Polk
• RE: [Sip] REFER security, krisztian . kiss
• RE: [Sip] bis-05: Terminating a session, Jonathan Rosenberg
• RE: [Sip] bis-05 compact form vs. short form, Jonathan Rosenberg
• RE: [Sip] 482 handling by proxies, Jonathan Rosenberg
• RE: [Sip] 482 handling by proxies, A Venkatraman
• RE: [Sip] bis-05: use of 100 Trying, John . Hearty
• RE: [Sip] bis-05 compact form vs. short form, William Marshall
• Re: [Sip] REFER security, William Marshall
• RE: [Sip] 482 handling by proxies, Jonathan Rosenberg
• Re: [Sip] bis-05 mostly NITS - full review, Christer Holmberg
• RE: [Sip] Removal proposal: Password in SIP-URL, Jonathan Rosenberg
• RE: [Sip] More clarification of bis-05 changes requested, Jonathan Rosenberg
• RE: [Sip] bis-05 mostly NITS - full review, Jonathan Rosenberg
• RE: [Sip] bis-05 compact form vs. short form, Jonathan Rosenberg
• Re: [Sip] bis-05: use of 100 Trying, Christer Holmberg
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• [Sip] Resource-Priority Header, Mpierce1
• [Sip] Last Call summary for draft-ietf-sip-call-auth-02, William Marshall
• Nov 19 2001
• RE: [Sip] REFER security, Robert Sparks
• [Sip] SIP-cookies, Mpierce1
• Re: [Sip] bis-05: use of 100 Trying, Gonzalo Camarillo
• [Sip] New internet drafts on security, Jari Arkko
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Brett Tate
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• RE: [Sip] bis definition of a call (was [Sip-implementors] Are we allowed to use same Call-ID ...), Jonathan Rosenberg
• RE: [Sip] Stateless CANCEL Processing, Jonathan Rosenberg
• RE: [Sip] How does Stateless Proxy handle Retransmission, Jonathan Rosenberg
• Nov 17 2001
• [Sip] REFER security, Henning Schulzrinne
• [Sip] Negotiating audio mixing capabilities, Mark Zeren
• [SIP] Correlation of Dialogs, Mayer Georg ICM N PG SP ST SN 1
• Nov 16 2001
• RE: [Sip] bis definition of a call (was [Sip-implementors] Are we allowed to use same Call-ID ...), Radu Ionescu
• RE: [Sip] How does Stateless Proxy handle Retransmission, Drage, Keith (Keith)
• RE: [Sip] bis-05: use of 100 Trying, Drage, Keith (Keith)
• [Sip] Agenda Development for Upcoming meetings at IETF-52, Dean Willis
• RE: [Sip] -05bis and Contact, Robert Sparks
• RE: [Sip] -05bis and Contact, Drage, Keith (Keith)
• Re: [Sip] review of draft-ietf-sip-refer-02, Miguel A. Garcia
• RE: [Sip] Session Initiation Protocol, Ranjit Avasarala
• Re: [Sip] Session Initiation Protocol, Chris Altree
• [Sip] Last Call: SIP-H.323 Interworking to Informational, The IESG
• RE: [Sip] Session Initiation Protocol, Ranjit Avasarala
• RE: [Sip] bis definition of a call (was [Sip-implementors] Are we allowed to use same Call-ID ...), Robert Sparks
• [Sip] bis definition of a call (was [Sip-implementors] Are we allowed to use same Call-ID ...), Bob Penfield
• [Sip] Session Initiation Protocol, Hasnaa MOUSTAFA
• [Sip] Session Initiation Protocol, Hasnaa MOUSTAFA
• [Sip] SIP alg for natpt, Thiagarajan Venkatachalam
• Nov 15 2001
• [Sip] Last Call: SIP Session Timer to Proposed Standard, The IESG
• [Sip] Resource-Priority header, Henning G. Schulzrinne
• RE: [Sip] bis-05 mostly NITS - full review, Tan Ya-Ching ICM N PG U ID A 1
• [Sip] bis-05 mostly NITS - full review, John . Hearty
• Re: [Sip] Communications Resource Priority Header, Henning G. Schulzrinne
• Re: [Sip] Communications Resource Priority Header, Dean Willis
• Nov 14 2001
• Re: [Sip] Stateless CANCEL Processing, Bob Penfield
• [Sip] cc-models ID updated, Rohan Mahy
• [Sip] SIP WG - Last Call Weekly Status Update, Rakesh Shah
• [Sip] SIP WG - 6 - Last Call Open Discussion CLOSED - draft-ietf-sip-manyfolks-resource-02.txt, Rakesh Shah
• [Sip] Stateless CANCEL Processing, Jiri Kuthan
• Re: [Sip] does callee need add itself into the same multicast group with caller, Gonzalo Camarillo
• [Sip] does callee need add itself into the same multicast group with caller, Lei Liang
• [Sip] Internet Draft on Call Control URI Parameters, Rohan Mahy
• [Sip] Event package related drafts moved to SIPPING, Rohan Mahy
• Nov 13 2001
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, John . Hearty
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Robert Sparks
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Brett Tate
• [Sip] DS-0 availability, Agboh, Charles
• [Sip] RE: Review of draft-ietf-sip-mib-03.txt Part 1, Tom-PT Taylor
• [Sip] bis-05 compact form vs. short form, William Marshall
• [Sip] review of draft-ietf-sip-refer-02, William Marshall
• [Sip] Summary of Last Call comments on draft-ietf-sip-manyfolks-resource-02, William Marshall
• Nov 12 2001
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, John . Hearty
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, John . Hearty
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• Re: [Sip] Bis-05: Dialog establishment ambiguity, Bob Penfield
• RE: [Sip] Bis-05: Dialog establishment ambiguity, Jonathan Rosenberg
• RE: [Sip] Bis-05: Dialog establishment ambiguity, Mark Watson
• RE: [Sip] Bis-05: Dialog establishment ambiguity, Jonathan Rosenberg
• RE: [Sip] How does Stateless Proxy handle Retransmission, Jonathan Rosenberg
• RE: [Sip] RE: How does Stateless Proxy handle Retransmission, Jonathan Rosenberg
• Re: [Sip] Bis-05: Dialog establishment ambiguity, Bob Penfield
• RE: [Sip] RE: How does Stateless Proxy handle Retransmission, Shan Lu
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Shan Lu
• RE: [Sip] Bis-05: Dialog establishment ambiguity, Mark Watson
• Re: [Sip] Bis-05: Dialog establishment ambiguity, Bob Penfield
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Jari Arkko
• Nov 11 2001
• [Sip] Draft-manyfolks: Capability Exchange, Alan O'Neill
• [Sip] Draft-manyfolks: Lead Role Negotiation, Alan O'Neill
• [Sip] General Issues on draft-manyfolks-resources, Alan O'Neill
• Nov 10 2001
• [Sip] Reference to URL syntax in refer-02?, Pekka Pessi
• Re: [Sip] How does Stateless Proxy handle Retransmission, Christer Holmberg
• [Sip] RE: How does Stateless Proxy handle Retransmission, Jonathan Rosenberg
• [Sip] RFC2543bis-05 minor typo, Francois Audet
• Nov 09 2001
• RE: [Sip] -05bis and Contact, Robert Sparks
• RE: [Sip] How does Stateless Proxy handle Retransmission, Robert Sparks
• [Sip] -05bis and Contact, Vijay Gurbani
• Re: [Sip] Communications Resource Priority Header, Henning G. Schulzrinne
• RE: [Sip] question on "Route" header examples (bis-05), Robert Sparks
• Re: [Sip] Communications Resource Priority Header, Mpierce1
• Re: [Sip] Communications Resource Priority Header, Mpierce1
• [Sip] RE: Multiple Refers (refer-02 draft), Robert Sparks
• Re: [Sip] Communications Resource Priority Header, Henning G. Schulzrinne
• [Sip] Communications Resource Priority Header, Mpierce1
• [Sip] Multiple Refers (refer-02 draft), Sriram Parameswar
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Bob Penfield
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Anders Kristensen
• Re: [Sip] Bis-05: Diaglog establishment ambiguity, Lei Liang
• [Sip] Bis-05: Diaglog establishment ambiguity, Mark Watson
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Tuexen Michael
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• Re: [Sip] How does Stateless Proxy handle Retransmission, Gonzalo Camarillo
• [Sip] Please unsubscribe, Manik Kapil
• Nov 08 2001
• RE: [Sip] How does Stateless Proxy handle Retransmission, Shan Lu
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• Re: [Sip] How does Stateless Proxy handle Retransmission, Gonzalo Camarillo
• RE: [Sip] Bis-5: TLS as secure transport for SIP, aki . niemi
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• [Sip] How does Stateless Proxy handle Retransmission, Shan Lu
• RE: [Sip] Bis-05: Registration and authorizing outgoing requests, Drage, Keith (Keith)
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Tuexen Michael
• RE: [Sip] Retransmisstion detection at Proxy, Jonathan Rosenberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• RE: [Sip] Re-use of Call-ID in the SIP Replaces header, Jonathan Rosenberg
• RE: [Sip] Bis-05: Registration and authorizing outgoing requests, Jonathan Rosenberg
• RE: [Sip] Bis-05 question: re-invite, Jonathan Rosenberg
• RE: [Sip] Bis-05 question: re-invite, Jonathan Rosenberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• RE: Security Considerations (was RE: [Sip] Alert-Info: header), Jonathan Rosenberg
• RE: [Sip] Handling of duplicate requests with differing request p aths., Jonathan Rosenberg
• RE: [Sip] Question regarding 300 Redirect Response, Jonathan Rosenberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• Nov 07 2001
• [Sip] SIP WG - 6 - Last Call Open Discussion CLOSED - draft-ietf-sip-manyfolks-resource-02.txt, Rakesh Shah
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• RE: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Jonathan Rosenberg
• RE: [Sip] Open issue #185, Jonathan Rosenberg
• RE: [Sip] UAS receiving INVITE with valid Route header, Jonathan Rosenberg
• [Sip] Bis-5: Proxy-Require modification, Christer Holmberg
• RE: [Sip] Bis-05: why 200 ms for 100 Trying, Gordon Ledgard
• [Sip] UAS receiving INVITE with valid Route header, krisztian . kiss
• [Sip] Info Method, Paul Pangalos
• [Sip] query on record-route and route treatment, Jonathan Rosenberg
• [Sip] Possible issue with URL comparison: query for input, Jonathan Rosenberg
• [Sip] Open issue #185, Badri Srinivasan S
• Re: [Sip] Introducing the "new bis"-draft-ietf-sip-rfc2543bis-05, James M. Polk
• Nov 06 2001
• Re: [Sip] Introducing the "new bis"-draft-ietf-sip-rfc2543bis-05, Henning G. Schulzrinne
• Re: [Sip] Introducing the "new bis" -draft-ietf-sip-rfc2543bis-05, James M. Polk
• Re: [Sip] Introducing the "new bis" -draft-ietf-sip-rfc2543bis-05, Henning G. Schulzrinne
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• Re: [Sip] 4xx by stateless proxy, Jiri Kuthan
• Re: [Sip] Introducing the "new bis" - draft-ietf-sip-rfc2543bis-05, James M. Polk
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• Re: [Sip] Introducing the "new bis" - draft-ietf-sip-rfc2543bis-05, Henning G. Schulzrinne
• RE: [Sip] Introducing the "new bis" - draft-ietf-sip-rfc2543bis-05, Drage, Keith (Keith)
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Drage, Keith (Keith)
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Shan Lu
• RE: [Sip] Bis-05: why 200 ms for 100 Trying, Drage, Keith (Keith)
• Re: [Sip] 4xx by stateless proxy, Vijay Gurbani
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• RE: [Sip] Handling of duplicate requests with differing request paths., Shan Lu
• RE: [Sip] Handling of duplicate requests with differing request paths., Shan Lu
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Jari Arkko
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• Re: [Sip] Question regarding 300 Redirect Response, Vijay Gurbani
• RE: [Sip] Handling of duplicate requests with differing request p aths., Itamar Gilad
• Security Considerations (was RE: [Sip] Alert-Info: header), Eric Burger
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Tuexen Michael
• Re: [Sip] Question regarding 300 Redirect Response, Christer Holmberg
• Re: [Sip] Question regarding 300 Redirect Response, seshashayi
• [Sip] Question regarding 300 Redirect Response, Chen, Xin (Xin)
• Re: [Sip] Handling of duplicate requests with differing request paths., Christer Holmberg
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Shieh, Hugh
• RE: [Sip] Handling of duplicate requests with differing request paths., Jonathan Rosenberg
• RE: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Jonathan Rosenberg
• RE: [Sip] Bis-05: NITS, Jonathan Rosenberg
• RE: [Sip] Bis-05 question: CANCEL -- Proposed solution, Jonathan Rosenberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• RE: [Sip] RE: [Sipping] Date header field & Expires (bug #178), Jonathan Rosenberg
• RE: [Sip] Via received and DNS advancing for responses, Jonathan Rosenberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• RE: [Sip] Bis[5] NIT - Priority Header Values inconsistent, Jonathan Rosenberg
• RE: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Jonathan Rosenberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Peterson, Jon
• [Sip] Bis[5] NIT - Priority Header Values inconsistent, James M. Polk
• RE: [Sip] Question on draft-ietf-sip-privacy-02, Theodore Havinis
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• Re: [Sip] Question on draft-ietf-sip-privacy-02, Flemming Andreasen
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Henning G. Schulzrinne
• Nov 05 2001
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Allison Mankin
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Jonathan Rosenberg
• Re: [Sip] 4xx by stateless proxy, Jiri Kuthan
• [Sip] Question on draft-ietf-sip-privacy-02, Theodore Havinis
• [Sip] Via received and DNS advancing for responses, Brett Tate
• RE: [Sip] To tags in bis-05, Robert Sparks
• [Sip] To tags in bis-05, McMurry, Kathleen
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Shieh, Hugh
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Shieh, Hugh
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• RE: [Sip] Bis-05: why 200 ms for 100 Trying, Shan Lu
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• Re[2]: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Dorgham Sisalem
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• Re[2]: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Dorgham Sisalem
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Christer Holmberg
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Vijay Gurbani
• Re: [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Bob Penfield
• Re: [Sip] Handling of duplicate requests with differing request paths., Christer Holmberg
• Re: [Sip] Handling of duplicate requests with differing request paths., Bob Penfield
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Vesa Torvinen (LMF)
• RE: [Sip] Bis-5: TLS as secure transport for SIP, James Undery
• [Sip] I-D ACTION:draft-ietf-sip-events-01.txt, Internet-Drafts
• [Sip] RE: [Sipping] RE: [Sip-implementors] 4xx by stateless proxy, Jiri Kuthan
• Nov 04 2001
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Jari Arkko
• [Sip] RE: [Sipping] Date header field & Expires (bug #178), Peterson, Jon
• Nov 03 2001
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Peterson, Jon
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Michael Thomas
• RE: [Sip] Bis-5: TLS as secure transport for SIP, Peterson, Jon
• Re: [Sip] Handling of duplicate requests with differing request paths., Christer Holmberg
• Re: [Sip] Bis-05 question: re-invite, Christer Holmberg
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Juha Heinanen
• Re: [Sip] Bis-5: TLS as secure transport for SIP, Jari Arkko
• [Sip] Bis-05: Registration and authorizing outgoing requests, Shieh, Hugh
• [Sip] Bis-05: NITS, Shieh, Hugh
• [Sip] Bis-5: TLS as secure transport for SIP, Shieh, Hugh
• Nov 02 2001
• Re: [Sip] Bis-05 question: re-invite, Christer Holmberg
• Re: [Sip] Bis-05 question: re-invite, Gonzalo Camarillo