sip  

Messages by Thread

• • 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 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 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 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 he...@sinnreich.net
  • [Sip] Mlab Tools he...@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)
• [P2PSIP] Access control lists for RELOAD storage Narayanan, Vidya
  • Re: [P2PSIP] Access control lists for RELOAD storage Narayanan, Vidya
  • Re: [P2PSIP] Access control lists for RELOAD storage songhaibin 64081
• [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
• Re: [P2PSIP] Notes on section 9: chord Jouni Mäenpää
• Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Bruce Lowekamp
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Bruce Lowekamp
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Salman Abdul Baset
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Dean Willis
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Salman Abdul Baset
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Eric Rescorla
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Salman Abdul Baset
  • Re: [P2PSIP] Comments on draft-ietf-p2psip-diagnostics songhaibin 64081
  • Re: [P2PSIP] Solution space for fragmentation, congestion control and reliability Saverio Mascolo
• [Sip] [Technical Errata Reported] RFC3261 (1742) RFC Errata System
• [P2PSIP] TURN usage in RELOAD Narayanan, Vidya
• [P2PSIP] direct routing support Das, Saumitra
  • Re: [P2PSIP] direct routing support Bruce Lowekamp
  • Re: [P2PSIP] direct routing support Bruce Lowekamp
• [P2PSIP] targeted requests Das, Saumitra
• [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
  • Re: [Sip] FW: [Geopriv] draft-ietf-sip-location-conveyance-13: WGLC comments James M. Polk
• [P2PSIP] Expired draft-ietf-p2psip-concepts-02 Frank Weber
• [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
• [P2PSIP] Configuration Updates in RELOAD Narayanan, Vidya
  • Re: [P2PSIP] Configuration Updates in RELOAD Bruce Lowekamp
  • [P2PSIP] Separation of identity assignment and service provider roles (RE: Configuration Updates in RELOAD) Narayanan, Vidya
  • Re: [P2PSIP] Separation of identity assignment and service provider roles (RE: Configuration Updates in RELOAD) Narayanan, Vidya
• [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] SIP INFO Eric Burger
  • Re: [Sip] SIP INFO Brett Tate
  • Re: [Sip] SIP INFO Eric Burger
  • Re: [Sip] SIP INFO Brett Tate
  • Re: [Sip] SIP INFO Paul Kyzivat
  • [Sip] Is REFER within dialog part of INVITE or subscription usage? (was RE: SIP INFO) Brett Tate
  • Re: [Sip] Is REFER within dialog part of INVITE or subscription usage? (was RE: SIP INFO) Dale Worley
  • Re: [Sip] Is REFER within dialog part of INVITE or subscription usage? (was RE: SIP INFO) Robert Sparks
  • Re: [Sip] Is REFER within dialog part of INVITE or subscription usage? (was RE: SIP INFO) Paul Kyzivat

• Earlier messages
• Later messages