IETF Discussion

• Thread Index

• Re: Data on internet drafts/year?
  • From: Melinda Shore
• Re: Data on internet drafts/year?
  • From: Eric Burger
• Re: Data on internet drafts/year?
  • From: Fred Baker (fred)
• Data on internet drafts/year?
  • From: Melinda Shore
• Re: IETF web site behind CloudFlare
  • From: Linus Nordberg
• RE: Gen-ART Telechat review of draft-ietf-opsec-lla-only-10
  • From: Michael Behringer (mbehring)
• RE: Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Re: Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Kathleen Moriarty
• Re: IETF web site behind CloudFlare
  • From: Julian Reschke
• Re: IETF web site behind CloudFlare
  • From: S Moonesamy
• Re: WG Review: Web-Based Push Notifications (webpush)
  • From: Paul Hoffman
• JOSE -32 and JWT -26 drafts addressing IETF Last Call comments
  • From: Mike Jones
• Re: email standards
  • From: Jari Arkko
• Re: facilitators at ietf@xxxxxxxx
  • From: IETF Chair
• Re: email standards
  • From: Dave Crocker
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Re: email standards
  • From: George Michaelson
• RE: Gen-ART LC review of draft-ietf-jose-json-web-algorithms-31
  • From: Mike Jones
• RE: Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Re: email standards
  • From: Phillip Hallam-Baker
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Phillip Hallam-Baker
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Viktor Dukhovni
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Scott Kitterman
• Re: email standards
  • From: John C Klensin
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: John C Klensin
• Last Call: <draft-ietf-appsawg-authres-ptypes-registry-03.txt> (A Property Types Registry for the Authentication-Results Header Field) to Proposed Standard
  • From: Scott Kitterman
• Re: email standards
  • From: Dave Crocker
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Phillip Hallam-Baker
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Michael Richardson
• NOMCOM 2014 - Call for Nominations
  • From: NomCom Chair 2014
• Re: email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: Randall Gellens
• email standards (was: Re: facilitators at ietf@xxxxxxxx)
  • From: John C Klensin
• Re: facilitators at ietf@xxxxxxxx
  • From: Phillip Hallam-Baker
• facilitators at ietf@xxxxxxxx
  • From: IETF Chair
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Jim Schaad
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Jim Schaad
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Jim Schaad
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: John Bradley
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Jim Schaad
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Jim Schaad
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• BoF proposals for IETF-91 due Friday!
  • From: IETF Chair
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Rich Kulawiec
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Rich Kulawiec
• RE: [jose] Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• RE: Gen-ART LC Review of draft-ietf-avtcore-srtp-aes-gcm-14
  • From: Igoe, Kevin M.
• Re: IETF web site behind CloudFlare
  • From: Ted Lemon
• Re: Gen-ART review of draft-ietf-appsawg-authres-ptypes-registry-03
  • From: Jari Arkko
• Code Sprint in Honolulu
  • From: IETF Chair
• Re: IETF web site behind CloudFlare
  • From: Doug Barton
• Re: IETF web site behind CloudFlare
  • From: Ted Lemon
• Re: IETF web site behind CloudFlare
  • From: Doug Barton
• Re: IETF web site behind CloudFlare
  • From: Stephen Farrell
• Gen-ART review of draft-ietf-appsawg-authres-ptypes-registry-03
  • From: Russ Housley
• Re: Gen-ART LC Review of draft-ietf-avtcore-srtp-aes-gcm-14
  • From: Ben Campbell
• Re: IETF web site behind CloudFlare
  • From: manning bill
• Re: IETF web site behind CloudFlare
  • From: Doug Barton
• Re: IETF web site behind CloudFlare
  • From: John Kristoff
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: S Moonesamy
• Re: IETF web site behind CloudFlare
  • From: Henrik Levkowetz
• Re: IETF web site behind CloudFlare
  • From: Jari Arkko
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Brian E Carpenter
• Re: IETF web site behind CloudFlare
  • From: Mark Andrews
• Re: IETF web site behind CloudFlare
  • From: Mark Andrews
• Re: Gen-ART LC Review of draft-ietf-avtcore-srtp-aes-gcm-14
  • From: Ben Campbell
• Re: IETF web site behind CloudFlare
  • From: David Conrad
• Re: IETF web site behind CloudFlare
  • From: John Kristoff
• Re: IETF web site behind CloudFlare
  • From: Ross Finlayson
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Abdussalam Baryun
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Phillip Hallam-Baker
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Yoav Nir
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Phillip Hallam-Baker
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: IETF web site behind CloudFlare
  • From: David Conrad
• Re: IETF web site behind CloudFlare
  • From: Martin Rex
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Jari Arkko
• Re: what time is the Formal IESG Teleconference WebEx
  • From: John Levine
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Dave Crocker
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Cyrus Daboo
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Loa Andersson
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Stewart Bryant
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Abdussalam Baryun
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Attracting volunteers for leadership roles (Was: Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom)))
  • From: Jari Arkko
• Re: IETF web site behind CloudFlare
  • From: Livingood, Jason
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Patrik Fältström
• Re: IETF web site behind CloudFlare
  • From: Jari Arkko
• Re: IETF web site behind CloudFlare
  • From: Rich Kulawiec
• Re: IETF web site behind CloudFlare
  • From: Linus Nordberg
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Jari Arkko
• Re: IETF web site behind CloudFlare
  • From: Linus Nordberg
• Re: IETF web site behind CloudFlare
  • From: Jari Arkko
• Re: IETF web site behind CloudFlare
  • From: Tom Thorogood
• Re: IETF web site behind CloudFlare
  • From: Rhys Smith
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• Re: IETF web site behind CloudFlare
  • From: Leif Johansson
• Re: IETF web site behind CloudFlare
  • From: Mikael Abrahamsson
• Re: IETF web site behind CloudFlare
  • From: Brian E Carpenter
• Re: IETF web site behind CloudFlare
  • From: Tom Thorogood
• Re: IETF web site behind CloudFlare
  • From: Tom Thorogood
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: IETF web site behind CloudFlare
  • From: Shumon Huque
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Pete Resnick
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Murray S. Kucherawy
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Spencer Dawkins at IETF
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Brian E Carpenter
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Nico Williams
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Joel M. Halpern
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Mary Barnes
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Melinda Shore
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Dave Crocker
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Joel M. Halpern
• Re: IETF web site behind CloudFlare
  • From: Doug Royer
• Re: IETF web site behind CloudFlare
  • From: Yoav Nir
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Doug Barton
• Re: IETF web site behind CloudFlare
  • From: Christopher Morrow
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Mary Barnes
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Doug Barton
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: IETF web site behind CloudFlare
  • From: Rich Kulawiec
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Mary Barnes
• Re: IETF web site behind CloudFlare
  • From: David Conrad
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Doug Barton
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: IETF web site behind CloudFlare
  • From: Paul Wouters
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Dave Crocker
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael Richardson
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Stewart Bryant
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Stewart Bryant
• Re: IETF web site behind CloudFlare
  • From: Linus Nordberg
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Allison Mankin
• Re: IETF web site behind CloudFlare
  • From: David Conrad
• Re: IETF web site behind CloudFlare
  • From: S Moonesamy
• Re: IETF web site behind CloudFlare
  • From: Fred Baker (fred)
• RE: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Ersue, Mehmet (NSN - DE/Munich)
• IETF web site behind CloudFlare
  • From: Linus Nordberg
• RE: Gen-ART LC Review of draft-ietf-avtcore-srtp-aes-gcm-14
  • From: Igoe, Kevin M.
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Bert Wijnen (IETF)
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Stephen Kent
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Olafur Gudmundsson
• Re: Bug reporting/tracker for xml2rfc?
  • From: Henrik Levkowetz
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Melinda Shore
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Michael StJohns
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Mary Barnes
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Brian E Carpenter
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Doug Barton
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Mary Barnes
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Dave Crocker
• Re: Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Brian E Carpenter
• Substantial nomcom procedure updates (Was: Re: Consolidating BCP 10 (Operation of the NomCom))
  • From: Jari Arkko
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Jari Arkko
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John Levine
• Re: [tsvwg] Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
  • From: Robert Sparks
• RE: [tsvwg] Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
  • From: karagian
• RE: Question about Crypto algorithm
  • From: Hosnieh Rafiee
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Michael Richardson
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: David Morris
• Re: gmail users read on...
  • From: George Michaelson
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Dave Crocker
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Michael StJohns
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Dave Crocker
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Hector Santos
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Hector Santos
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Hector Santos
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Scott Kitterman
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Hector Santos
• Re: gmail users read on...
  • From: Hector Santos
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Wei Chuang
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Wei Chuang
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Murray S. Kucherawy
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Murray S. Kucherawy
• Re: Bug reporting/tracker for xml2rfc?
  • From: Michael StJohns
• Re: Bug reporting/tracker for xml2rfc?
  • From: Tony Hansen
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Michael StJohns
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Joel M. Halpern
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Brian E Carpenter
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John C Klensin
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John Levine
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Michael StJohns
• Re: Bug reporting/tracker for xml2rfc?
  • From: Melinda Shore
• Re: Bug reporting/tracker for xml2rfc?
  • From: Michael StJohns
• Bug reporting/tracker for xml2rfc?
  • From: Michael StJohns
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John Levine
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Sabahattin Gucukoglu
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Jari Arkko
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Randy Bush
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Spencer Dawkins
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Spencer Dawkins
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Murray S. Kucherawy
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Tim Wicinski
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Murray S. Kucherawy
• Re: Consolidating BCP 10 (Operation of the NomCom)
  • From: Jari Arkko
• Re: Formal IESG Teleconference WebEx and Dial-in Information
  • From: Pete Resnick
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Murray S. Kucherawy
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Murray S. Kucherawy
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Murray S. Kucherawy
• Re: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Richard Barnes
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Nico Williams
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Doug Barton
• RE: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: MH Michael Hammer (5304)
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Dave Crocker
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Doug Barton
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Wei Chuang
• RE: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: MH Michael Hammer (5304)
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Viktor Dukhovni
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Donald Eastlake
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Theodore Ts'o
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Dave Crocker
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Miles Fidelman
• Re: OpenSource v.s. IETF standards
  • From: Linda Dunbar
• Gen-ART LC Review of draft-ietf-avtcore-srtp-aes-gcm-14
  • From: Ben Campbell
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Doug Barton
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Nico Williams
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John C Klensin
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John Levine
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: Doug Barton
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John C Klensin
• Re: dmarc damage, was gmail users read on... [bozo subtopic]
  • From: John Levine
• Fwd: New Version Notification for draft-bray-privacy-choices-00.txt
  • From: Tim Bray
• Re: gmail users read on... [bozo subtopic]
  • From: Doug Barton
• Re: Interesting problems with using IPv6 - multicast-less Ethernet
  • From: Alexandru Petrescu
• Call for Papers: IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)
  • From: IAB Chair
• Re: Last Call: <draft-ietf-opsec-bgp-security-05.txt> (BGP operations and security) to Best Current Practice
  • From: Jerome Durand (jerduran)
• Re: [Netconf] NETCONF WG Bi-Weekly Virtual Interim Meetings beginning September 8, 2014
  • From: Bert Wijnen (IETF)
• Re: Last Call: <draft-ietf-opsec-bgp-security-05.txt> (BGP operations and security) to Best Current Practice
  • From: Randy Bush
• Re: Last Call: <draft-ietf-opsec-bgp-security-05.txt> (BGP operations and security) to Best Current Practice
  • From: John G. Scudder
• Re: Interesting problems with using IPv6
  • From: Dale W. Carder
• RE: Gen-ART review of draft-ietf-soc-overload-rate-control-09
  • From: NOEL, ERIC C
• Re: Interesting problems with using IPv6
  • From: Masataka Ohta
• Re: Interesting problems with using IPv6
  • From: Ted Lemon
• Re: Interesting problems with using IPv6
  • From: Brian E Carpenter
• Interesting problems with using IPv6
  • From: l.wood
• RE: Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Re: gmail users read on... [bozo subtopic]
  • From: Joe Abley
• Re: gmail users read on... [bozo subtopic]
  • From: Antonio Prado
• Re: gmail users read on... [bozo subtopic]
  • From: Hector Santos
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: ned+ietf
• RE: Gen-ART LC review of draft-ietf-jose-json-web-algorithms-31
  • From: Roni Even
• RE: Gen-ART LC review of draft-ietf-jose-json-web-algorithms-31
  • From: Mike Jones
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: Wietse Venema
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: Wietse Venema
• Secdir review of draft-ietf-jose-json-web-signature-31
  • From: Tero Kivinen
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: John Levine
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: ned+ietf
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: Viktor Dukhovni
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: John R Levine
• Re: Hawaii Block - going, going....
  • From: Warren Kumari
• The Open IETF
  • From: Spencer Dawkins at IETF
• Re: Gen-ART Telechat Review of draft-ietf-forces-model-extension-04
  • From: Jari Arkko
• RE: Hawaii Block - going, going....
  • From: Christer Holmberg
• Consolidating BCP 10 (Operation of the NomCom)
  • From: Murray S. Kucherawy
• Re: RFC Editor Website Revamp SOW for Community Input
  • From: Stephen Farrell
• RFC Editor Automation of Stats and Reports Project SOW for Community Input
  • From: IETF Administrative Director
• RFC Digital Object Identifier SOW for Community Input
  • From: IETF Administrative Director
• RFC Editor Website Revamp SOW for Community Input
  • From: IETF Administrative Director
• RE: Hawaii Block - going, going, gone for Saturday
  • From: Robin Uyeshiro
• Re: Hawaii Block - going, going....
  • From: Brian E Carpenter
• Re: draft discussion lists
  • From: Nico Williams
• Re: draft discussion lists
  • From: Stephen Farrell
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: draft discussion lists
  • From: Dave Crocker
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Melinda Shore
• Re: draft discussion lists
  • From: Melinda Shore
• Re: draft discussion lists
  • From: Nico Williams
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Christopher Morrow
• Re: draft discussion lists
  • From: Melinda Shore
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Melinda Shore
• Re: Protocol Action: 'IKEv2 Fragmentation' to Proposed Standard (draft-ietf-ipsecme-ikev2-fragmentation-10.txt)
  • From: Kathleen Moriarty
• Re: draft discussion lists
  • From: Michael StJohns
• Re: Hawaii Block - going, going....
  • From: Ofer Inbar
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Christopher Morrow
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Brian E Carpenter
• Re: Protocol Action: 'IKEv2 Fragmentation' to Proposed Standard (draft-ietf-ipsecme-ikev2-fragmentation-10.txt)
  • From: Randy Presuhn
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: draft discussion lists
  • From: John C Klensin
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Ray Pelletier
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Stewart Bryant
• RE: Hawaii Block - going, going....
  • From: Christer Holmberg
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Ray Pelletier
• Re: draft discussion lists
  • From: John C Klensin
• Re: Hawaii Block - going, going....
  • From: Stephane Bortzmeyer
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Stephane Bortzmeyer
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Eggert, Lars
• [IETF 91] Hotel fully booked for the week-end?
  • From: Stephane Bortzmeyer
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: joel jaeggli
• Re: draft discussion lists
  • From: Nico Williams
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: draft discussion lists
  • From: Dave Crocker
• Re: draft discussion lists
  • From: Nico Williams
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: draft discussion lists
  • From: Fred Baker (fred)
• Re: SMTP 521 code
  • From: John C Klensin
• Gen-ART Telechat Review of draft-ietf-forces-model-extension-04
  • From: Ben Campbell
• SMTP 521 code
  • From: Viktor Dukhovni
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: John C Klensin
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: Viktor Dukhovni
• Re: [taugh.com-standards] Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: John R Levine
• Re: Gen-ART and OPS-Dir review of draft-ietf-appsawg-nullmx-06
  • From: Viktor Dukhovni
• Re: draft discussion lists
  • From: Donald Eastlake
• Re: draft discussion lists
  • From: Michael Richardson
• Re: draft discussion lists
  • From: John C Klensin
• Re: draft discussion lists
  • From: Andrew Sullivan
• Re: draft discussion lists
  • From: Melinda Shore
• Re: draft discussion lists
  • From: Julian Reschke
• Re: draft discussion lists
  • From: Nico Williams
• Re: draft-dukhovni-opportunistic-security-04
  • From: Nico Williams
• Re: draft discussion lists
  • From: Spencer Dawkins at IETF
• Re: draft discussion lists
  • From: Brian E Carpenter
• Re: draft discussion lists
  • From: Dave Cridland
• Re: draft discussion lists
  • From: Eliot Lear
• Re: draft discussion lists
  • From: Dave Cridland
• Re: The IETF should run an IMAPS server for its lists
  • From: Rich Kulawiec
• Re: draft discussion lists
  • From: manning bill
• Re: draft discussion lists
  • From: Eliot Lear
• draft discussion lists
  • From: Michael StJohns
• Gen-ART LC review of draft-ietf-jose-json-web-algorithms-31
  • From: Roni Even
• Gen-ART LC review for draft-ietf-roll-security-threats-09
  • From: Peter Yee
• Re: The IETF should run an IMAPS server for its lists
  • From: Nico Williams
• Re: The IETF should run an IMAPS server for its lists
  • From: John C Klensin
• Re: Opportunistic Lost (was Re: draft-dukhovni-opportunistic-security-04)
  • From: Theodore Ts'o
• Opportunistic Lost (was Re: draft-dukhovni-opportunistic-security-04)
  • From: Abdussalam Baryun
• Re: The IETF should run an IMAPS server for its lists
  • From: S Moonesamy
• RE: Opportunistic Lost (was Re: draft-dukhovni-opportunistic-security-04)
  • From: l.wood
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: Michael Richardson
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: Michael Richardson
• Re: Opportunistic Lost (was Re: draft-dukhovni-opportunistic-security-04)
  • From: Stephen Farrell
• Opportunistic Lost (was Re: draft-dukhovni-opportunistic-security-04)
  • From: Dave Crocker
• Re: The IETF should run an IMAPS server for its lists
  • From: John C Klensin
• Re: The IETF should run an IMAPS server for its lists
  • From: Phillip Hallam-Baker
• Re: The IETF should run an IMAPS server for its lists
  • From: Russ Housley
• Re: Connecting code (open source and proprietary) with IETF standards
  • From: Abdussalam Baryun
• No meetings on Hawaii in future
  • From: Christer Holmberg
• Re: Is it possible for individuals to avoid being monitored by Government agencies?
  • From: Dave Crocker
• The IETF should run an IMAPS server for its lists
  • From: Nico Williams
• Re: gmail users read on... [bozo subtopic]
  • From: Andrew G. Malis
• Re: Is it possible for individuals to avoid being monitored by Government agencies?
  • From: manning bill
• Re: Is it possible for individuals to avoid being monitored by Government agencies?
  • From: Ted Lemon
• Re: gmail users read on... [bozo subtopic]
  • From: Brian E Carpenter
• Re: gmail users read on... [technical subtopic]
  • From: Brian E Carpenter
• Is it possible for individuals to avoid being monitored by Government agencies?
  • From: Linda Dunbar
• Re: gmail users read on...
  • From: Phillip Hallam-Baker
• NOMCOM 2014 - Call for Nominations
  • From: NomCom Chair 2014
• Re: gmail users read on...
  • From: joel jaeggli
• Re: gmail users read on...
  • From: Ted Faber
• Re: gmail users read on...
  • From: TJ
• Re: gmail users read on...
  • From: Paul Hoffman
• Re: gmail users read on...
  • From: Riccardo Bernardini
• Re: gmail users read on...
  • From: Ross Finlayson
• Re: gmail users read on...
  • From: TJ
• Re: gmail users read on...
  • From: Tim Bray
• Re: gmail users read on...
  • From: Ted Faber
• Re: gmail users read on...
  • From: Ross Finlayson
• RE: gmail users read on...
  • From: l.wood
• Re: gmail users read on...
  • From: Mary Barnes
• Re: gmail users read on...
  • From: Michael Richardson
• Re: gmail users read on...
  • From: Ross Finlayson
• Re: gmail users read on...
  • From: Rich Kulawiec
• Re: gmail users read on...
  • From: Andrew G. Malis
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: Steve Crocker
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: Ralph Droms
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: Ralph Droms
• gmail users read on...
  • From: Brian E Carpenter
• IETF blog post on OpenStand
  • From: IAB Chair
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: SM
• Re: IETF 91 Registration
  • From: Leif Johansson
• Re: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Ben Campbell
• Re: Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: George, Wes
• Re: [jose] Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Kathleen Moriarty
• RE: Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Mike Jones
• Call for Review of draft-iab-smart-object-architecture-04.txt, "Architectural Considerations in Smart Object Networking"
  • From: IAB Chair
• Re: draft-dukhovni-opportunistic-security-04
  • From: Michael Richardson
• Re: Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Jari Arkko
• RE: [tsvwg] Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
  • From: karagian
• Re: draft-dukhovni-opportunistic-security-04
  • From: Paul Wouters
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Jari Arkko
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Chris Grundemann
• Re: draft-dukhovni-opportunistic-security-04
  • From: Stephen Farrell
• RE: draft-dukhovni-opportunistic-security-04
  • From: l.wood
• draft-dukhovni-opportunistic-security-04
  • From: Dave Crocker
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Brian E Carpenter
• Re: Hawaii Block - going, going, gone for Saturday
  • From: Tim Chown
• Re: Hawaii Block - going, going, gone for Saturday
  • From: John Levine
• RE: Hawaii Block - going, going....
  • From: Christer Holmberg
• Re: Hawaii Block - going, going....
  • From: Thomas Clausen
• Re: Hawaii Block - going, going....
  • From: Chris Elliott
• RE: Hawaii Block - going, going....
  • From: Christer Holmberg
• Re: Hawaii Block - going, going....
  • From: joel jaeggli
• Re: Hawaii Block - going, going....
  • From: Dave Crocker
• Re: Hawaii Block - going, going....
  • From: joel jaeggli
• Re: Hawaii Block - going, going....
  • From: Thomas Clausen
• RE: Hawaii Block - going, going....
  • From: Christer Holmberg
• Re: Hawaii Block - going, going....
  • From: Greg Shepherd
• Re: Hawaii Block - going, going....
  • From: Stewart Bryant
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Eric Burger
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Nico Williams
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Brian E Carpenter
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: Jari Arkko
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Peter Gutmann
• Re: Vacation locations
  • From: Michael Richardson
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: John C Klensin
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: Jari Arkko
• RE: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Hosnieh Rafiee
• Re: Hawaii Block - going, going....
  • From: Murray S. Kucherawy
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Ted Hardie
• Re: [saag] Is traffic analysis really a target (was Re: Is opportunistic unauthenticated encryption a waste of time?)
  • From: Henry B (Hank) Hotz, CISSP
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Henry B (Hank) Hotz, CISSP
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Mark Andrews
• Re: Vacation locations
  • From: Lou Berger
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: joel jaeggli
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: joel jaeggli
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Brian E Carpenter
• Gen-ART review of draft-ietf-jose-json-web-signature-31
  • From: Russ Housley
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Dave Crocker
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Michael StJohns
• Re: Is traffic analysis really a target (was Re: [saag] Is opportunistic unauthenticated encryption a waste of time?)
  • From: Eric Burger
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Stephen Farrell
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Viktor Dukhovni
• RE: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Bernard Aboba
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Stephen Farrell
• RE: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Bernard Aboba
• Re: The challenges of survey research (was Re: vacation locations)
  • From: Abdussalam Baryun
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: Ted Lemon
• The challenges of survey research (was Re: vacation locations)
  • From: Dave Crocker
• Re: Vacation locations
  • From: Dave Crocker
• Re: Vacation locations
  • From: Andrew G. Malis
• RE: The ability to automatically upgrade a reference to HTTPS fromHTTP
  • From: Chaitanya D
• Re: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Paul Hoffman
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Kathleen Moriarty
• Re: Vacation locations
  • From: Eliot Lear
• Re: Vacation locations
  • From: Stewart Bryant (stbryant)
• Gen-ART review of draft-ietf-soc-overload-rate-control-09
  • From: Peter Yee
• Re: Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Eliot Lear
• Re: Vacation locations
  • From: Dave Crocker
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Nico Williams
• RE: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Christian Huitema
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Theodore Ts'o
• RE: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Bernard Aboba
• Re: Vacation locations
  • From: Chris Elliott
• RE: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: l.wood
• Re: Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Nico Williams
• Re: Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Viktor Dukhovni
• Re: Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Kathleen Moriarty
• Re: Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Nico Williams
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: John C Klensin
• Re: There should be a design pattern, not patterns.
  • From: Phillip Hallam-Baker
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Kent
• Re: [saag] Adept Encryption: Was: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Kent
• Re: [saag] : Review of: Opportunistic Security -03 preview for comment
  • From: Stephen Kent
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Fwd: The ability to automatically upgrade a reference to HTTPS from HTTP
  • From: Tim Bray
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: Ole Jacobsen
• Re: Vacation locations
  • From: Melinda Shore
• Re: Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: Michael StJohns
• Re: Vacation locations
  • From: Lou Berger
• Vacation locations (was: Re: [Recentattendees] Were You Planning a Vacation Around IETF91 Trip?)
  • From: John C Klensin
• Re: [Recentattendees] IETF 91 - Registration is now open!
  • From: David Conrad
• Re: Hawaii Block - going, going....
  • From: Spencer Dawkins at IETF
• RE: Hawaii Block - going, going....
  • From: Andrew Allen
• RE: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Haleplidis Evangelos
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: Paul Wouters
• Re: [saag] Is opportunistic unauthenticated encryption a waste of time?
  • From: Viktor Dukhovni
• Re: [Recentattendees] IETF 91 - Registration is now open!
  • From: Ted Lemon
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Farrell
• Re: There should be a design pattern, not patterns.
  • From: Tom Thorogood
• Re: Hawaii Block - going, going....
  • From: Lou Berger
• RE: [Recentattendees] IETF 91 - Registration is now open!
  • From: Leaf Yeh
• RE: [saag] Adept Encryption: Was: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: l.wood
• Re: Hawaii Block - going, going....
  • From: Sandra Murphy
• Re: Hawaii Block - going, going....
  • From: Ben Campbell
• Re: Hawaii Block - going, going....
  • From: Ben Campbell
• Re: Hawaii Block - going, going....
  • From: Ben Campbell
• Re: [saag] Adept Encryption: Was: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Nico Williams
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: Viktor Dukhovni
• RE: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: l.wood
• Hawaii Block - going, going....
  • From: Michael StJohns
• Re: [Recentattendees] IETF 91 - Registration is now open!
  • From: Brian E Carpenter
• Gen-art LC review: draft-ietf-tsvwg-rsvp-pcn-09
  • From: Robert Sparks
• Gen-ART Telechat review of draft-ietf-opsec-lla-only-10
  • From: Peter Yee
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Nico Williams
• RE: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Christian Huitema
• Re: [saag] Adept Encryption: Was: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Nico Williams
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Viktor Dukhovni
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Viktor Dukhovni
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Kent
• RE: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Haleplidis Evangelos
• Re: [Gen-art] Genart LC review draft-ietf-paws-protocol-14 (was Re: Second Last Call: <draft-ietf-paws-protocol-14.txt> (Protocol to Access White-Space (PAWS) Databases) to Proposed Standard)
  • From: Jari Arkko
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Phillip Hallam-Baker
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Farrell
• RE: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: l.wood
• Re: There should be a design pattern, not patterns.
  • From: Mark Andrews
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Scott Kitterman
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Dave Crocker
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Nico Williams
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Farrell
• Re: Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Paul Wouters
• Re: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Ben Campbell
• Adept Encryption: Was: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Phillip Hallam-Baker
• RE: There should be a design pattern, not patterns.
  • From: Mike Jones
• Re: Flollow up from Admin Plenary
  • From: George, Wes
• There should be a design pattern, not patterns.
  • From: Phillip Hallam-Baker
• Fwd: Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Farrell
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Stephen Kent
• Re: IETF 91 Registration
  • From: Paul Wouters
• Re: IETF 91 Registration
  • From: Marcia Beaulieu
• IETF 91 Registration
  • From: Yoav Nir
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Eliot Lear
• Re: Flollow up from Admin Plenary
  • From: Yoav Nir
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: t.p.
• Re: Flollow up from Admin Plenary
  • From: Nico Williams
• Re: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Ben Campbell
• Re: Flollow up from Admin Plenary
  • From: Kathleen Moriarty
• Re: Flollow up from Admin Plenary
  • From: Walter Pienciak
• Re: Flollow up from Admin Plenary
  • From: Viktor Dukhovni
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Benjamin Kaduk
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Viktor Dukhovni
• Re: Flollow up from Admin Plenary
  • From: Kathleen Moriarty
• Re: Flollow up from Admin Plenary
  • From: Brian E Carpenter
• Flollow up from Admin Plenary
  • From: Kathleen Moriarty
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Re: Good practices
  • From: Abdussalam Baryun
• Re: Good practices
  • From: John C Klensin
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Kent
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Kent
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Dave Crocker
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Farrell
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Kent
• Re: [DNSOP] Last Call: <draft-ietf-dnsop-child-syncronization-02.txt> (Child To Parent Synchronization in DNS) to Proposed Standard
  • From: Wes Hardaker
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Eliot Lear
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Dave Crocker
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Re: [saag] Review of: Opportunistic Security -03 preview for comment
  • From: Benjamin Kaduk
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt> (Opportunistic Security: some protection most of the time) to Informational RFC
  • From: Benjamin Kaduk
• Re: IETF-91 Question - Hilton Hawaiian village construction and resort fee
  • From: Nico Williams
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Farrell
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Dave Crocker
• Re: IETF-91 Question - Hilton Hawaiian village construction and resort fee
  • From: John C Klensin
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Farrell
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Stephen Kent
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Stephen Kent
• Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt> (Opportunistic Security: some protection most of the time) to Informational RFC
  • From: Stephen Kent
• Re: IETF-91 Question - Hilton Hawaiian village construction and resort fee
  • From: Samuel Weiler
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Viktor Dukhovni
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Nico Williams
• RE: Gen-ART LC Review of draft-ietf-forces-model-extension-03
  • From: Haleplidis Evangelos
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: John Wroclawski
• Re: the ancient reorganisation question, was IETF-91 Question etc
  • From: Thomas Clausen
• Re: [DNSOP] Last Call: <draft-ietf-dnsop-child-syncronization-02.txt> (Child To Parent Synchronization in DNS) to Proposed Standard
  • From: 神明達哉
• Re: [rmcat] Last Call: <draft-ietf-rmcat-cc-requirements-05.txt> (Congestion Control Requirements For RMCAT) to Informational RFC
  • From: Colin Perkins
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Benjamin Kaduk
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Nico Williams
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Paul Wouters
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Paul Wouters
• Re: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Paul Wouters
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Dave Crocker
• Re: [saag] DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Benjamin Kaduk
• Re: DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Phillip Hallam-Baker
• RE: Review of: Opportunistic Security -03 preview for comment
  • From: l.wood
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: Nico Williams
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Nico Williams
• DANE should be more prominent (Re: Review of: Opportunistic Security -03 preview for comment)
  • From: Nico Williams
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Nico Williams
• Re: [saag] : Review of: Opportunistic Security -03 preview for comment
  • From: Benjamin Kaduk
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Nico Williams
• Re: [saag] Protocol Design Pattern (was Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Benjamin Kaduk
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Michael Richardson
• Re: [saag] : Review of: Opportunistic Security -03 preview for comment
  • From: Theodore Ts'o
• RE: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: l.wood
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: Viktor Dukhovni
• RE: Review of: Opportunistic Security -03 preview for comment
  • From: l.wood
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Dave Crocker
• Re: Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Scott Kitterman
• Protocol Design Pattern (was Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt>)
  • From: Dave Crocker
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Stephen Farrell
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Fred Baker (fred)
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Dave Crocker
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Stephen Farrell
• Re: Review of: Opportunistic Security -03 preview for comment
  • From: Dave Crocker
• Re: [saag] Last Call: <draft-dukhovni-opportunistic-security-01.txt> (Opportunistic Security: some protection most of the time) to Informational RFC
  • From: Viktor Dukhovni
• Re: [saag]: Review of: Opportunistic Security -03 preview for comment
  • From: Eliot Lear
• Re: Last Call: <draft-dukhovni-opportunistic-security-01.txt> (Opportunistic Security: some protection most of the time) to Informational RFC
  • From: Stephen Kent