IETF Discussion (thread)
Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice,
Russ Housley,
2013/12/30
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, David Farmer, 2013/12/30
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy, 2013/12/30
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, David Farmer, 2013/12/30
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Andrew Sullivan, 2013/12/30
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, t.p., 2013/12/31
- RE: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Yoav Nir, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Andrew Sullivan, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, t.p., 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Ted Lemon, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Andrew Sullivan, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Ted Lemon, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, joel jaeggli, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Abdussalam Baryun, 2013/12/31
- Re: we're all yahoos on this bus, was Concerns about draft-moonesamy-ietf-conduct, John Levine, 2013/12/31
- Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Russ Housley, 2013/12/31
ITCG?,
Brian E Carpenter,
2013/12/22
WG Chair as author of WG document,
SM,
2013/12/20
- Re: WG Chair as author of WG document, Ted Lemon, 2013/12/20
- Re: WG Chair as author of WG document, Jari Arkko, 2013/12/20
- Re: WG Chair as author of WG document, Dave Crocker, 2013/12/20
- Re: WG Chair as author of WG document, Abdussalam Baryun, 2013/12/20
- Re: WG Chair as author of WG document, Scott Brim, 2013/12/20
- Re: WG Chair as author of WG document, Loa Andersson, 2013/12/20
- Re: WG Chair as author of WG document, Stephen Kent, 2013/12/20
Chang'E 3,
Michael Richardson,
2013/12/14
- RE: Chang'E 3, l.wood, 2013/12/14
- Re: Chang'E 3, Michael Richardson, 2013/12/24
- RE: Chang'E 3, l.wood, 2013/12/24
- Re: Chang'E 3, Michael Richardson, 2013/12/24
- RE: Chang'E 3, l.wood, 2013/12/25
- Chang'E 3, Abdussalam Baryun, 2013/12/26
- RE: Chang'E 3, l.wood, 2013/12/26
- Re: Chang'E 3, Abdussalam Baryun, 2013/12/27
- RE: Chang'E 3, l.wood, 2013/12/27
- Re: Chang'E 3, Abdussalam Baryun, 2013/12/27
- RE: Chang'E 3, l.wood, 2013/12/27
- Re: Re: Chang'E 3, Jiankang Yao, 2013/12/30
- Re: Chang'E 3, Abdussalam Baryun, 2013/12/30
- RE: Re: Chang'E 3, l.wood, 2013/12/30
- RE: Chang'E 3, l.wood, 2013/12/14
Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard,
Paul Hoffman,
2013/12/13
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Alyssa Rowan, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Yoav Nir, 2013/12/13
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Martin Thomson, 2013/12/13
- RE: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Stephan Friedl (sfriedl), 2013/12/13
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Watson Ladd, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Alyssa Rowan, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Martin Thomson, 2013/12/13
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Nikos Mavrogiannopoulos, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Alyssa Rowan, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Yoav Nir, 2013/12/14
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Alyssa Rowan, 2013/12/15
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Randy Presuhn, 2013/12/16
- Re: [TLS] Last Call: <draft-ietf-tls-applayerprotoneg-03.txt> (Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension) to Proposed Standard, Mohamad Badra, 2013/12/15
RE: [rtcweb] Straw Poll on Video Codec Alternatives,
Matthew Kaufman (SKYPE),
2013/12/09
- Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives, Magnus Westerlund, 2013/12/10
- Re: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives, Harald Alvestrand, 2013/12/10
- RE: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives, Matthew Kaufman (SKYPE), 2013/12/10
- RE: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives, Matthew Kaufman (SKYPE), 2013/12/10
- Re: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, Adam Roach, 2013/12/10
- RE: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, l.wood, 2013/12/10
- Re: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, Martin Thomson, 2013/12/10
- RE: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, Matthew Kaufman (SKYPE), 2013/12/11
- RE: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, l.wood, 2013/12/11
- Re: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives, Ted Hardie, 2013/12/11
- Re: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives, Gonzalo Camarillo, 2013/12/12
- RE: [rtcweb] Straw Poll on Video Codec Alternatives, Brent Kelly, 2013/12/10
- Why the Straw Poll, Cullen Jennings (fluffy), 2013/12/11
Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02,
Eliot Lear,
2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Eliot Lear, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Stephen Farrell, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Eliot Lear, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Dave Cridland, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Stephen Farrell, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Eliot Lear, 2013/12/09
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Stephen Farrell, 2013/12/10
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Jari Arkko, 2013/12/10
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Alissa Cooper, 2013/12/10
- RE: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Romascanu, Dan (Dan), 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Stephen Farrell, 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Phillip Hallam-Baker, 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Brian E Carpenter, 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Alissa Cooper, 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Scott Brim, 2013/12/11
- Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02, Theodore Ts'o, 2013/12/10
Editorial thoughts on draft-farrell-perpass-attack-02,
Bjoern Hoehrmann,
2013/12/06
- Message not available
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Stephen Farrell, 2013/12/09
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Scott Brim, 2013/12/11
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Stewart Bryant, 2013/12/11
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Ted Hardie, 2013/12/11
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Eliot Lear, 2013/12/11
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Scott Brim, 2013/12/11
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Jari Arkko, 2013/12/15
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Dave Crocker, 2013/12/15
- RE: Editorial thoughts on draft-farrell-perpass-attack-02, Dearlove, Christopher (UK), 2013/12/16
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Stephen Kent, 2013/12/16
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, t.p., 2013/12/16
- Re: Editorial thoughts on draft-farrell-perpass-attack-02, Stephen Kent, 2013/12/16
- RE: Editorial thoughts on draft-farrell-perpass-attack-02, Dearlove, Christopher (UK), 2013/12/17
Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC,
Cullen Jennings (fluffy),
2013/12/05
- RE: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Roni Even, 2013/12/05
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Colin Perkins, 2013/12/06
- RE: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Bernard Aboba, 2013/12/06
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Cullen Jennings (fluffy), 2013/12/09
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Colin Perkins, 2013/12/09
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Martin Thomson, 2013/12/09
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Cullen Jennings (fluffy), 2013/12/09
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Colin Perkins, 2013/12/10
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Richard Barnes, 2013/12/10
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Dale R. Worley, 2013/12/10
- Re: [AVTCORE] Last Call: <draft-ietf-avt-srtp-not-mandatory-14.txt> (Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution) to Informational RFC, Pete Resnick, 2013/12/09
Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01,
l.wood,
2013/12/04
- Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Ted Lemon, 2013/12/04
- RE: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/04
- Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Ted Lemon, 2013/12/04
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Theodore Ts'o, 2013/12/04
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Hannes Tschofenig, 2013/12/04
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Mark Nottingham, 2013/12/04
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/06
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stephen Farrell, 2013/12/06
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/07
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stephen Farrell, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Phillip Hallam-Baker, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Brian E Carpenter, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stewart Bryant (stbryant), 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Jari Arkko, 2013/12/10
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Phillip Hallam-Baker, 2013/12/10
- Re:Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, t.p., 2013/12/10
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Hannes Tschofenig, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Bjoern Hoehrmann, 2013/12/08
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/08
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Jari Arkko, 2013/12/10
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Eliot Lear, 2013/12/10
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Phillip Hallam-Baker, 2013/12/10
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, l.wood, 2013/12/10
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, t.p., 2013/12/10
- Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Josh Howlett, 2013/12/05
- Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stephen Farrell, 2013/12/05
- Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Josh Howlett, 2013/12/05
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stephen Farrell, 2013/12/05
- RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Josh Howlett, 2013/12/05
- Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01, Stephen Farrell, 2013/12/05
RTCWeb proposal,
Phillip Hallam-Baker,
2013/12/04
- Message not available
- Re: RTCWeb proposal, Stephan Wenger, 2013/12/04
- Re: RTCWeb proposal, Phillip Hallam-Baker, 2013/12/04
- Re: RTCWeb proposal, Harald Alvestrand, 2013/12/05
- Re: RTCWeb proposal, Stephan Wenger, 2013/12/05
- Re: RTCWeb proposal, Phillip Hallam-Baker, 2013/12/05
- Re: RTCWeb proposal, Cullen Jennings (fluffy), 2013/12/06
- Re: RTCWeb proposal, Harald Alvestrand, 2013/12/06
- Re: RTCWeb proposal, Phillip Hallam-Baker, 2013/12/06
Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice,
Jari Arkko,
2013/12/03
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Wesley Eddy, 2013/12/03
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/09
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/09
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/09
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/09
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/09
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Josh Howlett, 2013/12/09
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/10
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/11
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/11
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Avri Doria, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Randy Bush, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Randy Bush, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Avri Doria, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/11
- Privacy protection takes more than resolve (was Re: Last Call: <draft-farrell-perpass-attack-02.txt..., Dave Crocker, 2013/12/11
- Re: Privacy protection takes more than resolve (was Re: Last Call: <draft-farrell-perpass-attack-02.txt..., Scott Brim, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stefan Winter, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Randy Bush, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, John C Klensin, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/11
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Bjoern Hoehrmann, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, John C Klensin, 2013/12/31
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Bjoern Hoehrmann, 2013/12/31
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Dave Crocker, 2013/12/31
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Abdussalam Baryun, 2013/12/31
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, John C Klensin, 2013/12/31
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Melinda Shore, 2013/12/31
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/11
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Dale R. Worley, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Eliot Lear, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Phillip Hallam-Baker, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Ted Faber, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Phillip Hallam-Baker, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Mark Nottingham, 2013/12/06
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/12
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Eliot Lear, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Eliot Lear, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Eliot Lear, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Eliot Lear, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/16
- Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice - extended, Jari Arkko, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Spencer Dawkins, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/14
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Sam Hartman, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/14
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, l.wood, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Tim Bray, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Pete Resnick, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Brian E Carpenter, 2013/12/13
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Jari Arkko, 2013/12/14
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, SM, 2013/12/03
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/15
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Bjoern Hoehrmann, 2013/12/15
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Sam Hartman, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Bjoern Hoehrmann, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Sam Hartman, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Andrew Sullivan, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Andrew Sullivan, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Andrew Sullivan, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Ted Lemon, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Andrew Sullivan, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Joseph Lorenzo Hall, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, t.p., 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Bjoern Hoehrmann, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stewart Bryant, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Scott Brim, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Farrell, 2013/12/17
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Abdussalam Baryun, 2013/12/19
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Stephen Kent, 2013/12/16
- Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Murray S. Kucherawy, 2013/12/17
- RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice, Michel Py, 2013/12/31
I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt,
Ines Robles,
2013/12/03
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Abdussalam Baryun, 2013/12/04
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Jari Arkko, 2013/12/04
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Arturo Servin, 2013/12/05
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Brian E Carpenter, 2013/12/05
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Arturo Servin, 2013/12/05
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Solarus, 2013/12/17
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, S Moonesamy, 2013/12/18
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Jari Arkko, 2013/12/09
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Arturo Servin, 2013/12/09
- Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt, Jari Arkko, 2013/12/10
Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft),
Alex Russell,
2013/12/02
- Message not available
- Message not available
- Message not available
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Tim Berners-Lee, 2013/12/02
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Noah Mendelsohn, 2013/12/02
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Phillip Hallam-Baker, 2013/12/02
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Ashok Malhotra, 2013/12/03
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Phillip Hallam-Baker, 2013/12/02
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Nico Williams, 2013/12/03
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Phillip Hallam-Baker, 2013/12/02
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), John Cowan, 2013/12/03
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Nico Williams, 2013/12/03
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), John Cowan, 2013/12/03
- Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft), Alex Russell, 2013/12/03
RE: [rtcweb] Alternative decision process in RTCWeb,
DRAGE, Keith (Keith),
2013/12/02
- Message not available
- Message not available
- Re: [rtcweb] Alternative decision process in RTCWeb, Dave Crocker, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Phillip Hallam-Baker, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Ted Lemon, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Eric Burger, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Jim Gettys, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Phillip Hallam-Baker, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Jari Arkko, 2013/12/04
- Re: [rtcweb] Alternative decision process in RTCWeb, Phillip Hallam-Baker, 2013/12/04
- Re: [rtcweb] Alternative decision process in RTCWeb, Hector Santos, 2013/12/03
- 0, 1, or many standards and their impact (or not), Eliot Lear, 2013/12/03
- Re: 0, 1, or many standards and their impact (or not), Phillip Hallam-Baker, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Harald Alvestrand, 2013/12/03
- Re: [rtcweb] Alternative decision process in RTCWeb, Mary Barnes, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Ron, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Bjoern Hoehrmann, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Phillip Hallam-Baker, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Bjoern Hoehrmann, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Martin Thomson, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Stephan Wenger, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, David Singer, 2013/12/04
- Re: [rtcweb] Alternative decision process in RTCWeb, Sam Hartman, 2013/12/02
- Re: [rtcweb] Alternative decision process in RTCWeb, Eric Burger, 2013/12/04
Re: https at ietf.org,
David Conrad,
2013/12/01
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/02
- Re: https at ietf.org, David Conrad, 2013/12/02
- Re: https at ietf.org, Doug Barton, 2013/12/06
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/08
- Re: https at ietf.org, David Conrad, 2013/12/08
- Re: https at ietf.org, Doug Barton, 2013/12/08
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/08
- Re: https at ietf.org, Doug Barton, 2013/12/09
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/09
- Re: https at ietf.org, Mark Andrews, 2013/12/09
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/09
- Re: https at ietf.org, John C Klensin, 2013/12/10
- Re: https at ietf.org, Doug Barton, 2013/12/10
- Re: https at ietf.org, Phillip Hallam-Baker, 2013/12/10
- Re: https at ietf.org, Douglas Otis, 2013/12/11
- Re: https at ietf.org, Doug Barton, 2013/12/06
Re: Alternative decision process in RTCWeb,
Ted Hardie,
2013/12/01
- Re: Alternative decision process in RTCWeb, Melinda Shore, 2013/12/01
- Re: Alternative decision process in RTCWeb, Ted Hardie, 2013/12/02
- Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Eric Burger, 2013/12/02
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), cb.list6, 2013/12/02
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Mary Barnes, 2013/12/02
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Phillip Hallam-Baker, 2013/12/02
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Eric Burger, 2013/12/02
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Peter Saint-Andre, 2013/12/04
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Gonzalo Camarillo, 2013/12/04
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Richard Barnes, 2013/12/04
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Cullen Jennings (fluffy), 2013/12/06
- Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb), Timothy B. Terriberry, 2013/12/09
- Re: Alternative decision process in RTCWeb, Eric Burger, 2013/12/01
- Re: Alternative decision process in RTCWeb, Scott O. Bradner, 2013/12/01
- Re: Alternative decision process in RTCWeb, Avri Doria, 2013/12/02
- Re: Alternative decision process in RTCWeb, Cullen Jennings (fluffy), 2013/12/02
- Re: Alternative decision process in RTCWeb, Carsten Bormann, 2013/12/02