IETF Discussion

• Thread Index

• Re: https at ietf.org
  • From: Douglas Otis
• Re: [Recentattendees] IETF 89 - Registration Now Open!
  • From: Marcia Beaulieu
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• Re: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives
  • From: Martin Thomson
• RE: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives
  • From: l.wood
• Re: [rtcweb] Matthew's Objections: was Re: Straw Poll on Video Codec Alternatives
  • From: Adam Roach
• RE: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Matthew Kaufman (SKYPE)
• RE: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Matthew Kaufman (SKYPE)
• Re: https at ietf.org
  • From: Doug Barton
• 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
  • From: Dale R. Worley
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Alissa Cooper
• RE: gen-ART LC review of draft-ietf-mpls-mldp-hsmp-04
  • From: Lizhong Jin
• nfvcon mailing list
  • From: Songhaibin (A)
• RE: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Brent Kelly
• RE: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Brent Kelly
• Re: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Dave Cridland
• Re: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Dave Crocker
• 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
  • From: Richard Barnes
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: t.p.
• Re: https at ietf.org
  • From: John C Klensin
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Theodore Ts'o
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Jari Arkko
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Phillip Hallam-Baker
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Phillip Hallam-Baker
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Jari Arkko
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Eliot Lear
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Jari Arkko
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Stephen Farrell
• Re: Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Harald Alvestrand
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: t.p.
• Re:Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: t.p.
• Previous Process Proposal, was: Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Magnus Westerlund
• Matthew's Objections: was Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Magnus Westerlund
• 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
  • From: Colin Perkins
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Jari Arkko
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Eliot Lear
• RE: gen-ART LC review of draft-ietf-mpls-mldp-hsmp-04
  • From: Roni Even
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Martin Thomson
• Re: https at ietf.org
  • From: Mark Andrews
• Re: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Martin Thomson
• 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
  • From: Pete Resnick
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• 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
  • From: Cullen Jennings (fluffy)
• RE: [rtcweb] Straw Poll on Video Codec Alternatives
  • From: Matthew Kaufman (SKYPE)
• 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
  • From: Martin Thomson
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Arturo Servin
• 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
  • From: Colin Perkins
• 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
  • From: Martin Thomson
• Re: https at ietf.org
  • From: Doug Barton
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Jari Arkko
• 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
  • From: Cullen Jennings (fluffy)
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Josh Howlett
• 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
  • From: Cullen Jennings (fluffy)
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Stephen Farrell
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Dave Cridland
• RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: l.wood
• Re: Last Call: <draft-ietf-stox-core-07.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling) to Proposed Standard
  • From: Robert Sparks
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Eliot Lear
• Re: Last Call: <draft-ietf-stox-core-07.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling) to Proposed Standard
  • From: Peter Saint-Andre
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Timothy B. Terriberry
• Re: [Stox] Last Call: <draft-ietf-stox-core-07.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling) to Proposed Standard
  • From: Peter Saint-Andre
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Stephen Farrell
• Re: IETF 89 - Registration Now Open!
  • From: Alexa Morris
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Eliot Lear
• Re: [perpass] comments and questions for the group on draft-farrell-perpass-attack-02
  • From: Eliot Lear
• Re: [Stox] Last Call: <draft-ietf-stox-core-07.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling) to Proposed Standard
  • From: Dave Cridland
• Eliot's draft-farrell-perpass-attack thread
  • From: Stephen Farrell
• Re: Reducing Internet Latency Workshop
  • From: Matthew Ford
• Re: Editorial thoughts on draft-farrell-perpass-attack-02
  • From: Stephen Farrell
• Re: [Recentattendees] IETF 89 - Registration Now Open!
  • From: Antoin Verschuren
• RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: l.wood
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stefan Winter
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stefan Winter
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stefan Winter
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• Re: https at ietf.org
  • From: Doug Barton
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: https at ietf.org
  • From: David Conrad
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Bjoern Hoehrmann
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Hannes Tschofenig
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stewart Bryant (stbryant)
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Brian E Carpenter
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Phillip Hallam-Baker
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stephen Farrell
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• gen-ART LC review of draft-ietf-mpls-mldp-hsmp-04
  • From: Roni Even
• Re: [IETF] https at ietf.org
  • From: Michael Richardson
• RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Adrian Farrel
• Gen-ART LC review of draft-allen-dispatch-imei-urn-as-instanceid-12
  • From: Roni Even
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Spencer Dawkins at IETF
• Re: Editorial thoughts on draft-farrell-perpass-attack-02
  • From: SM
• Re: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Gonzalo Camarillo
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Mark Nottingham
• Editorial thoughts on draft-farrell-perpass-attack-02
  • From: Bjoern Hoehrmann
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Scott Brim
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Scott Brim
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Brian E Carpenter
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stephen Farrell
• Re: RTCWeb proposal
  • From: Phillip Hallam-Baker
• Re: [IETF] https at ietf.org
  • From: Warren Kumari
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: t.p.
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: t.p.
• Re: IETF Registration System PCI DSS Compliant
  • From: Bradner, Scott
• IETF Registration System PCI DSS Compliant
  • From: Alexa Morris
• RE: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Eric Gray
• Re: WG Review: Multiple Interfaces (mif)
  • From: Ted Lemon
• Re: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Dave Crocker
• 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
  • From: Bernard Aboba
• Re: RTCWeb proposal
  • From: Harald Alvestrand
• Re: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Harald Alvestrand
• Re: A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Eliot Lear
• Re: RTCWeb proposal
  • From: Cullen Jennings (fluffy)
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Cullen Jennings (fluffy)
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stephen Farrell
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stephen Farrell
• 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
  • From: Colin Perkins
• A few thoughts on processes WAS (Re: Alternative decision process in RTCWeb)
  • From: Gonzalo Camarillo
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stefan Winter
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: t.p.
• Re: https at ietf.org
  • From: Doug Barton
• Re: https at ietf.org
  • From: Doug Barton
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• 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
  • From: Roni Even
• Re: [Geopriv] Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-07.txt> (Location Information Server (LIS) Discovery using IP address and Reverse DNS) to Proposed Standard
  • From: Richard Barnes
• Re: [Recentattendees] IETF 89 - Registration Now Open!
  • From: Olafur Gudmundsson
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Arturo Servin
• Re: RTCWeb proposal
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Wesley Eddy
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Brian E Carpenter
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stephen Farrell
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Wesley Eddy
• 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
  • From: Cullen Jennings (fluffy)
• Re: RTCWeb proposal
  • From: Stephan Wenger
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Arturo Servin
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stephen Farrell
• RE: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Josh Howlett
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stephen Farrell
• Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Josh Howlett
• Re: RTCWeb proposal
  • From: Harald Alvestrand
• Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Stephen Farrell
• Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Josh Howlett
• Re: [Json] Last Call: <draft-ietf-json-rfc4627bis-07.txt> (The JSON Data Interchange Format) to Proposed Standard
  • From: Julian Reschke
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Mark Nottingham
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Hannes Tschofenig
• Re: [perpass] Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Theodore Ts'o
• Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Ted Lemon
• RE: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: Ted Lemon
• Re: perens-perpass-appropriate-response-01 (in plain text)
  • From: =JeffH
• Commnets on draft-farrell-perpass-attack-00 was RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: perens-perpass-appropriate-response-01
  • From: Ted Lemon
• RE: perens-perpass-appropriate-response-01
  • From: l.wood
• Re: Last Call: <draft-trammell-ipfix-tcpcontrolbits-revision-04.txt> (Revision of the tcpControlBits IPFIX Information Element) to Informational RFC
  • From: Scharf, Michael (Michael)
• Re: Last Call: <draft-trammell-ipfix-tcpcontrolbits-revision-04.txt> (Revision of the tcpControlBits IPFIX Information Element) to Informational RFC
  • From: Brian Trammell
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Jari Arkko
• perens-perpass-appropriate-response-01
  • From: Bruce Perens
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: David Singer
• RE: [perpass] perens-perpass-appropriate-response-01
  • From: JOSEFSSON Erik
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Ines Robles
• Re: RTCWeb proposal
  • From: Phillip Hallam-Baker
• Re: RTCWeb proposal
  • From: Stephan Wenger
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: RTCWeb proposal
  • From: Phillip Hallam-Baker
• RTCWeb proposal
  • From: Phillip Hallam-Baker
• Re: 'geonet' BoF
  • From: Alexandru Petrescu
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Stephen Farrell
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Richard Barnes
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: [perpass] perens-perpass-appropriate-response-01
  • From: Martin Millnert
• Re: I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Abdussalam Baryun
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Gonzalo Camarillo
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Jari Arkko
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Peter Saint-Andre
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: SM
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Wesley Eddy
• Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
  • From: Jari Arkko
• Re: Last Call: <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database YANG Module) to Proposed Standard
  • From: SM
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: 0, 1, or many standards and their impact (or not)
  • From: Phillip Hallam-Baker
• RE: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: l.wood
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Hector Santos
• RE: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: Adrian Farrel
• RE: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: Adrian Farrel
• Re: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: Donald Eastlake
• Re: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: Fred Baker (fred)
• Re: Last Call: <draft-ietf-stox-core-07.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Architecture, Addresses, and Error Handling) to Proposed Standard
  • From: Robert Sparks
• Re: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: Bjoern Hoehrmann
• Re: New Non-WG Mailing List: ACTN -- Abstraction and Control of Transport Networks (ACTN)
  • From: James Polk
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Alex Russell
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Nico Williams
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Nico Williams
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: John Cowan
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: John Cowan
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Ashok Malhotra
• I-D Action: draft-moonesamy-ietf-conduct-3184bis-04.txt
  • From: Ines Robles
• 0, 1, or many standards and their impact (or not)
  • From: Eliot Lear
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Jim Gettys
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Ted Lemon
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Harald Alvestrand
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: IETF Meeting Scheduling
  • From: Chaitanya Dhareshwar
• Re: IETF Meeting Scheduling
  • From: Tim Chown
• Re: IETF Meeting Scheduling
  • From: Dave Cridland
• RE: IETF Meeting Scheduling
  • From: l.wood
• Re: IETF Meeting Scheduling
  • From: Randy Bush
• IETF Meeting Scheduling
  • From: Dave Cridland
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Stephan Wenger
• Gen-ART review of draft-ietf-dime-rfc4005bis-14
  • From: Black, David
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Phillip Hallam-Baker
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Ofer Inbar
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Martin Thomson
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Bjoern Hoehrmann
• Re: https at ietf.org
  • From: David Conrad
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Sam Hartman
• Re: Alternative decision process in RTCWeb
  • From: Sam Hartman
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Phillip Hallam-Baker
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Eric Burger
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Dave Crocker
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Jari Arkko
• Re: Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Pete Resnick
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Bjoern Hoehrmann
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Dave Crocker
• Re: Alternative decision process in RTCWeb
  • From: Carsten Bormann
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Mary Barnes
• Re: Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: cb.list6
• Daughter of CODEC (was Re: Alternative decision process in RTCWeb)
  • From: Eric Burger
• Re: Alternative decision process in RTCWeb
  • From: cb.list6
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Tim Berners-Lee
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Alex Russell
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Ron
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Noah Mendelsohn
• Re: Alternative decision process in RTCWeb
  • From: Cullen Jennings (fluffy)
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Mary Barnes
• RE: [rtcweb] Alternative decision process in RTCWeb
  • From: DRAGE, Keith (Keith)
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: John Cowan
• Re: Alternative decision process in RTCWeb
  • From: Avri Doria
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Allen Wirfs-Brock
• Re: Alternative decision process in RTCWeb
  • From: Ted Hardie
• Re: Alternative decision process in RTCWeb
  • From: Paul Hoffman
• Re: Alternative decision process in RTCWeb
  • From: Jari Arkko
• Re: Alternative decision process in RTCWeb
  • From: Joel M. Halpern
• Re: https at ietf.org
  • From: David Conrad
• Re: Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: Alternative decision process in RTCWeb
  • From: Scott O. Bradner
• Re: Alternative decision process in RTCWeb
  • From: Melinda Shore
• Re: Alternative decision process in RTCWeb
  • From: Ted Hardie
• W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
  • From: IAB Chair
• Re: Alternative decision process in RTCWeb
  • From: cb.list6
• Re: https at ietf.org
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Ofer Inbar
• Re: Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: Alternative decision process in RTCWeb
  • From: Melinda Shore
• Re: Alternative decision process in RTCWeb
  • From: Bjoern Hoehrmann
• Re: Alternative decision process in RTCWeb
  • From: Dave Crocker
• Re: Alternative decision process in RTCWeb
  • From: Harald Alvestrand
• Re: Alternative decision process in RTCWeb
  • From: Roger Jørgensen
• Re: https at ietf.org
  • From: Sean Turner
• Gen-ART review of draft-bundesbank-eurosystem-namespace-02
  • From: Black, David
• Re: Alternative decision process in RTCWeb
  • From: Stephan Wenger
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Roberto Peon
• Re: [rtcweb] Alternative decision process in RTCWeb
  • From: Ted Lemon
• Re: Alternative decision process in RTCWeb
  • From: Carsten Bormann
• Re: Alternative decision process in RTCWeb
  • From: Cullen Jennings
• Re: Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• Re: Alternative decision process in RTCWeb
  • From: Phillip Hallam-Baker
• RE: [rtcweb] Alternative decision process in RTCWeb
  • From: Bernard Aboba
• Re: Alternative decision process in RTCWeb
  • From: Ted Lemon
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: SM
• Re: Alternative decision process in RTCWeb
  • From: Michael Richardson
• Re: Alternative decision process in RTCWeb
  • From: Yoav Nir
• Re: Alternative decision process in RTCWeb
  • From: Tim Bray
• Re: Alternative decision process in RTCWeb
  • From: Melinda Shore
• Re: Alternative decision process in RTCWeb
  • From: Ted Lemon
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: Alternative decision process in RTCWeb
  • From: Dave Crocker
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Carsten Bormann
• Re: Alternative decision process in RTCWeb
  • From: Eric Rescorla
• Re: Alternative decision process in RTCWeb
  • From: Sam Hartman
• Re: Alternative decision process in RTCWeb
  • From: Ted Lemon
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: Alternative decision process in RTCWeb
  • From: Eric Rescorla
• Re: Alternative decision process in RTCWeb
  • From: Dave Crocker
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: Alternative decision process in RTCWeb
  • From: Eliot Lear
• Re: Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: Alternative decision process in RTCWeb
  • From: Eric Burger
• Re: Alternative decision process in RTCWeb
  • From: Dave Cridland
• Re: Alternative decision process in RTCWeb
  • From: Eliot Lear
• Alternative decision process in RTCWeb
  • From: Gonzalo Camarillo
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Carsten Bormann
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Joe Hildebrand (jhildebr)
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Phillip Hallam-Baker
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Tim Bray
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Carsten Bormann
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Paul Hoffman
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: Abdussalam Baryun
• Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Tim Bray
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: SM
• Re: The "nomap" Network Identifier Suffix
  • From: David Farmer
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: Jari Arkko
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: Stephen Farrell
• Re: The "nomap" Network Identifier Suffix
  • From: Eric Burger
• Re: The "nomap" Network Identifier Suffix
  • From: Mark Andrews
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: Mary Barnes
• Re: IAB statement on draft-farrell-perpass-attack-00
  • From: SM
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Jari Arkko
• IAB statement on draft-farrell-perpass-attack-00
  • From: IAB Chair
• Re: The "nomap" Network Identifier Suffix
  • From: Ted Lemon
• Re: The "nomap" Network Identifier Suffix
  • From: Dave Cridland
• Re: The "nomap" Network Identifier Suffix
  • From: Eric Burger
• Re: The "nomap" Network Identifier Suffix
  • From: SM
• RE: [Gen-art] Gen-ART LC review of draft-ietf-nfsv4-labreqs-04
  • From: Roni Even
• Re: The "nomap" Network Identifier Suffix
  • From: joel jaeggli
• Re: The "nomap" Network Identifier Suffix
  • From: John Levine
• Re: The "nomap" Network Identifier Suffix
  • From: Richard Barnes
• RE: The "nomap" Network Identifier Suffix
  • From: Christian Huitema
• Re: The "nomap" Network Identifier Suffix
  • From: Mark Nottingham
• Re: The "nomap" Network Identifier Suffix
  • From: Stephen Farrell
• Re: The "nomap" Network Identifier Suffix
  • From: Mark Andrews
• Re: The "nomap" Network Identifier Suffix
  • From: Ted Lemon
• Re: The "nomap" Network Identifier Suffix
  • From: Richard Barnes
• Re: [Roll] Working group chairs
  • From: S Moonesamy
• Re: The "nomap" Network Identifier Suffix
  • From: Eric Burger
• Re: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: John Curran
• RE: WG Review: Extensible Provisioning Protocol Extensions (eppext)
  • From: Hollenbeck, Scott
• Re: https at ietf.org
  • From: David Conrad
• Re: https at ietf.org
  • From: Joe Abley
• Re: https at ietf.org
  • From: Randy Bush
• Re: https at ietf.org
  • From: Randy Bush
• Reconstruct the key
  • From: S Moonesamy
• Re: Comments Requested on Candidates for ICANN Technical Liaison Group
  • From: IAB Chair
• Re: https at ietf.org
  • From: Michael Richardson
• Coercion
  • From: S Moonesamy
• Re: https at ietf.org
  • From: Ted Lemon
• The "nomap" Network Identifier Suffix
  • From: Bjoern Hoehrmann
• Re: https at ietf.org
  • From: John R Levine
• Re: https at ietf.org
  • From: David Conrad
• Re: WG Review: Extensible Provisioning Protocol Extensions (eppext)
  • From: John Levine
• Re: WG Review: Extensible Provisioning Protocol Extensions (eppext)
  • From: SM
• Re: https at ietf.org
  • From: John Levine
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: David Conrad
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: David Conrad
• Re: London
  • From: Carsten Bormann
• Re: [Json] BOMs
  • From: Matt Miller (mamille2)
• Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Matt Miller (mamille2)
• Re: London
  • From: Eric Burger
• Re: https at ietf.org
  • From: Joe Abley
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: Joe Abley
• Re: https at ietf.org
  • From: Eric Burger
• Feature Request for IPR listings/system
  • From: TSG - personal
• Re: London
  • From: Ben Laurie
• London
  • From: Gordon Lennox
• Comments Requested on Candidates for ICANN Technical Liaison Group
  • From: Russ Housley
• Re: IPv6 deployment . . . Geoff Huston's 2011 presentation
  • From: Robin Whittle
• Re: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ted Lemon
• Re: [IETF] Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Phillip Hallam-Baker
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: SM
• Re: [IETF] Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Warren Kumari
• Re: [IETF] Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: cb.list6
• Re: [IETF] Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ralph Droms
• Re: [IETF] Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Warren Kumari
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ted Lemon
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ted Lemon
• Re: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ross Finlayson
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Re: Last Call: <draft-ietf-jose-use-cases-05.txt> (Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)) to Informational RFC
  • From: Benjamin Kaduk
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Phillip Hallam-Baker
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: S Moonesamy
• Re: [Json] BOMs
  • From: Bjoern Hoehrmann
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Richard Barnes
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John C Klensin
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: SM
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ted Lemon
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John Levine
• Re: [Json] BOMs
  • From: Nico Williams
• Re: [Json] BOMs
  • From: John Cowan
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Noel Chiappa
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Ted Lemon
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: S Moonesamy
• Re: [Tools-discuss] Service downtime for xml.resource.org
  • From: Henrik Levkowetz
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Phillip Hallam-Baker
• Re: Service downtime for xml.resource.org
  • From: Henrik Levkowetz
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John C Klensin
• Re: Service downtime for xml.resource.org
  • From: Henrik Levkowetz
• Service downtime for xml.resource.org
  • From: Henrik Levkowetz
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: SM
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: joel jaeggli
• IPv6 deployment [was Re: Recent Internet governance events]
  • From: SM
• RE: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: Michel Py
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John Curran
• Re: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: [IETF] IPv6 deployment [was Re: Recent Internet governance events]
  • From: Robin Whittle
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Spontaneous Procedure Invention ( was Re: Procedural Changes through side-effect)
  • From: Dave Crocker
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Randy Bush
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John Levine
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Randy Bush
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: John C Klensin
• Re: IPv6 deployment [was Re: Recent Internet governance events]
  • From: Chris Grundemann
• IPv6 deployment [was Re: Recent Internet governance events]
  • From: Brian E Carpenter
• Re: www.1net.org (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Jorge Amodio
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Phillip Hallam-Baker
• Re: [Json] BOMs
  • From: Bjoern Hoehrmann
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: SM
• Re: www.1net.org (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• www.1net.org (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: Procedural Changes through side-effect (was: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic)
  • From: S Moonesamy
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Phillip Hallam-Baker
• Re: [Json] BOMs
  • From: Bjoern Hoehrmann
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: [Json] BOMs
  • From: Allen Wirfs-Brock
• Re: [Json] BOMs
  • From: Allen Wirfs-Brock
• Re: [Json] BOMs
  • From: Henri Sivonen
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: SM
• Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Jari Arkko
• Re: Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: Jorge Amodio
• Procedural Changes through side-effect (was: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic)
  • From: John C Klensin
• Recent Internet governance events (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: [Gen-art] Gen-ART LC review of draft-ietf-nfsv4-labreqs-04
  • From: Jari Arkko
• Re: [Gen-art] Gen-ART review of draft-ietf-appsawg-malformed-mail-10
  • From: Jari Arkko
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Murray S. Kucherawy
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Ted Lemon
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John Levine
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Bradner, Scott
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Bradner, Scott
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Hector Santos
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: John C Klensin
• Re: What "1net" is... (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: John C Klensin
• Re: What "1net" is... (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: SM
• Re: What "1net" is... (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Ted Lemon
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Eliot Lear
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Brian E Carpenter
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Ted Lemon
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Ted Lemon
• Re: What "1net" is... (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: SM
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Eliot Lear
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Bob Braden
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Alexey Melnikov
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Ted Lemon
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Dave Crocker
• Re: FUSSP inherent barriers (was Re: Project Proposal: DNS ...)
  • From: Ted Lemon
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John C Klensin
• Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
  • From: Barry Leiba
• FUSSP inherent barriers (was Re: Project Proposal: DNS ...)
  • From: Dave Crocker
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Ted Lemon
• Re: [Json] BOMs
  • From: Tatu Saloranta
• Consensus re: top-level value restriction (Re: [Json] JSON: remove gap between Ecma-404 and IETF draft)
  • From: Nico Williams
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Dave Crocker
• Re: [Json] BOMs
  • From: Joe Hildebrand (jhildebr)
• Re: [Json] BOMs
  • From: Henry S. Thompson
• Re: [Json] BOMs
  • From: Henry S. Thompson
• Re: [Json] BOMs
  • From: "Martin J. Dürst"
• Re: BOMs
  • From: Chris Lilley
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Christopher LILJENSTOLPE
• Re: [Json] BOMs
  • From: Allen Wirfs-Brock
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Ted Lemon
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John R. Levine
• Re: severely UNCHECKED Global Multistakeholder Meeting on the Future of Internet Governance
  • From: John Levine
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Phillip Hallam-Baker
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: ned+ietf
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John C Klensin
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Michael Richardson
• What "1net" is... (was: Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance)
  • From: John Curran
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Hector Santos
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS {dkim-fail}
  • From: ned+ietf
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jari Arkko
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Mark Andrews
• Re: [eX-bulk] : Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John R Levine
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Bob Hinden
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John R Levine
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Ted Lemon
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Hector Santos
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Dave Crocker
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Ted Lemon
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Randy Bush
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: Mark Andrews
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Hannes Tschofenig
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Brian E Carpenter
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jari Arkko
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Phillip Hallam-Baker
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: John Levine
• Re: Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: ned+ietf
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• RE: Last Call: <draft-ietf-bfd-on-lags-02.txt>
  • From: Bhatia, Manav (Manav)
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: jonne.soininen
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Crocker
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Russ Housley
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Russ Housley
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Phillip Hallam-Baker
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Russ Housley
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: [Json] BOMs
  • From: Bjoern Hoehrmann
• Re: BOMs
  • From: "Martin J. Dürst"
• Re: BOMs
  • From: Bjoern Hoehrmann
• Re: BOMs
  • From: t.p.
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: IETF Server Upgrade and Transition Complete (Except RT)
  • From: Alexa Morris
• Re: IETF Server Upgrade and Transition Complete (Except RT)
  • From: SM
• Re: BOMs
  • From: "Martin J. Dürst"
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Crocker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Phillip Hallam-Baker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Phillip Hallam-Baker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Andrew Sullivan
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jaap Akkerhuis
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Randy Bush
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Crocker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Andrew Sullivan
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Scott Kitterman
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Crocker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Phillip Hallam-Baker
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jari Arkko
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Cridland
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Dave Cridland
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Project Proposal: DNS Licensing Look UP - AntiSpam and IP licensing Lookup Additions as text records in DNS
  • From: TSG
• Transparency in the IETF...
  • From: TSG
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Lucy Lynch
• Re: Pervasive surveilance isn't an attack, it is a cancer; mandatory encryption doesn't cure it
  • From: Scott Brim
• Re: [Json] BOMs
  • From: Tatu Saloranta
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Pete Cordell
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: John Cowan
• Re: BOMs
  • From: Phillip Hallam-Baker
• Re: Pervasive surveilance isn't an attack, it is a cancer; mandatory encryption doesn't cure it
  • From: Jari Arkko
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: John Levine
• Re: Pervasive surveilance isn't an attack, it is a cancer; mandatory encryption doesn't cure it
  • From: Scott Brim
• RT (IETF Ticket System) is Operational
  • From: Alexa Morris
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Jorge Amodio
• Re: Global Multistakeholder Meeting on the Future of Internet Governance
  • From: Russ Housley
• Re: ***UNCHECKED*** Global Multistakeholder Meeting on the Future of Internet Governance
  • From: SM
• Re: Pervasive surveilance isn't an attack, it is a cancer; mandatory encryption doesn't cure it
  • From: SM
• Re: Number of CAs (was: Mandatory encryption as part of HTTP2)
  • From: Phillip Hallam-Baker
• IETF Server Upgrade and Transition Complete (Except RT)
  • From: Alexa Morris
• Re: Number of CAs (was: Mandatory encryption as part of HTTP2)
  • From: Phillip Hallam-Baker
• Re: Where at IETF is done: cloud computing, small cells, base station?
  • From: Melinda Shore
• Gen-ART Telechat review of draft-ietf-geopriv-res-gw-lis-discovery-08
  • From: Peter Yee
• Re: es-discuss Digest, Vol 81, Issue 82
  • From: Bjoern Hoehrmann
• Re: Gen-ART LC review of draft-ietf-6man-oversized-header-chain-08
  • From: Peter Yee
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Pete Cordell
• Re: BOMs
  • From: Pete Cordell
• BOMs (Was: Re: [Json] JSON: remove gap between Ecma-404 and IETF draft)
  • From: Pete Cordell
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Julian Reschke
• Re: BOMs
  • From: Henry S. Thompson
• Re: BOMs
  • From: Henry S. Thompson
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: John Cowan
• Re: BOMs
  • From: John Cowan
• Reminder: IETF Server Offline Today During Transition / Upgrade
  • From: Alexa Morris
• RE: Last Call: <draft-ietf-bfd-on-lags-02.txt>
  • From: Adrian Farrel
• Re: Where at IETF is done: cloud computing, small cells, base station?
  • From: SM
• Re: [Json] BOMs (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
  • From: Tim Bray
• RE: Where at IETF is done: cloud computing, small cells, base station?
  • From: Romascanu, Dan (Dan)
• Re: Pervasive surveilance isn't an attack, it is a cancer; mandatory encryption doesn't cure it
  • From: Stephen Farrell
• Re: Where at IETF is done: cloud computing, small cells, base station?
  • From: Alexandru Petrescu
• Re: Where at IETF is done: cloud computing, small cells, base station?
  • From: Alexandru Petrescu
• Re: Where at IETF is done: cloud computing, small cells, base station?
  • From: Alexandru Petrescu
• Re: Number of CAs (was: Mandatory encryption as part of HTTP2)
  • From: Ted Lemon
• Re: BOMs
  • From: Bjoern Hoehrmann