IETF Discussion

• Thread Index

• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Brian E Carpenter
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Abdussalam Baryun
• Re: Hum theatre
  • From: Jorge Amodio
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• How US military base in Hawaii was compromised - Password sharing
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Dave Cridland
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Ines Robles
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• RE: Respecting the IETF rough consensus process
  • From: Adrian Farrel
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Murray S. Kucherawy
• Re: [eX-bulk] : Wayback Machine hardware burnt out
  • From: Livingood, Jason
• Re: remote participation yesterday
  • From: Christopher Morrow
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Brian E Carpenter
• Re: "secure Dropbox clone"
  • From: Phillip Hallam-Baker
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Abdussalam Baryun
• Re: Weekly posting summary for ietf@xxxxxxxx
  • From: Abdussalam Baryun
• Re: https at ietf.org
  • From: Dave Cridland
• RE: Wayback Machine hardware burnt out
  • From: l.wood
• Re: Wayback Machine hardware burnt out
  • From: Alejandro Acosta
• Re: Wayback Machine hardware burnt out
  • From: Vinayak Hegde
• Re: Hum theatre
  • From: Andrew Sullivan
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: https at ietf.org
  • From: Martin Rex
• Re: Piloting a University Outreach Programme
  • From: Medel v6 Ramirez
• Re: Hum theatre
  • From: Dave Crocker
• Re: Wayback Machine hardware burnt out
  • From: Frank Solensky
• Re: [eX-bulk] : Wayback Machine hardware burnt out
  • From: Christopher LILJENSTOLPE
• Re: Hum theatre
  • From: Ted Lemon
• Re: Wayback Machine hardware burnt out
  • From: Noel Chiappa
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: David Farmer
• Wayback Machine hardware burnt out
  • From: Brian E Carpenter
• Re: https at ietf.org
  • From: Pranesh Prakash
• Re: https at ietf.org
  • From: Pranesh Prakash
• Re: https at ietf.org
  • From: Douglas Otis
• Re: https at ietf.org
  • From: Ted Lemon
• Re: Respecting the IETF rough consensus process
  • From: Martin Rex
• Re: https at ietf.org
  • From: Måns Nilsson
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: Martin Rex
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: Martin Rex
• Re: Hum theatre
  • From: Dave Cridland
• Re: https at ietf.org
  • From: Chris Inacio
• Re: https at ietf.org
  • From: David Conrad
• Re: https at ietf.org
  • From: ned+ietf
• Re: Hum theatre
  • From: Pete Resnick
• Re: https at ietf.org
  • From: Noel Chiappa
• Re: Hum theatre
  • From: Klaas Wierenga (kwiereng)
• Re: Hum theatre
  • From: Richard Barnes
• Re: https at ietf.org
  • From: t.p.
• Re: Hum theatre
  • From: Jari Arkko
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Brian E Carpenter
• Re: Hum theatre
  • From: Jari Arkko
• Re: https at ietf.org
  • From: Yoav Nir
• Re: Hum theatre
  • From: Phillip Hallam-Baker
• Re: https at ietf.org
  • From: Tim Bray
• Re: https at ietf.org
  • From: Tim Bray
• Re: Hum theatre
  • From: Pete Resnick
• Re: Hum theatre
  • From: Dave Crocker
• Re: Piloting a University Outreach Programme
  • From: IETF Chair
• Re: https at ietf.org
  • From: Noel Chiappa
• Re: Hum theatre
  • From: Carsten Bormann
• remote participation yesterday
  • From: Jari Arkko
• Re: https at ietf.org
  • From: Chris Inacio
• Re: https at ietf.org
  • From: Dave Cridland
• Re: Piloting a University Outreach Programme
  • From: Medel v6 Ramirez
• Re: https at ietf.org
  • From: Noel Chiappa
• Re: Hum theatre
  • From: Klaas Wierenga (kwiereng)
• Re: [88attendees] IETF 88 - Second Life Ballet: Live Performance
  • From: Xiaohong Deng
• Re: Hum theatre
  • From: Klaas Wierenga (kwiereng)
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: ned+ietf
• Re: Hum theatre
  • From: Scott Brim
• Re: Hum theatre
  • From: Paul Hoffman
• Re: Hum theatre
  • From: Randy Bush
• Re: Hum theatre
  • From: Tim Bray
• Re: Hum theatre
  • From: Bob Hinden
• Re: https at ietf.org
  • From: Arturo Servin
• Re: Hum theatre
  • From: Randy Bush
• Re: https at ietf.org
  • From: David Conrad
• Re: #507 integer value parsing, Re: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Julian Reschke
• Thank you for a great new attendees reception this time!
  • From: Spencer Dawkins at IETF
• Re: Hum theatre
  • From: Scott Brim
• Re: "secure Dropbox clone" (was: Re: [IAB] IETF88 Technical Plenary hums)
  • From: Eggert, Lars
• Re: "secure Dropbox clone" (was: Re: [IAB] IETF88 Technical Plenary hums)
  • From: Vinayak Hegde
• Re: Hum theatre
  • From: Dave Crocker
• Re: Hum theatre
  • From: Arturo Servin
• Re: "secure Dropbox clone"
  • From: Christian de Larrinaga
• Fwd: [IP] Now there's a bug bounty program for the whole Internet
  • From: Eggert, Lars
• "secure Dropbox clone" (was: Re: [IAB] IETF88 Technical Plenary hums)
  • From: Eggert, Lars
• Re: Hum theatre
  • From: Christian de Larrinaga
• Re: https at ietf.org
  • From: Dave Cridland
• Re: https at ietf.org
  • From: t.p.
• Re: Hum theatre
  • From: Richard Barnes
• Re: Hum theatre
  • From: Stefan Winter
• Re: Hum theatre
  • From: Fred Baker (fred)
• Re: Hum theatre
  • From: Fred Baker (fred)
• Re: Hum theatre
  • From: "Martin J. Dürst"
• Re: Hum theatre
  • From: Stefan Winter
• Re: https at ietf.org
  • From: Måns Nilsson
• Re: https at ietf.org
  • From: Måns Nilsson
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Hum theatre
  • From: Pete Resnick
• Re: https at ietf.org
  • From: Carsten Bormann
• Re: Clarifying Russ's hums
  • From: Masataka Ohta
• Re: Hum theatre
  • From: Francis Dupont
• Hum theatre
  • From: Abdussalam Baryun
• Re: Hum theatre
  • From: Ted Lemon
• Re: Hum theatre
  • From: Brian E Carpenter
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: Carsten Bormann
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: Måns Nilsson
• Re: Hum theatre
  • From: Fred Baker (fred)
• Re: Hum theatre
  • From: Ralph Droms
• Re: impeding pervasive monitoring via information dispersal
  • From: Scott Brim
• Re: Hum theatre
  • From: Larry Masinter
• impeding pervasive monitoring via information dispersal
  • From: Yaakov Stein
• Re: Hum theatre
  • From: Jorge Amodio
• 3 weeks left! Call for Nominations: 2014 Applied Networking Research Prize (ANRP)
  • From: Eggert, Lars
• Gen-ART review of draft-ietf-appsawg-malformed-mail-10
  • From: Black, David
• Re: Hum theatre
  • From: Randy Bush
• Re: Hum theatre
  • From: Tim Bray
• Re: Hum theatre
  • From: Phillip Hallam-Baker
• Re: Hum theatre
  • From: Yoav Nir
• Re: 'geonet' BoF one time advertisement
  • From: Meetecho IETF support
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Abdussalam Baryun
• Re: https at ietf.org
  • From: Yoav Nir
• Hum theatre
  • From: Dave Crocker
• 'geonet' BoF one time advertisement
  • From: Alexandru Petrescu
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Gen-ART review of draft-ietf-appsawg-malformed-mail-09
  • From: John Levine
• RE: Gen-ART review of draft-ietf-appsawg-malformed-mail-09
  • From: Black, David
• Re: Gen-ART review of draft-ietf-appsawg-malformed-mail-09
  • From: Barry Leiba
• #507 integer value parsing, Re: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Julian Reschke
• Re: Gen-ART review of draft-ietf-appsawg-malformed-mail-09
  • From: Murray S. Kucherawy
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Arturo Servin
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: https at ietf.org
  • From: Marco Davids (Prive)
• Re: [88attendees] IETF 88 - Second Life Ballet: Live Performance
  • From: Randy Bush
• Re: [88attendees] IETF 88 - Second Life Ballet: Live Performance
  • From: John C Klensin
• Re: [88attendees] IETF 88 - Second Life Ballet: Live Performance
  • From: John C Klensin
• Re: Clarifying Russ's hums
  • From: Roberto Peon
• Re: Clarifying Russ's hums
  • From: John C Klensin
• Re: Clarifying Russ's hums
  • From: Yoav Nir
• Re: Clarifying Russ's hums
  • From: Brian E Carpenter
• Re: Clarifying Russ's hums
  • From: Phillip Hallam-Baker
• Re: Clarifying Russ's hums
  • From: Roberto Peon
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: Arturo Servin
• Re: Clarifying Russ's hums
  • From: Arturo Servin
• Re: Clarifying Russ's hums
  • From: Roberto Peon
• Re: [IAB] IETF88 Technical Plenary hums
  • From: Eliot Lear
• Re: Clarifying Russ's hums
  • From: Scott Brim
• Re: Clarifying Russ's hums
  • From: Brian E Carpenter
• Re: https at ietf.org
  • From: Eric Burger
• Piloting a University Outreach Programme
  • From: Abdussalam Baryun
• Clarifying Russ's hums
  • From: Scott Brim
• IETF88 Technical Plenary hums
  • From: Russ Housley
• Re: Respecting the IETF rough consensus process
  • From: Dave Crocker
• RE: Look who is leading the most important debate affecting democracy
  • From: S Moonesamy
• Re: Respecting the IETF rough consensus process
  • From: Dan Harkins
• Re: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
  • From: Spencer Dawkins at IETF
• Re: Look who is leading the most important debate affecting democracy
  • From: Brian E Carpenter
• Re: Respecting the IETF rough consensus process
  • From: Noel Chiappa
• RE: Look who is leading the most important debate affecting democracy
  • From: Andre Brisson
• RE: Look who is leading the most important debate affecting democracy
  • From: Andre Brisson
• Re: [88all] #IETF88 on Twitter
  • From: Jon Hudson
• Picked up a BlackBerry
  • From: Liubing (Leo)
• Re: https at ietf.org
  • From: MAISONNEUVE, JULIEN (JULIEN)
• RE: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
  • From: Adrian Farrel
• Re: Respecting the IETF rough consensus process
  • From: Melinda Shore
• Re: Respecting the IETF rough consensus process
  • From: Noel Chiappa
• Re: Respecting the IETF rough consensus process
  • From: George Michaelson
• Re: Respecting the IETF rough consensus process
  • From: Melinda Shore
• Re: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
  • From: Brian E Carpenter
• Respecting the IETF rough consensus process
  • From: Dave Crocker
• Re: authentication without https (was Re: https at ietf.org)
  • From: Ted Lemon
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: ned+ietf
• authentication without https (was Re: https at ietf.org)
  • From: Dave Crocker
• Re: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
  • From: Bjoern Hoehrmann
• Re: https at ietf.org
  • From: Ted Lemon
• Re: https at ietf.org
  • From: John C Klensin
• Re: https at ietf.org
  • From: John C Klensin
• Re: https at ietf.org
  • From: Bjoern Hoehrmann
• Re: https at ietf.org
  • From: Thiago Marinello
• Re: https at ietf.org
  • From: Dave Cridland
• Re: https at ietf.org
  • From: Eric Burger
• RE: future of identifiers
  • From: l.wood
• Re: Document Action: 'Terms used in Ruting for Low power And Lossy Networks' to Informational RFC (draft-ietf-roll-terminology-13.txt)
  • From: Glen Zorn
• Re: https at ietf.org
  • From: Måns Nilsson
• thoughts on strengthening the security of the Internet
  • From: IETF Chair
• Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
  • From: S Moonesamy
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Abdussalam Baryun
• Re: future of identifiers
  • From: Fred Baker (fred)
• Re: https at ietf.org
  • From: Yoav Nir
• Re: https at ietf.org
  • From: ned+ietf
• Re: future of identifiers
  • From: Toerless Eckert
• Re: https at ietf.org
  • From: Hector Santos
• Re: https at ietf.org
  • From: Marco Davids (Prive)
• Re: https at ietf.org
  • From: Hector Santos
• Re: https at ietf.org
  • From: Joe Abley
• Re: https at ietf.org
  • From: Tim Bray
• Re: future of identifiers
  • From: Phillip Hallam-Baker
• Re: https at ietf.org
  • From: Dean Willis
• Re: https at ietf.org
  • From: ned+ietf
• Re: https at ietf.org
  • From: Joe Abley
• Re: https at ietf.org
  • From: Paul Wouters
• Re: https at ietf.org
  • From: Eric Burger
• Re: future of identifiers
  • From: Fred Baker (fred)
• Re: future of identifiers
  • From: Phillip Hallam-Baker
• Re: https at ietf.org
  • From: David Morris
• Re: https at ietf.org
  • From: Joe Abley
• https at ietf.org
  • From: Tim Bray
• Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Ben Campbell
• Re: List processing capacity (was Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails)
  • From: Chris Griffiths
• Re: [IETF] Re: time, well clocks
  • From: Warren Kumari
• Re: time, well clocks
  • From: Dave Cridland
• #IETF88 on Twitter
  • From: IETF Chair
• Re: Look who is leading the most important debate affecting democracy
  • From: Harald Alvestrand
• Re: Look who is leading the most important debate affecting democracy
  • From: Roger Jørgensen
• RE: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Larry Masinter
• Piloting a University Outreach Programme
  • From: IETF Chair
• Re: time, well clocks
  • From: Riccardo Bernardini
• Re: Anti-harassment policy and ombudsperson
  • From: Murray S. Kucherawy
• Re: Anti-harassment policy and ombudsperson
  • From: John C Klensin
• Re: Anti-harassment policy and ombudsperson
  • From: Brian E Carpenter
• Re: time, well clocks
  • From: Carsten Bormann
• Re: Look who is leading the most important debate affecting democracy
  • From: Christopher Morrow
• Re: Look who is leading the most important debate affecting democracy
  • From: Noel Chiappa
• Re: Look who is leading the most important debate affecting democracy
  • From: Ted Lemon
• Re: time, well clocks
  • From: Ted Lemon
• Re: time, well clocks
  • From: Christopher Morrow
• Re: Look who is leading the most important debate affecting democracy
  • From: Christopher Morrow
• Re: time, well clocks
  • From: Randy Bush
• Re: time, well clocks
  • From: Murray S. Kucherawy
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Murray S. Kucherawy
• Re: [88attendees] Anti-harassment policy and ombudsperson
  • From: Paul M
• Re: [88attendees] Anti-harassment policy and ombudsperson
  • From: Dan Harkins
• Look who is leading the most important debate affecting democracy
  • From: Andre Brisson
• Re: Anti-harassment policy and ombudsperson
  • From: Murray S. Kucherawy
• Re: List processing capacity (was Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails)
  • From: Dave Crocker
• RE: [88attendees] Anti-harassment policy and ombudsperson
  • From: Black, David
• Re: Anti-harassment policy and ombudsperson
  • From: Dave Crocker
• Re: Anti-harassment policy and ombudsperson
  • From: John C Klensin
• Re: [88attendees] Anti-harassment policy and ombudsperson
  • From: Murray S. Kucherawy
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Martin Rex
• Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Benoit Claise
• Re: [88attendees] Anti-harassment policy and ombudsperson
  • From: Eggert, Lars
• Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Benoit Claise
• Re: Anti-harassment policy and ombudsperson
  • From: Harald Alvestrand
• Re: [88attendees] Anti-harassment policy and ombudsperson
  • From: Alissa Cooper
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Ted Lemon
• Re: Anti-harassment policy and ombudsperson
  • From: ned+ietf
• IETF journal reader survey
  • From: Matthew Ford
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Dave Cridland
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Ted Lemon
• Re: Anti-harassment policy and ombudsperson
  • From: joel jaeggli
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Randy Presuhn
• Re: Anti-harassment policy and ombudsperson
  • From: John C Klensin
• Re: will the IETF-88 technical plenary be recorded for later viewing?
  • From: Dan York
• Re: List processing capacity (was Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails)
  • From: Chris Griffiths
• Re: List processing capacity (was Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails)
  • From: Livingood, Jason
• List processing capacity (was Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails)
  • From: Dave Crocker
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Livingood, Jason
• Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Henry S. Thompson
• Re: Anti-harassment policy and ombudsperson
  • From: Dave Crocker
• Re: Anti-harassment policy and ombudsperson
  • From: Brian E Carpenter
• Re: Anti-harassment policy and ombudsperson
  • From: Theodore Ts'o
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Pete Resnick
• Re: Meetecho IETF recordings? (was: Video of TCMTF BoF)
  • From: S Moonesamy
• Re: Anti-harassment policy and ombudsperson
  • From: John C Klensin
• RE: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Larry Masinter
• Re: Anti-harassment policy and ombudsperson
  • From: Andrew Sullivan
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Peter Saint-Andre
• Re: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Dave Cridland
• RE: Last Call: <C> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Larry Masinter
• Re: Anti-harassment policy and ombudsperson
  • From: Murray S. Kucherawy
• Re: Anti-harassment policy and ombudsperson
  • From: Melinda Shore
• Re: [manet] SmartAmerica Challenge briefing/meeting
  • From: manning bill
• Re: [manet] SmartAmerica Challenge briefing/meeting
  • From: Abdussalam Baryun
• Re: Anti-harassment policy and ombudsperson
  • From: SM
• Re: NOMCOM: Updated Open Office Hours in Vancouver (and feedback info)
  • From: Spencer Dawkins
• Re: Anti-harassment policy and ombudsperson
  • From: Bob Hinden
• Re: Anti-harassment policy and ombudsperson
  • From: IETF Chair
• Re: NOMCOM: Updated Open Office Hours in Vancouver (and feedback info)
  • From: Spencer Dawkins
• Re: Anti-harassment policy and ombudsperson
  • From: Dave Crocker
• Re: Community Feedback: Turning off monthly IETF mailing listpassword reminder emails
  • From: John Levine
• Re: time, well clocks
  • From: Scott Brim
• Re: will the IETF-88 technical plenary be recorded for later viewing?
  • From: Ray Pelletier
• Re: Anti-harassment policy and ombudsperson
  • From: Abdussalam Baryun
• Re: Meetecho IETF recordings? (was: Video of TCMTF BoF)
  • From: joel jaeggli
• will the IETF-88 technical plenary be recorded for later viewing?
  • From: =JeffH
• Meetecho IETF recordings? (was: Video of TCMTF BoF)
  • From: =JeffH
• Re: Anti-harassment policy and ombudsperson
  • From: Melinda Shore
• Re: Anti-harassment policy and ombudsperson
  • From: SM
• RE: time, well clocks
  • From: l.wood
• Re: Anti-harassment policy and ombudsperson
  • From: joel jaeggli
• Re: Anti-harassment policy and ombudsperson
  • From: John C Klensin
• Re: Anti-harassment policy and ombudsperson
  • From: Dave Crocker
• Anti-harassment policy and ombudsperson
  • From: IETF Chair
• Re: [IAOC] Community Feedback: Turning off monthly IETF mailing listpassword reminder emails
  • From: Chris Griffiths
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: David Morris
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Phillip Hallam-Baker
• Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Martin Thomson
• Re: Community Feedback: Turning off monthly IETF mailing listpassword reminder emails
  • From: Paul Wouters
• Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: bizzbyster
• Re: time, well clocks
  • From: Suresh Krishnan
• Re: time, well clocks
  • From: Suresh Krishnan
• Re: time, well clocks
  • From: CJ Aronson
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Sandy Wills
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Rich Kulawiec
• Re: for those with some time
  • From: Tim Bray
• Re: time, well clocks
  • From: Thomas D. Nadeau
• for those with some time
  • From: Randy Bush
• Re: time, well clocks
  • From: Scott Brim
• Re: time, well clocks
  • From: Edwin A. Opare
• time, well clocks
  • From: Randy Bush
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Arturo Servin
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Andrew G. Malis
• Volunteers Needed for ICANN Technical Liaison Group
  • From: IAB Chair
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Hector Santos
• The curse of Apple wasRe: Review of: Characterization of Proposed Standards
  • From: t.p.
• Re: Community Feedback: Turning off monthly IETF mailing listpassword reminder emails
  • From: Bjoern Hoehrmann
• Re: Community Feedback: Turning off monthly IETF mailing listpassword reminder emails
  • From: t.p.
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Riccardo Bernardini
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Carsten Bormann
• Re: Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: John Levine
• Community Feedback: Turning off monthly IETF mailing list password reminder emails
  • From: Chris Griffiths
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Brian E Carpenter
• Re: Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: future of identifiers
  • From: Phillip Hallam-Baker
• Re: Review of: Characterization of Proposed Standards
  • From: Jari Arkko
• Re: Review of: Characterization of Proposed Standards
  • From: Jari Arkko
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: future of identifiers
  • From: Jari Arkko
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Jari Arkko
• Gen-ART review of draft-ietf-appsawg-malformed-mail-09
  • From: Black, David
• Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Paul Aitken
• RE: Review of: Characterization of Proposed Standards
  • From: Larry Masinter
• RE: future of identifiers
  • From: Larry Masinter
• Re: Review of: Characterization of Proposed Standards
  • From: SM
• Re: future of identifiers
  • From: Fred Baker (fred)
• Re: future of identifiers
  • From: Dick Franks
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Review of: Characterization of Proposed Standards
  • From: SM
• Re: Review of: Characterization of Proposed Standards
  • From: Barry Leiba
• Re: Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• Re: Last Call: <draft-leiba-smime-type-registry-01.txt> (Creation of aregistry for smime-type parameter values) to Proposed Standard
  • From: Barry Leiba
• Re: Last Call: <draft-leiba-smime-type-registry-01.txt> (Creation of aregistry for smime-type parameter values) to Proposed Standard
  • From: t.p.
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Ben Campbell
• Re: [perpass] [removed] metrics
  • From: SM
• Re: Review of: Characterization of Proposed Standards
  • From: Olaf Kolkman
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: S Moonesamy
• Re: future of identifiers
  • From: Jari Arkko
• RE: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: l.wood
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: S Moonesamy
• Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: "Martin J. Dürst"
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Mark Nottingham
• Review of: Characterization of Proposed Standards
  • From: Abdussalam Baryun
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Ted Lemon
• Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: S Moonesamy
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: TSG - personal
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Vinayak Hegde
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Vinayak Hegde
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: John Levine
• RE: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Dearlove, Christopher (UK)
• Re: future of identifiers
  • From: Avri Doria
• Re: IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Michael Sweet
• Re: [IETF] Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Warren Kumari
• RE: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Dearlove, Christopher (UK)
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: S Moonesamy
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Andrew Feren
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: joel jaeggli
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Bjoern Hoehrmann
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Cyrus Daboo
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Tony Finch
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: ned+ietf
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Eliot Lear
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Richard Barnes
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Ole Jacobsen
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Dave Cridland
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Randy Bush
• Re: RFC2119 keywords in registration requirements
  • From: ned+ietf
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Scott Brim
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: IAB Chair
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Richard Barnes
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: ned+ietf
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Tim Chown
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Jari Arkko
• deprecation of HTTP header field line folding, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Julian Reschke
• RE: [xrblock] Last Call: <draft-ietf-xrblock-rtcp-xr-qoe-12.txt> (RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric Reporting) to Proposed Standard
  • From: Romascanu, Dan (Dan)
• Re: RFC2119 keywords in registration requirements
  • From: Julian Reschke
• Re: RFC2119 keywords in registration requirements
  • From: Bjoern Hoehrmann
• Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Re: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: "Martin J. Dürst"
• Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Julian Reschke
• Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: "Martin J. Dürst"
• Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Julian Reschke
• Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: S Moonesamy
• Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: S Moonesamy
• Re: obs-date, was: [apps-discuss] APPSDIR review, etc.
  • From: S Moonesamy
• Re: IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: S Moonesamy
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Loa Andersson
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Stephane Bortzmeyer
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Stephane Bortzmeyer
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Ross Finlayson
• Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Carsten Bormann
• IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
  • From: Stephane Bortzmeyer
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Dan Harkins
• APPSDIR review of draft-ietf-httpbis-p7-auth-24
  • From: S Moonesamy
• APPSDIR review of draft-ietf-httpbis-p6-cache-24
  • From: S Moonesamy
• Re: future of identifiers
  • From: Phillip Hallam-Baker
• Re: RFC2119 keywords in registration requirements
  • From: John Levine
• Re: RFC2119 keywords in registration requirements
  • From: Ted Lemon
• Re: RFC2119 keywords in registration requirements
  • From: Ted Lemon
• NOMCOM - Community Feedback and Office Hours
  • From: NomCom Chair 2013
• Re: RFC2119 keywords in registration requirements
  • From: ned+ietf
• Re: future of identifiers
  • From: Jorge Amodio
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Douglas Otis
• Re: future of identifiers
  • From: Brian E Carpenter
• Re: future of identifiers
  • From: Randy Bush
• Re: RFC2119 keywords in registration requirements
  • From: Barry Leiba
• Re: RFC2119 keywords in registration requirements
  • From: Paul Hoffman
• Re: RFC2119 keywords in registration requirements
  • From: Bradner, Scott
• Re: RFC2119 keywords in registration requirements
  • From: Julian Reschke
• Re: RFC2119 keywords in registration requirements
  • From: Bradner, Scott
• Re: RFC2119 keywords in registration requirements
  • From: Julian Reschke
• Re: RFC2119 keywords in registration requirements
  • From: Bradner, Scott
• RFC2119 keywords in registration requirements
  • From: Julian Reschke
• Re: future of identifiers
  • From: Noel Chiappa
• Re: future of identifiers
  • From: Brian E Carpenter
• Re: future of identifiers
  • From: Christian de Larrinaga
• Re: future of identifiers
  • From: manning bill
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Pete Resnick
• Re: future of identifiers
  • From: Patrik Fältström
• Re: future of identifiers
  • From: Eliot Lear
• Re: future of identifiers
  • From: Paul Hoffman
• Re: future of identifiers
  • From: Patrik Fältström
• connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Julian Reschke
• Re: future of identifiers
  • From: manning bill
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Barry Leiba
• #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Julian Reschke
• Information request for Secure WiFi standards
  • From: Howard Tinker
• Re: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Amos Jeffries
• Discussions on Internet Hardening in Vancouver
  • From: IETF Chair
• Re: future of identifiers
  • From: Juliao Braga
• custom byte ranges, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: Julian Reschke
• Re: future of identifiers
  • From: Jorge Amodio
• future of identifiers
  • From: Jari Arkko
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Re: Registration requirements for transfer codings, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: S Moonesamy
• Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: S Moonesamy
• APPSDIR review of draft-ietf-httpbis-p5-range-24
  • From: S Moonesamy
• Re: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: S Moonesamy
• APPSDIR review of draft-ietf-httpbis-p4-conditional-24
  • From: S Moonesamy
• Re: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: John C Klensin
• content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Registration requirements for transfer codings, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Julian Reschke
• Re: Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
  • From: Ralph Droms (rdroms)
• IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
  • From: Julian Reschke
• Re: IGOVUPDATE session
  • From: Avri Doria
• Re: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Re: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: John C Klensin
• obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: Julian Reschke
• Gen-ART LC review of draft-ietf-nfsv4-labreqs-04
  • From: Roni Even
• Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
  • From: Julian Reschke
• Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
  • From: S Moonesamy
• Re: IANA URIS, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: S Moonesamy
• APPSDIR review of draft-ietf-httpbis-p2-semantics-24
  • From: S Moonesamy
• On anonymity.... (was: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx)
  • From: Olaf Kolkman
• RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational RFC
  • From: Adrian Farrel
• IANA URIS, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: Julian Reschke
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Eliot Lear
• Re: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational RFC
  • From: Abdussalam Baryun
• APPSDIR review of draft-ietf-httpbis-p1-messaging-24
  • From: S Moonesamy
• Re: Last calling draft-resnick-on-consensus
  • From: Pete Resnick
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Pete Resnick
• Re: Gen-ART Review of draft-resnick-on-consensus-05
  • From: Pete Resnick
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Pete Resnick
• Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
  • From: Pete Resnick
• RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational RFC
  • From: Adrian Farrel
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: Julian Reschke
• Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
  • From: S Moonesamy
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Jorge Amodio
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: SM
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: Julian Reschke
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Roger Jørgensen
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: David Conrad
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Melinda Shore
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Jorge Amodio
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Jorge Amodio
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: John Levine
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: SM
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: ned+ietf
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: Martin Thomson
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: Barry Leiba
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: Ted Lemon
• IGOVUPDATE session
  • From: IETF Chair
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: Abdussalam Baryun
• Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
  • From: t.p.
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: Cullen Jennings
• Re: [IETF] Re: NOMCOM - Critical shortage of nominees for multiple areas
  • From: John C Klensin
• Re: Gen-ART review of draft-ietf-siprec-architecture-08
  • From: Gonzalo Camarillo
• Re: [IETF] Re: NOMCOM - Critical shortage of nominees for multiple areas
  • From: Thomas Narten
• Re: Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• RE: Review of: Characterization of Proposed Standards
  • From: Moriarty, Kathleen
• Re: [IAB] Comments from the IAB on NIST SP 800-90A Proceeding
  • From: Russ Housley
• Review of: Characterization of Proposed Standards
  • From: Abdussalam Baryun
• Review of: Characterization of Proposed Standards
  • From: Dave Crocker
• Re: Comments from the IAB on NIST SP 800-90A Proceeding
  • From: Hannes Tschofenig
• Re: Comments from the IAB on NIST SP 800-90A Proceeding
  • From: Jari Arkko
• Re: Comments from the IAB on NIST SP 800-90A Proceeding
  • From: Riccardo Bernardini
• Re: Comments from the IAB on NIST SP 800-90A Proceeding
  • From: Abdussalam Baryun
• Gen-ART Telechat review of draft-kolkman-proposed-standards-clarified-04
  • From: Peter Yee
• Re: Internet standardisation remains unilateral
  • From: Randy Presuhn
• Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
  • From: Jari Arkko
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Douglas Otis
• Re: Proposed IETF Anti-Harassment Policy
  • From: Bjoern Hoehrmann
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Dave Crocker
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Randy Bush
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Ted Lemon
• Fwd: Re: Proposed IETF Anti-Harassment Policy
  • From: Harald Alvestrand
• Re: Internet standardisation remains unilateral
  • From: John Day
• RE: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Richard Shockey
• Re: Internet standardisation remains unilateral
  • From: Fred Baker (fred)
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Scott Brim
• Re: Internet standardisation remains unilateral
  • From: Phillip Hallam-Baker
• Re: Sergeant at arms: please deal with [censored]
  • From: Jorge Amodio
• Re: Proposed IETF Anti-Harassment Policy
  • From: Theodore Ts'o
• Re: Proposed IETF Anti-Harassment Policy
  • From: Abdussalam Baryun
• Re: Sergeant at arms: please deal with [censored]
  • From: SM
• RE: Internet standardisation remains unilateral
  • From: Michel Py
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Melinda Shore
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: joel jaeggli
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Masataka Ohta
• Re: Proposed IETF Anti-Harassment Policy
  • From: Scott Brim
• Re: Proposed IETF Anti-Harassment Policy
  • From: Theodore Ts'o
• International enforcement agencies join forces to thwart caller identification spoofing
  • From: Richard Shockey
• Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
  • From: Ben Campbell
• Re: Proposed IETF Anti-Harassment Policy
  • From: Ted Lemon
• RE: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Christian Huitema
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: JORDI PALET MARTINEZ
• RE: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: l.wood
• Re: doubt about WG for e-mail protocol enhancement
  • From: John C Klensin
• Re: doubt about WG for e-mail protocol enhancement
  • From: John Levine
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: John C Klensin
• Re: Proposed IETF Anti-Harassment Policy
  • From: Theodore Ts'o
• doubt about WG for e-mail protocol enhancement
  • From: Noel David Torres Taño
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Ted Lemon
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Ted Lemon
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Thomas Narten
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Randy Bush
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Melinda Shore
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Abdussalam Baryun
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Melinda Shore
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Jari Arkko
• Re: Sergeant at arms: please deal with [censored]
  • From: SM
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Ted Lemon
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Scott Brim
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Brian E Carpenter
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Randy Bush
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: Ted Lemon
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: John C Klensin
• IETF::ISOC (was Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx)
  • From: Dave Crocker
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Melinda Shore
• RIPE and IGF presentations
  • From: Jari Arkko
• Re: Proposed IETF Anti-Harassment Policy
  • From: Cullen Jennings
• Re: Proposed IETF Anti-Harassment Policy
  • From: Cullen Jennings
• Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
  • From: Cullen Jennings
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Randy Bush
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Dave Crocker
• Applications open for ISOC Fellowship to IETF 89 (London)
  • From: Steve Conte
• Re: Separate ADs roles from IESG
  • From: Ted Lemon
• Re: Separate ADs roles from IESG
  • From: Dave Crocker
• Re: Separate ADs roles from IESG
  • From: Stephen Farrell
• Re: question: ISOC Panel at IETF88 in Vancouver?
  • From: Alexandru Petrescu
• Re: Proposed IETF Anti-Harassment Policy
  • From: Melinda Shore
• Re: question: ISOC Panel at IETF88 in Vancouver?
  • From: CJ Aronson
• Re: Proposed IETF Anti-Harassment Policy
  • From: Ted Lemon
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Barry Leiba
• Re: Internet standardisation remains unilateral
  • From: John Day
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Phillip Hallam-Baker
• Re: Internet standardisation remains unilateral
  • From: Phillip Hallam-Baker
• RE: Proposed IETF Anti-Harassment Policy
  • From: l.wood
• Re: Sergeant at arms: please deal with mars.techno.cat@xxxxxxxxx
  • From: Randy Bush
• Re: Proposed IETF Anti-Harassment Policy
  • From: Fred Baker (fred)