Session Initiation Protocol Discussion Archive - Thread Index

• [Sip] Protocol Action: 'Connection Reuse in the Session Initiation Protocol (SIP)' to Proposed Standard, The IESG
• [Sip] Protocol Action: 'Using Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates' to Proposed Standard, The IESG
• [Sip] RFC 5658 on Addressing Record-Route Issues in the Session Initiation Protocol (SIP), rfc-editor
• [Sip] RFC 5630 on The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP), rfc-editor
• [Sip] RFC 5627 on Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP), rfc-editor
• [Sip] RFC 5626 on Managing Client-Initiated Connections in the Session Initiation Protocol (SIP), rfc-editor
• [Sip] I-D Action:draft-ietf-sip-eku-08.txt, Internet-Drafts
• [Sip] A new version of sip-eku has been released, Vijay K. Gurbani
• [Sip] I-D Action:draft-ietf-sip-eku-07.txt, Internet-Drafts
• [Sip] I-D Action:draft-ietf-sip-eku-06.txt, Internet-Drafts
• [Sip] Securing messages with TEL URI over SIP, Avshalom Houri
  • Re: [Sip] Securing messages with TEL URI over SIP, aayush bhatnagar
  • Re: [Sip] Securing messages with TEL URI over SIP, Paul Kyzivat
    • Re: [Sip] Securing messages with TEL URI over SIP, Olle E. Johansson
• [Sip] Thoughts on multiple registrations to an extension, Sidney San Martín
  • Re: [Sip] Thoughts on multiple registrations to an extension, Dale Worley
    • Re: [Sip] Thoughts on multiple registrations to an extension, Dale Worley
  • Re: [Sip] Thoughts on multiple registrations to an extension, Scott Lawrence
  • <Possible follow-ups>
  • Re: [Sip] Thoughts on multiple registrations to an extension, Attila Sipos
• [Sip] I-D draft-avasarala-dispatch-comm-div-notification, Avasarala Ranjit-A20990
• [Sip] Fwd: Request for community guidance on issue concerning a future meeting of the IETF, Cullen Jennings
• [Sip] Call fork, sairam.pokkunuri
  • Re: [Sip] Call fork, Dean Willis
    • Re: [Sip] Call fork, Paraskevopoulos Pavlos
  • Re: [Sip] Call fork, Dale Worley
• [Sip] two questions for route information preprocessing of initial INVITE with Route headers, ding . xuexin
  • Re: [Sip] two questions for route information preprocessing of initial INVITE with Route headers, Scott Lawrence
  • Re: [Sip] two questions for route information preprocessing of initial INVITE with Route headers, Dale Worley
• [Sip] I-D Action:draft-ietf-sip-session-policy-framework-06.txt, Internet-Drafts
• [Sip] RFC 5621 on Message Body Handling in the Session Initiation Protocol (SIP), rfc-editor
• [Sip] I-D Action:draft-ietf-sip-certs-09.txt, Internet-Drafts
• [Sip] updates to draft-ietf-sip-certs, Jason Fischl
• [Sip] Changed From Tag in Spiral Request, Manjunath Warad
  • Re: [Sip] Changed From Tag in Spiral Request, Dale Worley
• [Sip] Question on draft-ietf-sip-outbound-20 draft: multiple flow creation, Vavilapalli Srikanth-A19563
  • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multiple flowcreation, Francois Audet
    • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multiple flowcreation, Vavilapalli Srikanth-A19563
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Francois Audet
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Vavilapalli Srikanth-A19563
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Scott Lawrence
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Scott Lawrence
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Francois Audet
      • Re: [Sip] [Sip-implementors] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Iñaki Baz Castillo
      • Re: [Sip] Question on draft-ietf-sip-outbound-20 draft: multipleflowcreation, Nils Ohlmeier
• [Sip] 200 OK response for hold with different media capabilities, sunil.bhagat
  • Re: [Sip] 200 OK response for hold with different media capabilities, Avasarala Ranjit-A20990
    • Re: [Sip] [Sip-implementors] 200 OK response for hold with different media capabilities, Paul Kyzivat
      • Re: [Sip] [Sip-implementors] 200 OK response for hold with different media capabilities, Avasarala Ranjit-A20990
      • Re: [Sip] [Sip-implementors] 200 OK response for hold with different media capabilities, Paul Kyzivat
  • Re: [Sip] 200 OK response for hold with different media capabilities, Vikram Chhibber
    • Re: [Sip] [Sip-implementors] 200 OK response for hold withdifferent media capabilities, Avasarala Ranjit-A20990
      • Re: [Sip] [Sip-implementors] 200 OK response for hold withdifferent media capabilities, aayush bhatnagar
      • Re: [Sip] [Sip-implementors] 200 OK response for hold withdifferent media capabilities, Vikram Chhibber
      • Re: [Sip] [Sip-implementors] 200 OK response for hold withdifferent media capabilities, Vikram Chhibber
• [Sip] Protocol Action: 'Addressing Record-Route issues in the Session Initiation Protocol (SIP)' to Proposed Standard, The IESG
• Re: [Sip] Pharmacy Online Sale 88% OFF!, VIAGRA Inc .
• [Sip] Protocol Action: 'An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package' to Proposed Standard, The IESG
• [Sip] New version of "draft-avasasarala-dispatch-comm-diversion-info" draft submitted, Avasarala Ranjit-A20990
  • Re: [Sip] New version of"draft-avasasarala-dispatch-comm-diversion-info" draft submitted, Gilad Shaham
    • Re: [Sip] New version of "draft-avasasarala-dispatch-comm-diversion-info" draft submitted, Avasarala Ranjit-A20990
• [Sip] I-D Action:draft-ietf-sip-record-route-fix-10.txt, Internet-Drafts
• [Sip] I-D Action:draft-ietf-sip-record-route-fix-09.txt, Internet-Drafts
• [Sip] draft-levy-sip-diversion-10: examples containing uselessly quoted values, Brett Tate
• [Sip] Progress on draft-ietfsip-record-route-fix, Dean Willis
• [Sip] Usage of the 'Route' header., Yoav Gaziel
  • Re: [Sip] Usage of the 'Route' header., Christer Holmberg
  • Re: [Sip] Usage of the 'Route' header., Tomasz Zieleniewski
• [Sip] Contact header in 200 OK, sandip gangakhedkar
  • Re: [Sip] Contact header in 200 OK, T Satyanarayana-A12694
    • Re: [Sip] Contact header in 200 OK, sandip gangakhedkar
  • Re: [Sip] Contact header in 200 OK, Goyal, Devki
  • Re: [Sip] Contact header in 200 OK, Dale Worley
• [Sip] New version of connect-reuse issued, post IESG review, Vijay K. Gurbani
• [Sip] I-D Action:draft-ietf-sip-connect-reuse-14.txt, Internet-Drafts
• [Sip] draft-ietf-sip-record-route-fix-08 Changes, BONNAERENS Ben
  • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Elwell, John
    • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, BONNAERENS Ben
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Elwell, John
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, BONNAERENS Ben
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Elwell, John
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Robert Sparks
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Elwell, John
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Dean Willis
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Robert Sparks
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Elwell, John
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Dean Willis
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, BONNAERENS Ben
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Dean Willis
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Gilad Shaham
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Robert Sparks
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Olle E. Johansson
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Dean Willis
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, Tomasz Zieleniewski
      • Re: [Sip] draft-ietf-sip-record-route-fix-08 Changes, BONNAERENS Ben
• [Sip] I-D Action:draft-ietf-sip-record-route-fix-08.txt, Internet-Drafts
• [Sip] Record-Route-fix, Robert Sparks
• [Sip] SIP Dialog Match, Karunesh Sharma
  • Re: [Sip] SIP Dialog Match, aayush bhatnagar
    • Re: [Sip] SIP Dialog Match, Dale Worley
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, Dale Worley
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, Dale Worley
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, Dale Worley
      • Re: [Sip] SIP Dialog Match, T Satyanarayana-A12694
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, T Satyanarayana-A12694
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, T Satyanarayana-A12694
      • Re: [Sip] SIP Dialog Match, T Satyanarayana-A12694
      • Re: [Sip] SIP Dialog Match, Karunesh Sharma
      • Re: [Sip] SIP Dialog Match, Dale Worley
• [Sip] I-D Action:draft-ietf-sip-certs-08.txt, Internet-Drafts
• [Sip] I-D Action:draft-ietf-sip-xcapevent-08.txt, Internet-Drafts
• [Sip] I-D Action:draft-ietf-sip-record-route-fix-07.txt, Internet-Drafts
• [Sip] Protocol Action: 'Message Body Handling in the Session Initiation Protocol (SIP)' to Proposed Standard, The IESG
• [Sip] Last Call: draft-ietf-sip-record-route-fix (Addressing Record-Route issues in the Session Initiation Protocol (SIP)) to BCP, The IESG
• [Sip] AD review : draft-ietf-sip-record-route-fix, Robert Sparks
• [Sip] Last Call: draft-ietf-sip-body-handling (Message Body Handling in the Session Initiation Protocol (SIP)) to Proposed Standard, The IESG
• [Sip] [Fwd: [dispatch] Protocol Action: 'Managing Client Initiated Connections in the Session Initiation Protocol (SIP)' to Proposed Standard], Dean Willis
• [Sip] [Fwd: I-D Action:draft-ietf-sip-outbound-20.txt], Dean Willis
• [Sip] CORRECTED Protocol Action: 'Managing Client Initiated Connections in the Session Initiation Protocol (SIP)' to Proposed Standard, IESG Secretary
• [Sip] Document Action: 'UA-Driven Privacy Mechanism for SIP' to Informational RFC, The IESG
• [Sip] Reuse of Sip Call-Id question..., Cahall, Glenn
  • <Possible follow-ups>
  • Re: [Sip] Reuse of Sip Call-Id question..., Attila Sipos
    • Re: [Sip] Reuse of Sip Call-Id question..., Martin Larochelle
• [Sip] [sip] I-D Action:draft-ietf-sip-outbound-19.txt, DRAGE, Keith (Keith)
  • Re: [Sip] [sip] I-D Action:draft-ietf-sip-outbound-19.txt, Mary Barnes
• [Sip] Not my day for tidy; draft-ietf-sip-xcapevent-07 submitted, Dean Willis
• [Sip] More on xcapevent -06, Dean Willis
• [Sip] Revised xcapevent to -06, Dean Willis
• [Sip] [sip] I-D Action:draft-ietf-sip-outbound-18.txt, DRAGE, Keith (Keith)
• [Sip] Draft ietf-sip-xcapevent revised, many open questions, Dean Willis
  • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Jari Urpalainen
    • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Robert Sparks
      • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Jari Urpalainen
  • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Byron Campen
    • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Jari Urpalainen
    • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Anders Lindgren C
      • Re: [Sip] Draft ietf-sip-xcapevent revised, many open questions, Byron Campen
• [Sip] Last Call: draft-ietf-sip-connect-reuse (Connection Reuse in the Session Initiation Protocol (SIP)) to Proposed Standard, The IESG
• [Sip] Last Call: draft-ietf-sip-eku (Using Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates) to Proposed Standard, The IESG
• [Sip] Gen-ART review of draft-ietf-sip-outbound-17, Black_David
  • Re: [Sip] Gen-ART review of draft-ietf-sip-outbound-17, Cullen Jennings
    • Re: [Sip] Gen-ART review of draft-ietf-sip-outbound-17, Black_David
• [Sip] http://tools.ietf.org/wg/sip/ no longer updated, Brett Tate
• [Sip] I-D Action:draft-ietf-sip-eku-05.txt, DRAGE, Keith (Keith)
• [Sip] I-D Action:draft-ietf-sip-domain-certs-04.txt, DRAGE, Keith (Keith)
• [Sip] I-D Action:draft-ietf-sip-ua-privacy-08.txt, DRAGE, Keith (Keith)
• [Sip] New versions of domain-certs and sip-eku, Vijay K. Gurbani
• [Sip] REVISED Last Call: draft-ietf-sip-outbound (Managing Client Initiated Connections in the Session Initiation Protocol (SIP)) to Proposed Standard, The IESG
• [Sip] Fwd: Last Call: draft-ietf-sip-outbound (Managing Client Initiated Connections in the Session Initiation Protocol (SIP)) to Proposed Standard, Robert Sparks
• Re: [Sip] SIP WG closed (was RE: Question about Accept-Language), Attila Sipos
  • Re: [Sip] SIP WG closed (was RE: Question about Accept-Language), Vijay K. Gurbani
• [Sip] Question about Accept-Language, Szilagyi, Mike
  • Re: [Sip] Question about Accept-Language, Dean Willis
    • Re: [Sip] Question about Accept-Language, DRAGE, Keith (Keith)
• [Sip] RFC 3261 Accept-Language change to allow empty, Rawsthorne, Alan \(Alan\)
  • <Possible follow-ups>
  • Re: [Sip] RFC 3261 Accept-Language change to allow empty, Attila Sipos
• [Sip] WG Action: Conclusion of Session Initiation Protocol (sip), IESG Secretary
• [Sip] Last Call: draft-ietf-sip-ua-privacy (UA-Driven Privacy Mechanism for SIP) to Informational RFC, The IESG
• [Sip] Registration for SIPit 24 closes next week, Robert Sparks
• [Sip] SIPCORE -- If you're not subscribed, you're missing stuff, Adam Roach
• [Sip] Draft new version: draft-holmberg-sipcore-keep-00 (previously known as draft-holmberg-sip-keep), Christer Holmberg
• [Sip] Linked minutes, slides, and audio recordings for SIP at IETF 74, Dean Willis
• [Sip] Future of this mailing list, DRAGE, Keith (Keith)
• [Sip] Draft SIP minutes for IETF 74 posted, Dean Willis
• [Sip] Fwd: [RAI] SIP and SIPPING, Dean Willis
  • Re: [Sip] Fwd: [RAI] SIP and SIPPING, Vijay K. Gurbani
    • Re: [Sip] Fwd: [RAI] SIP and SIPPING, Dean Willis
• [Sip] SIPCORE and DISPATCH have been approved - Please see the RAI list for more info, Robert Sparks
• [Sip] bug #2 in draft-ietf-sip-outbound-16 grammar, Florian Zumbiehl
• [Sip] bug #1 in draft-ietf-sip-outbound-16 grammar, Florian Zumbiehl
  • Re: [Sip] bug #1 in draft-ietf-sip-outbound-16 grammar, Rohan Mahy
    • Re: [Sip] bug #1 in draft-ietf-sip-outbound-16 grammar, Dean Willis
• [Sip] bug in draft-ietf-sip-gruu-15 grammar, Florian Zumbiehl
  • Re: [Sip] bug in draft-ietf-sip-gruu-15 grammar, Andrew Allen
    • Re: [Sip] bug in draft-ietf-sip-gruu-15 grammar, Paul Kyzivat
      • Re: [Sip] bug in draft-ietf-sip-gruu-15 grammar, Dale Worley
      • Re: [Sip] bug in draft-ietf-sip-gruu-15 grammar, Paul Kyzivat
      • Re: [Sip] bug in draft-ietf-sip-gruu-15 grammar, Dale Worley
• [Sip] Registration for SIPIt 24 closes in 3 weeks., Robert Sparks
• [Sip] I-D Action:draft-ietf-sip-199-08.txt, Internet-Drafts
• [Sip] Draft new version: draft-ietf-sip-199-08, Christer Holmberg
• [Sip] draft-ietf-sip-199-07: 199 response and local ringtone generation, Hans Erik van Elburg
  • Re: [Sip] draft-ietf-sip-199-07: 199 response and local ringtone generation, Christer Holmberg
• [Sip] Publication request for draft-ietf-sip-eku, DRAGE, Keith (Keith)
• [Sip] Clarification on RFC 4458: SIP URIs for Applications such as Voicemail and Interactive Voice Response (IVR), DRAGE, Keith (Keith)
  • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications such as Voicemail and Interactive Voice Response (IVR), Francois Audet
    • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications suchas Voicemail and Interactive Voice Response (IVR), marianne.mohali
      • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications suchas Voicemail and Interactive Voice Response (IVR), Francois Audet
  • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications such as Voicemail and Interactive Voice Response (IVR), Hans Erik van Elburg
    • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications such as Voicemail and Interactive Voice Response (IVR), DRAGE, Keith (Keith)
      • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications such as Voicemail and Interactive Voice Response (IVR), Hans Erik van Elburg
      • Re: [Sip] Clarification on RFC 4458: SIP URIs for Applications suchas Voicemail and Interactive Voice Response (IVR), Francois Audet
• [Sip] Publication request for draft-ietf-sip-domain-certs, DRAGE, Keith (Keith)
• [Sip] I-D Action:draft-ietf-sip-eku-04.txt, Internet-Drafts
• [Sip] I-D Action:draft-ietf-sip-domain-certs-03.txt, Internet-Drafts
• [Sip] Publication request for draft-ietf-sip-ua-privacy, DRAGE, Keith (Keith)
• [Sip] I-D Action:draft-ietf-sip-ua-privacy-07.txt, Internet-Drafts
• [Sip] RFC 5479 on Requirements and Analysis of Media Security Management Protocols, rfc-editor
• [Sip] My take on where we are with Identity, Elwell, John
  • Re: [Sip] My take on where we are with Identity, Dan Wing
• [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Munjo Yu
  • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, eburger
    • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Keith Moore
      • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Paul Kyzivat
      • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Keith Moore
      • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Munjo Yu
      • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, John C Klensin
  • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Keith Moore
  • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Dale Worley
    • Re: [Sip] Proposal of Non-Sequential Group Notion in ABNF w/ a SIP case, Munjo Yu
• [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
  • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
  • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Francois Audet
    • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Attila Sipos
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Spencer Dawkins
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Tan, Ya Ching (NSN - DE/Munich)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07 - comment on section 7, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07 - comment on section 7, DRAGE, Keith (Keith)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07 - comment onsection 7, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07 - comment onsection 7, DRAGE, Keith (Keith)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07 - comment onsection 7, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Tan, Ya Ching (NSN - DE/Munich)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Tan, Ya Ching (NSN - DE/Munich)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, DRAGE, Keith (Keith)
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
      • Re: [Sip] Draft new version: draft-ietf-sip-199-07, Christer Holmberg
• [Sip] I-D Action:draft-ietf-sip-199-07.txt, Internet-Drafts
• [Sip] WGLC comments on draft-ietf-sip-location-conveyance-13, Thomson, Martin
• [Sip] secure-call-id vs. session-id, Hadriel Kaplan
  • Re: [Sip] secure-call-id vs. session-id, L.Liess
• [Sip] Media vs Signaling identity (was Re: francois' comments and why RFC4474 not used in the field), Victor Pascual Ávila
  • Re: [Sip] Media vs Signaling identity (was Re: francois' comments and why RFC4474 not used in the field), Jonathan Rosenberg
  • Re: [Sip] Media vs Signaling identity (was Re: francois' comments andwhy RFC4474 not used in the field), Elwell, John
    • Re: [Sip] Media vs Signaling identity (was Re: francois' comments andwhy RFC4474 not used in the field), Victor Pascual Ávila
      • Re: [Sip] Media vs Signaling identity (was Re: francois' comments andwhy RFC4474 not used in the field), Elwell, John
• [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
  • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
  • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Uzelac, Adam
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Michael Procter
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jonathan Rosenberg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jonathan Rosenberg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hans Erik van Elburg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
  • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
  • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, DRAGE, Keith (Keith)
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dwight, Timothy M (Tim)
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Christer Holmberg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dwight, Timothy M (Tim)
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dwight, Timothy M (Tim)
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hans Erik van Elburg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Adam Roach
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Anthony D Pike
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Adam Roach
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Adam Roach
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Adam Roach
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jon Peterson
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hans Erik van Elburg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Christer Holmberg
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, henry at sinnreich.net
      • [Sip] Mlab Tools, henry at sinnreich.net
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Paul Kyzivat
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dan Wing
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Victor Pascual Ávila
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Hadriel Kaplan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dwight, Timothy M (Tim)
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Elwell, John
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Francois Audet
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Dean Willis
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
    • Re: [Sip] francois' comments and why RFC4474 not used in the field, Jiri Kuthan
      • Re: [Sip] francois' comments and why RFC4474 not used in the field, Cullen Jennings
• Re: [Sip] [Geopriv] Geo URI and privacy URI, DOLLY, MARTIN C, ATTLABS
• [Sip] Completion of draft-ietf-sip-ua-privacy-06, DRAGE, Keith (Keith)
• [Sip] draft-boulton-sip-endpoint-view-00, Chris Boulton
• [Sip] draft-kaplan-sip-secure-call-id-00, DRAGE, Keith (Keith)
• [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Jonathan Rosenberg
  • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Hadriel Kaplan
    • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Jiri Kuthan
      • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, L.Liess
      • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Jiri Kuthan
      • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Theo Zourzouvillys
      • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Victor Pascual Ávila
  • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Spencer Dawkins
  • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Venkatesh
    • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Victor Pascual Ávila
    • Re: [Sip] The problem with draft-kaplan-sip-secure-call-id-00, Hadriel Kaplan
• [Sip] Reminder: SIPit24 registration closes April 30, Robert Sparks
• [Sip] [Technical Errata Reported] RFC3261 (1742), RFC Errata System
• [Sip] SIP-CLF Ad Hoc, Eric Burger
• [Sip] UA Config Ad Hoc, Eric Burger
  • Re: [Sip] UA Config Ad Hoc, Eric Burger
• [Sip] FW: [Geopriv] draft-ietf-sip-location-conveyance-13: WGLC comments, Thomson, Martin
  • Message not available
    • Re: [Sip] FW: [Geopriv] draft-ietf-sip-location-conveyance-13: WGLC comments, James M. Polk
• [Sip] Slides for SIP and SIPPING sessions, DRAGE, Keith (Keith)
  • Re: [Sip] [Sipping] Slides for SIP and SIPPING sessions, Mary Barnes
    • [Sip] FW: [Sipping] Slides for SIP and SIPPING sessions, Mary Barnes
• [Sip] skype for sip announced, Dean Willis
• [Sip] Skype for SIP, Dan Wing
  • Re: [Sip] Skype for SIP, Victor Pascual Ávila
  • Re: [Sip] Skype for SIP, Dan York
    • Re: [Sip] Skype for SIP, Uzelac, Adam
• [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Elwell, John
  • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
    • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Paul Kyzivat
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Paul Kyzivat
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
    • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Hadriel Kaplan
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Bob Penfield
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Hadriel Kaplan
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Dale Worley
  • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Dale Worley
    • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Paul Kyzivat
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Dale Worley
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Adam Roach
      • Re: [Sip] Comment on draft-roach-sipcore-rfc3265bis-00, Dale Worley
• [Sip] comments on draft-kaplan-sip-session-id-01, Jonathan Rosenberg
  • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Hadriel Kaplan
  • Re: [Sip] comments on draft-kaplan-sip-session-id-01, L.Liess
  • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Dale Worley
    • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Hadriel Kaplan
      • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Dale Worley
      • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Venkatesh
      • Re: [Sip] comments on draft-kaplan-sip-session-id-01, DRAGE, Keith (Keith)
      • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Venkatesh
      • Re: [Sip] comments on draft-kaplan-sip-session-id-01, Hadriel Kaplan
      • Re: [Sip] draft-kaplan-sip-session-id-02, L.Liess
      • Re: [Sip] draft-kaplan-sip-session-id-02, DOLLY, MARTIN C, ATTLABS
      • Re: [Sip] draft-kaplan-sip-session-id-02, Theo Zourzouvillys
• [Sip] comments on draft-kaplan-sip-secure-call-id-00.txt, Jonathan Rosenberg
  • Re: [Sip] comments on draft-kaplan-sip-secure-call-id-00.txt, Hadriel Kaplan
• [Sip] comments on draft-barnes-sip-rfc4244bis-00.txt, Jonathan Rosenberg
  • Re: [Sip] comments on draft-barnes-sip-rfc4244bis-00.txt, Francois Audet
    • Re: [Sip] comments on draft-barnes-sip-rfc4244bis-00.txt, Elwell, John
      • Re: [Sip] comments on draft-barnes-sip-rfc4244bis-00.txt, Mary Barnes
• [Sip] Policy to register media feature tags, Gonzalo Camarillo
  • Re: [Sip] Policy to register media feature tags, Paul Kyzivat
    • Re: [Sip] Policy to register media feature tags, Hans Erik van Elburg
      • Re: [Sip] Policy to register media feature tags, Paul Kyzivat
      • Re: [Sip] Policy to register media feature tags, Hans Erik van Elburg
      • Re: [Sip] Policy to register media feature tags, Paul Kyzivat
    • Re: [Sip] Policy to register media feature tags, Atle Monrad
      • Re: [Sip] Policy to register media feature tags, Paul Kyzivat
  • Re: [Sip] Policy to register media feature tags, Atle Monrad
• [Sip] DEFINITION: Target, Address, Name, Retarget, Reroute, Christer Holmberg
  • Re: [Sip] DEFINITION: Target, Address, Name, Retarget, Reroute, DRAGE, Keith (Keith)
    • Re: [Sip] DEFINITION: Target, Address, Name, Retarget, Reroute, Paul Kyzivat
• [Sip] Publication requested for draft-ietf-sip-record-route-fix-06, Dean Willis
• [Sip] New rev of Location Conveyance (to -13), James M. Polk
• [Sip] WGLC for draft-ietf-sip-location-conveyance, DRAGE, Keith (Keith)
• [Sip] comments on draft-zourzouvillys-sip-via-cookie-02, Jonathan Rosenberg
  • Re: [Sip] comments on draft-zourzouvillys-sip-via-cookie-02, Theo Zourzouvillys
• [Sip] draft-ietf-sip-199-06, Dale Worley
  • Re: [Sip] draft-ietf-sip-199-06, Christer Holmberg
  • <Possible follow-ups>
  • [Sip] draft-ietf-sip-199-06, Adam Roach
    • Re: [Sip] draft-ietf-sip-199-06, Christer Holmberg