Mail Index

• Thread Index

• Remarks on opt-in-09, was Re: Remarks on draft-stjohns-dnssec-sigonly
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Publication request raft-ietf-dnsext-trustupdate-timers-05
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Publication request draft-ietf-dnsext-rollover-requirements-04
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Remarks on draft-stjohns-dnssec-sigonly
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Remarks on draft-stjohns-dnssec-sigonly
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Remarks on draft-stjohns-dnssec-sigonly
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Remarks on draft-stjohns-dnssec-sigonly
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: additions to dnssec-bis-updates-04.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• additions to dnssec-bis-updates-04.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: DNSv2 comment in Re: brain cycles of the WG
  • From: Paul Vixie <paul@vix.com>
• Re: DNSv2 comment in Re: brain cycles of the WG
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSv2 comment in Re: brain cycles of the WG
  • From: Paul Vixie <paul@vix.com>
• DNSv2 comment in Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: SO vs DNSSEC
  • From: Jay Daley <jay@nominet.org.uk>
• Re: brain cycles of the WG
  • From: Jay Daley <jay@nominet.org.uk>
• Re: SO vs DNSSEC
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: SO vs DNSSEC
  • From: Paul Vixie <paul@vix.com>
• Re: SO vs DNSSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Noah's principle
  • From: Paul Vixie <paul@vix.com>
• Re: Noah's principle
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: brain cycles of the WG
  • From: Ben Laurie <ben@algroup.co.uk>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Noah's principle
  • From: Roy Arends <roy@nominet.org.uk>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Danny Mayer <mayer@gis.net>
• Re: 2929bis RRTYPE Allocation for the ENUM Branch Location Record
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• 2929bis RRTYPE Allocation for the ENUM Branch Location Record
  • From: Otmar Lendl <lendl@nic.at>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: Christian Huitema <huitema@windows.microsoft.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: brain cycles of the WG
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• Re: brain cycles of the WG
  • From: Jim Reid <jim@rfc1035.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: Christian Huitema <huitema@windows.microsoft.com>
• I-D ACTION:draft-ietf-dnsext-2929bis-04.txt
  • From: Internet-Drafts@ietf.org
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Ralph Droms <rdroms@cisco.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Ralph Droms <rdroms@cisco.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Ralph Droms <rdroms@cisco.com>
• DNSEXT IETF-67 meeting minutes
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: SO vs DNSSEC
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Wrap-up trustupdate timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Danny Mayer <mayer@gis.net>
• Re: SO vs DNSSEC
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: SO vs DNSSEC
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: brain cycles of the WG
  • From: Florian Weimer <fw@deneb.enyo.de>
• SO vs DNSSEC
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• An argument from a contrarian point of view (was: Pimping DNSSEC)
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: brain cycles of the WG
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: brain cycles of the WG
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: brain cycles of the WG
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: brain cycles of the WG
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: brain cycles of the WG
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• brain cycles of the WG
  • From: Pekka Savola <pekkas@netcore.fi>
• peace
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: DNSSEC - Signature Only vs the MX/A issue.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Robert Story <rstory@sparta.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Robert Story <rstory@sparta.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bmanning@karoshi.com
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Paul Vixie <paul@vix.com>
• RE: Non-terminal-wildcards Re: SRV records considered dubious
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Tony Finch <dot@dotat.at>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Pimping DNSSEC (was Re: DNSSEC - Signature Only vs the MX/A issue.)
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: Back to Ohta's old proposal (Was: DNSSEC - Signature Only vs the MX/A issue.
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Ralph Droms <rdroms@cisco.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Back to Ohta's old proposal (Was: DNSSEC - Signature Only vs the MX/A issue.
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Florian Weimer <fw@deneb.enyo.de>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Rob Austein <sra@isc.org>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Application use of Provable non-existence
  • From: "william(at)elan.net" <william@elan.net>
• I-D ACTION:draft-ietf-dnsext-trustupdate-timers-05.txt
  • From: Internet-Drafts@ietf.org
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: Non-terminal-wildcards Re: SRV records considered dubious
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• I-D ACTION:draft-ietf-dnsext-rollover-requirements-04.txt
  • From: Internet-Drafts@ietf.org
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: Trustworthiness rules
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Trustworthiness rules
  • From: David Blacka <davidb@verisignlabs.com>
• Trustworthiness rules
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Off-tree signatures
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Josh Littlefield <joshl@cisco.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Robert Story <rstory@sparta.com>
• Re: DNSSEC - Off-tree signatures
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Peter Koch <pk@denic.de>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Off-tree signatures
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSSEC - Signature Only vs the MX/A issue.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC - Off-tree signatures
  • From: David Blacka <davidb@verisignlabs.com>
• RE: DNSSEC-lite - thoughts
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Off-tree signatures
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Scott Rose <scottr@nist.gov>
• Re: DNSSEC - Application use of Provable non-existence
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• DNSSEC - Signature Only vs the MX/A issue.
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• DNSSEC - Application use of Provable non-existence
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• DNSSEC - Off-tree signatures
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• DNSSEC - Intermediate Validation - Good or bad idea?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• DNSSEC-lite - thoughts
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: "william(at)elan.net" <william@elan.net>
• Re: Non-terminal-wildcards Re: SRV records considered dubious
  • From: Dave Crocker <dcrocker@bbiw.net>
• Non-terminal-wildcards Re: SRV records considered dubious
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Wrap-up trustupdate timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• DNSEXT WGLC Summary: RFC2929bis
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Wrap-up trustupdate timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Wrap-up trustupdate timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Wrap-up rollover requirements
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• dnsext-relax-gratuitous-tsig
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: DNAME questions
  • From: Klaus Malorny <Klaus.Malorny@knipp.de>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: Peter Koch <pk@denic.de>
• Relaxing Gratuitous TSIG Requirement comments
  • From: Brian Wellington <Brian.Wellington@nominum.com>
• Re: DNAME [4.10]: Synthesized CNAME TTL=0
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSEXT WGLC: RFC2929bis - templates and guidelines
  • From: Sam Weiler <weiler@tislabs.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Peter Koch <pk@DENIC.DE>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Simon Josefsson <jas@extundo.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: New working group document ?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Simon Josefsson <jas@extundo.com>
• Re: New working group document ?
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Peter Koch <pk@DENIC.DE>
• DNSEXT WGLC: RFC2929bis - templates and guidelines
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: NSEC3 and dynamic update issues.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: New working group document ?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: New working group document ?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: New working group document ?
  • From: Peter Koch <pk@DENIC.DE>
• Re: New working group document ?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: New working group document ?
  • From: Roy Arends <roy@nominet.org.uk>
• New working group document ?
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: DNAME [4.9]: Name Compression in RDATA
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNAME [4.8]: DNAME and CIDR Blocks in in-addr.arpa
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNAME [4.2]: DNAME Apex is not Redirected Itself
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• NSEC3 and dynamic update issues.
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Fwd: note the boilerplate change
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• comments on draft-ietf-dnsext-dnssec-bis-updates-04.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: I-D ACTION:draft-eastlake-dnsext-cookies-01.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Paul Vixie <paul@vix.com>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Peter Koch <pk@DENIC.DE>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Peter Koch <pk@denic.de>
• Re: dnssec-bis-updates-04 qtype any DO bit
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• I-D ACTION:draft-ietf-dnsext-nsec3-08.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-dnssec-bis-updates-04.txt
  • From: Internet-Drafts@ietf.org
• DDNS-DHCP RFCs
  • From: Ralph Droms <rdroms@cisco.com>
• RFC 4701 on A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)
  • From: rfc-editor@rfc-editor.org
• IETF-57 draft agenda has been posted
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• RE: I-D ACTION:draft-ietf-dnsext-rfc2539bis-dhk-08.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: I-D ACTION:draft-ietf-dnsext-rfc2536bis-dsa-08.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• I-D ACTION:draft-ietf-dnsext-rfc2539bis-dhk-08.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-rfc2536bis-dsa-08.txt
  • From: Internet-Drafts@ietf.org
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Roy Arends <roy@nominet.org.uk>
• Re: WGLC on trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: comments on trustupdate-timers-04
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Wouter Wijngaards <wouter@nlnetlabs.nl>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Wouter Wijngaards <wouter@nlnetlabs.nl>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: FYI: Fwd: I-D ACTION:draft-stjohns-dnssec-sigonly-00.txt
  • From: Paul Vixie <paul@vix.com>
• Fwd: Last Call: 'DNSSEC Lookaside Validation (DLV)' to Informational RFC (draft-weiler-dnssec-dlv)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: FYI: Fwd: I-D ACTION:draft-stjohns-dnssec-sigonly-00.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• FYI: Fwd: I-D ACTION:draft-stjohns-dnssec-sigonly-00.txt
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Jim Reid <jim@rfc1035.com>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME [4.2]: DNAME Apex is not Redirected Itself
  • From: Wouter Wijngaards <wouter@nlnetlabs.nl>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Wouter Wijngaards <wouter@nlnetlabs.nl>
• Re: DNAME [4.8]: DNAME and CIDR Blocks in in-addr.arpa
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNAME [4.14]: Small Corner Cases
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNAME [4.13]: PTR Records and DNAME
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: "Hilarie Orman" <hilarie@purplestreak.com>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME [4.3]: DNAME is Always Included in Outgoing Packets.
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Robert Story <rstory@tislabs.com>
• Re: DNAME [4.3]: DNAME is Always Included in Outgoing Packets.
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: WGLC on trustudpate-timers
  • From: Sam Weiler <weiler@tislabs.com>
• comments on trustupdate-timers-04
  • From: Lindy Foster <lindy@tislabs.com>
• Re: DNAME update draft
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME update draft
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME [4.2]: DNAME Apex is not Redirected Itself
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME [4.2]: DNAME Apex is not Redirected Itself
  • From: Peter Koch <pk@denic.de>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Peter Koch <pk@denic.de>
• Re: DNAME [4.1]: DNAME as a Delegation Tool
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME update draft
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: DNAME update draft
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: DNAME [4.8]: DNAME and CIDR Blocks in in-addr.arpa
  • From: Peter Koch <pk@denic.de>
• Re: DNAME [4.11]: Wildcarded DNAME
  • From: Peter Koch <pk@denic.de>
• Re: DNAME [4.9]: Name Compression in RDATA
  • From: Peter Koch <pk@denic.de>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Roy Arends <roy@nominet.org.uk>
• DNAME [4.14]: Small Corner Cases
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.13]: PTR Records and DNAME
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.12]: NSEC3 and DNAME
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.11]: Wildcarded DNAME
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.10]: Synthesized CNAME TTL=0
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.9]: Name Compression in RDATA
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.8]: DNAME and CIDR Blocks in in-addr.arpa
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.7]: A DNAME is not a Zone-cut
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.6]: Signaling of DNAME Understanding
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.5]: DNSSEC
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.4]: MX and NS Records Require that the DNAME in their RDATA is Canonical
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.3]: DNAME is Always Included in Outgoing Packets.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.2]: DNAME Apex is not Redirected Itself
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME [4.1]: DNAME as a Delegation Tool
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• DNAME update draft
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: NSEC3 Issue 27: creating a flag octet.
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: bmanning@karoshi.com
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: bmanning@karoshi.com
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: "G. S. Marzot" <giovanni.marzot@sparta.com>
• NSEC3 Issue 27: creating a flag octet.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: bmanning@karoshi.com
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: draft-ietf-dnsext-rollover-requirements-03.txt
  • From: bmanning@karoshi.com
• draft-ietf-dnsext-rollover-requirements-03.txt
  • From: Lindy Foster <lindy@tislabs.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: char sample <charz_work@yahoo.com>
• RE: WGLC on rollover-requirements and trustudpate-timers
  • From: "Griffin, Wesley" <Wes.Griffin@sparta.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: char sample <charz_work@yahoo.com>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: David Conrad <david.conrad@icann.org>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: more ambiguity (was Re: LOC)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: more ambiguity (was Re: LOC)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: more ambiguity (was Re: LOC)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: LOC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: more ambiguity (was Re: LOC)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: more ambiguity (was Re: LOC)
  • From: "william(at)elan.net" <william@elan.net>
• Re: more ambiguity (was Re: LOC)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: LOC
  • From: wayne <wayne@schlitt.net>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• more ambiguity (was Re: LOC)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: LOC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: LOC
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: LOC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: LOC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: LOC
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: LOC
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: LOC
  • From: Dean Anderson <dean@av8.com>
• Re: LOC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: WGLC on rollover-requirements and trustudpate-timers
  • From: Scott Rose <srose@verisignlabs.com>
• Re: humid IPv6 addresses
  • From: Pars Mutaf <pars.mutaf@int-evry.fr>
• Re: WGLC on trustudpate-timers
  • From: "dr. W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: humid IPv6 addresses
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: WGLC on trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: WGLC on trustudpate-timers
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• 2nd NSEC3 workshop draft report
  • From: Scott Rose <srose@verisignlabs.com>
• humid IPv6 addresses
  • From: Pars Mutaf <pars.mutaf@int-evry.fr>
• I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-00.txt
  • From: Internet-Drafts@ietf.org
• Re: WGLC on trustudpate-timers
  • From: Scott Rose <srose@verisignlabs.com>
• WGLC on trustudpate-timers
  • From: "dr. W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• WGLC on rollover-requirements and trustudpate-timers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• I-D ACTION:draft-ietf-dnsext-rollover-requirements-03.txt
  • From: Internet-Drafts@ietf.org
• Re: DNSEXT call for agenda items
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSEXT call for agenda items
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• RFC 4471 on Derivation of DNS Name Predecessor and Successor
  • From: rfc-editor@rfc-editor.org
• Re: DNSEXT WGLC: RFC2929bis
  • From: bmanning@vacation.karoshi.com
• Re: DNSEXT WGLC: RFC2929bis
  • From: Sam Weiler <weiler@tislabs.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Thomas Narten <narten@us.ibm.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Thomas Narten <narten@us.ibm.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: bmanning@vacation.karoshi.com
• Re: DNSEXT WGLC: RFC2929bis
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: DNSEXT WGLC: RFC2929bis
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Sam Weiler <weiler@tislabs.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Thomas Narten <narten@us.ibm.com>
• DNSEXT call for agenda items
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Sam Weiler <weiler@tislabs.com>
• Re: RFC proposal on DNS spoofing prevention
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: nsec3 and update
  • From: David Blacka <davidb@verisignlabs.com>
• Re: BIND and OpenSSL's RSA signature forging issue
  • From: Ben Laurie <ben@algroup.co.uk>
• I-D ACTION:draft-ietf-dnsext-trustupdate-timers-04.txt
  • From: Internet-Drafts@ietf.org
• Re: nsec3 and update
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: BIND and OpenSSL's RSA signature forging issue
  • From: bmanning@vacation.karoshi.com
• Re: nsec3 and update
  • From: Scott Rose <srose@verisignlabs.com>
• Re: [dnsop] Re: [dnssec-deployment] BIND and OpenSSL's RSA signature forging issue
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: BIND and OpenSSL's RSA signature forging issue
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: BIND and OpenSSL's RSA signature forging issue
  • From: Roy Arends <roy@nominet.org.uk>
• Re: BIND and OpenSSL's RSA signature forging issue
  • From: Roy Arends <roy@nominet.org.uk>
• Re: [dnssec-deployment] BIND and OpenSSL's RSA signature forging issue
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• BIND and OpenSSL's RSA signature forging issue
  • From: Ben Laurie <ben@algroup.co.uk>
• nsec3 and update
  • From: Mark Andrews <Mark_Andrews@isc.org>
• NSEC3PARAMS and UPDATE
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: RFC proposal on DNS spoofing prevention
  • From: Scott Rose <srose@verisignlabs.com>
• Re: RFC proposal on DNS spoofing prevention
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: draft-ietf-dnsext-trustupdate-timers-03 - Last Pass
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: leading zeros, odd digit counts in salt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: leading zeros, odd digit counts in salt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: RFC proposal on DNS spoofing prevention
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• RFC 4635 on HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm Identifiers
  • From: rfc-editor@rfc-editor.org
• I-D ACTION:draft-ietf-dnsext-nsec3-07.txt
  • From: Internet-Drafts@ietf.org
• Last Call: 'DNSSEC Opt-In' to Experimental RFC (draft-ietf-dnsext-dnssec-opt-in)
  • From: The IESG <iesg-secretary@ietf.org>
• Last Call: 'DNSSEC Experiments' to Proposed Standard (draft-ietf-dnsext-dnssec-experiments)
  • From: The IESG <iesg-secretary@ietf.org>
• Re: RFC proposal on DNS spoofing prevention
  • From: Robert Story <rstory@sparta.com>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• draft-ietf-dnsext-nsec3-07
  • From: Roy Arends <roy@nominet.org.uk>
• Re: RFC proposal on DNS spoofing prevention
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3, UPDATE and adding/removing a zone cut
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: UPDATE and NSEC3 parameter transitions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: UPDATE and NSEC3 parameter transitions.
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: UPDATE and NSEC3 parameter transitions.
  • From: David Blacka <davidb@verisignlabs.com>
• RE: UPDATE and NSEC3 parameter transitions.
  • From: "Rose, Scott" <srose@verisign.com>
• Re: UPDATE and NSEC3 parameter transitions.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RE: UPDATE and NSEC3 parameter transitions.
  • From: "Rose, Scott" <srose@verisign.com>
• Re: UPDATE and NSEC3 parameter transitions.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• UPDATE and NSEC3 parameter transitions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 9, update
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9, update
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 9, update
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 11, revisited.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Mark Andrews <Mark_Andrews@isc.org>
• NSEC3 Issue 9, update
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 11, revisited.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 11, revisited.
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: NSEC3 Issue 11, revisited.
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: NSEC3 Issue 11, revisited.
  • From: David Blacka <davidb@verisignlabs.com>
• RE: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: NSEC3 Issue 11, revisited.
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Ben Laurie <ben@algroup.co.uk>
• RE: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 19, revisited.
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 19, revisited.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: NSEC3 Issue 11, revisited.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: NSEC3 Issue 11, revisited.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: NSEC3 Issue 11, revisited.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 11, revisited.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: NSEC3 Issue 11, revisited.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 11, revisited.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: NSEC3 Issue 23: dealing with unknown hashes
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 19, revisited.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 11, revisited.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• NSEC3 Issue 23: dealing with unknown hashes
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 19, revisited.
  • From: David Blacka <davidb@verisignlabs.com>
• NSEC3 Issue 11, revisited.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: nsec3 and unknown hash algorithms
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: nsec3 and unknown hash algorithms
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: nsec3 and unknown hash algorithms
  • From: David Blacka <davidb@verisignlabs.com>
• Re: closest provable encloser vs closest encloser
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsec3 and unknown hash algorithms
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: nsec3 and unknown hash algorithms
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• nsec3 and unknown hash algorithms
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: closest provable encloser vs closest encloser
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: closest provable encloser vs closest encloser
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• closest provable encloser vs closest encloser
  • From: Mark Andrews <Mark_Andrews@isc.org>
• I-D ACTION:draft-ietf-dnsext-mdns-47.txt
  • From: Internet-Drafts@ietf.org
• RE: Hashed/name collision (Was Re: Removing the SERVFAIL response on hash collisions.)
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Hashed/name collision (Was Re: Removing the SERVFAIL response on hash collisions.)
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Hashed/name collision (Was Re: Removing the SERVFAIL response on hash collisions.)
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: Hashed/name collision (Was Re: Removing the SERVFAIL response on hash collisions.)
  • From: Eric Rescorla <ekr@networkresonance.com>
• Hashed/name collision (Was Re: Removing the SERVFAIL response on hash collisions.)
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• CLASS, was RE: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-nsec3-06
  • From: Roy Arends <roy@nominet.org.uk>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• draft-ietf-dnsext-nsec3-06
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: updated: Re: RFC proposal on DNS spoofing prevention
  • From: Florian Weimer <fw@deneb.enyo.de>
• updated: Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: David Blacka <davidb@verisignlabs.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: "The Purple Streak, Hilarie Orman" <ho@alum.mit.edu>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Roy Arends <roy@nominet.org.uk>
• Re: 11.3. NSEC-to-NSEC3 transition Considerations
  • From: David Blacka <davidb@verisignlabs.com>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: Alex Bligh <alex@alex.org.uk>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Alex Bligh <alex@alex.org.uk>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Paul Vixie <paul@vix.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: David Blacka <davidb@verisignlabs.com>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: "Larson, Matt" <mlarson@verisign.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Removing the SERVFAIL response on hash collisions.
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Rob Austein <sra@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Matt Larson <mlarson@verisign.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• 11.3. NSEC-to-NSEC3 transition Considerations
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Removing the SERVFAIL response on hash collisions.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Namedroppers moderation announcement
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• draft-ietf-dnsext-trustupdate-timers-03 - Last Pass
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: OASIS and new RR types
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: DNSEXT WGLC: RFC2929bis
  • From: bmanning@vacation.karoshi.com
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Namedroppers moderation announcement
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: OASIS and new RR types
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: OASIS and new RR types
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: OASIS and new RR types
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsec3
  • From: David Blacka <davidb@verisignlabs.com>
• Re: OASIS and new RR types
  • From: Julian Mehnle <julian@mehnle.net>
• Re: nsec3
  • From: Roy Arends <roy@nominet.org.uk>
• nsec3
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: OASIS and new RR types
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: OASIS and new RR types
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: OASIS and new RR types
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: OASIS and new RR types
  • From: Mark Andrews <Mark_Andrews@isc.org>
• DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: RFC proposal on DNS spoofing prevention
  • From: Paul Vixie <paul@vix.com>
• RFC proposal on DNS spoofing prevention
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Minimalist TAK automated rollover procedure in DNS resolver
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: OASIS and new RR types
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: OASIS and new RR types
  • From: David Conrad <david.conrad@icann.org>
• OASIS and new RR types
  • From: "Anders Rundgren" <anders.rundgren@telia.com>
• Re: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• test
  • From: "Roger Yerbanga" <roger.yerbanga@afribonemali.net>
• Re: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• RE: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• RE: a suggestion for super-wildcards
  • From: "william(at)elan.net" <william@elan.net>
• RE: a suggestion for super-wildcards
  • From: "william(at)elan.net" <william@elan.net>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: a suggestion for super-wildcards
  • From: "william(at)elan.net" <william@elan.net>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: a suggestion for super-wildcards
  • From: "william(at)elan.net" <william@elan.net>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• DNSEXT66 minutes
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: a suggestion for super-wildcards
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• Bad handling of DNS responses over TCP.
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Måns Nilsson <mansaxel@sunet.se>
• Re: timers draft and parent DS records
  • From: Robert Story <rstory@sparta.com>
• Re: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• superwildcards poc code.
  • From: Roy Arends <roy@nominet.org.uk>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Comments on dr
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: timers draft and parent DS records
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Comments on dr
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Doug Barton <dougb@dougbarton.us>
• Re: a suggestion for super-wildcards
  • From: Doug Barton <dougb@dougbarton.us>
• RE: a suggestion for super-wildcards
  • From: "william(at)elan.net" <william@elan.net>
• Re: a suggestion for super-wildcards
  • From: David Blacka <davidb@verisignlabs.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Doug Barton <dougb@dougbarton.us>
• Re: Comments on dr
  • From: Eric Rescorla <ekr@networkresonance.com>
• Comments on dr
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: timers draft and parent DS records
  • From: Robert Story <rstory@sparta.com>
• Re: DNS zone file format (Was: a suggestion for super-wildcards
  • From: bert hubert <bert.hubert@netherlabs.nl>
• DNS zone file format (Was: a suggestion for super-wildcards
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: timers draft and parent DS records
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: timers draft and parent DS records
  • From: Robert Story <rstory@sparta.com>
• Re: timers draft and parent DS records
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: a suggestion for super-wildcards
  • From: Douglas Otis <dotis@mail-abuse.org>
• timers draft and parent DS records
  • From: Robert Story <rstory@sparta.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: 3 comments on timers-03
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: a suggestion for super-wildcards
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: a suggestion for super-wildcards
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Notes on DNSSEC key rollover
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• RE: 3 comments on timers-03
  • From: "Scott Rose" <scottr@nist.gov>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Notes on DNSSEC key rollover
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Notes on DNSSEC key rollover
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: a suggestion for super-wildcards
  • From: Julian Mehnle <julian@mehnle.net>
• Re: a suggestion for super-wildcards
  • From: Doug Barton <dougb@dougbarton.us>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Notes on DNSSEC key rollover
  • From: Eric Rescorla <ekr@networkresonance.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: 3 comments on timers-03
  • From: Robert Story <rstory@sparta.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: 3 comments on timers-03
  • From: "Scott Rose" <scottr@nist.gov>
• Re: 3 comments on timers-03
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: 3 comments on timers-03
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: 3 comments on timers-03
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• 3 comments on timers-03
  • From: "Scott Rose" <scottr@nist.gov>
• RE: a suggestion for super-wildcards
  • From: Roy Arends <roy@nominet.org.uk>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: a suggestion for super-wildcards
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: a suggestion for super-wildcards
  • From: Paul Vixie <paul@vix.com>
• pushing the limits of DNS Re: a suggestion for super-wildcards
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: a suggestion for super-wildcards
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: a suggestion for super-wildcards
  • From: Roy Arends <roy@nominet.org.uk>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: "dr. W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: a suggestion for super-wildcards
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RFC 4592 on The Role of Wildcards in the Domain Name System
  • From: rfc-editor@rfc-editor.org
• Re: DNSEXT WGLC: RFC2929bis
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• a suggestion for super-wildcards
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: [ietf-dkim] The URL to my paper describing the DKIM policy options
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: "Stuart E. Schechter" <ses@ll.mit.edu>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: Ben Laurie <ben@algroup.co.uk>
• RE: DNSEXT WGLC: RFC2929bis
  • From: "Scott Rose" <scottr@nist.gov>
• Re: DNSEXT WGLC: RFC2929bis
  • From: Peter Koch <pk@DENIC.DE>
• DNSEXT WGLC: RFC2929bis
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: "Scott Rose" <scottr@nist.gov>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• 2nd NSEC3 workshop, 18-20 September 2006
  • From: Roy Arends <roy@nominet.org.uk>
• I-D ACTION:draft-ietf-dnsext-trustupdate-timers-03.txt
  • From: Internet-Drafts@ietf.org
• RE: New DSA key sizes RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: New DSA key sizes RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Key Rollover: proposed way forward
  • From: Roy Arends <roy@nominet.org.uk>
• RE: New DSA key sizes RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: comments on rollover-requirements-02
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: clarification...Re: Key Rollover: proposed way forward
  • From: "Howard J. Eland" <heland@afilias.info>
• Re: Key Rollover: proposed way forward
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• RE: clarification...Re: Key Rollover: proposed way forward
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Key Rollover: proposed way forward
  • From: bmanning@vacation.karoshi.com
• Re: Key Rollover: proposed way forward
  • From: Paul Vixie <paul@vix.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Key Rollover: proposed way forward
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Key Rollover: proposed way forward
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: Key Rollover: proposed way forward
  • From: albertof_mtzherrera@itesm.mx
• Re: Key Rollover: proposed way forward
  • From: Gustavo Lozano <glozano@nic.mx>
• Re: clarification...Re: Key Rollover: proposed way forward
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Key Rollover: proposed way forward
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Key Rollover: proposed way forward
  • From: Rob Austein <sra@isc.org>
• Key Rollover: proposed way forward
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• DNSEXT WGLC Summary: RFC2536bis and RFC2539bis
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• DNSEXT action items from IETF-66 meeting
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: comments on rollover-requirements-02
  • From: Robert Story <rstory@sparta.com>
• Re: Do any DNSEXT participants care about TAK rollover security?
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• comments on rollover-requirements-02
  • From: Wes Hardaker <hardaker@tislabs.com>
• RE: Do any DNSEXT participants care about TAK rollover security?
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: Sam Weiler <weiler@tislabs.com>
• Draft: updated milestones
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: [nsec3-testing] NSEC3 Meeting at IETF 66
  • From: <geoff@nominet.org.uk>
• Re: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: Peter Koch <pk@DENIC.DE>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Clarifications about status of TAKREM proposal for automated TAK rollover
  • From: bmanning@vacation.karoshi.com
• RE: Advance request for opt-in and experiments
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Dean Anderson <dean@av8.com>
• Clarifications about status of TAKREM proposal for automated TAK rollover
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Do any DNSEXT participants care about TAK rollover security?
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• RE: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [Re: Applications/API meeting during IETF-66]
  • From: bmanning@vacation.karoshi.com
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: <geoff@nominet.org.uk>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Recall: Key rollover Work.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Trust anchor rollover review
  • From: bmanning@vacation.karoshi.com
• Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid) (fwd)
  • From: Dean Anderson <dean@av8.com>
• RE: Advance request for opt-in and experiments
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Advance request for opt-in and experiments
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Advance request for opt-in and experiments
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Advance request for opt-in and experiments
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: Recall: Key rollover Work.
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• DNSEXT WGLC: Evaluating DNSSEC Transition Mechanisms
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Advance request for opt-in and experiments
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Advance request for opt-in and experiments
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Recall: Key rollover Work.
  • From: Gustavo Lozano <glozano@nic.mx>
• Re: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Advance request for opt-in and experiments
  • From: David Blacka <davidb@verisignlabs.com>
• DNSEXT-66 Agenda
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Advance request for opt-in and experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Advance request for opt-in and experiments
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Advance request for opt-in and experiments
  • From: Sam Weiler <weiler@tislabs.com>
• Advance request for opt-in and experiments
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Problems in DDNS Client Development for Secure Update
  • From: Badrinath.S@flextronicssoftware.com
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: "Suranjith Ariyapperuma" <priyandika@hotmail.com>
• Re: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: Roy Arends <roy@nominet.org.uk>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: John Kristoff <jtk@ultradns.net>
• RE: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Is keyrollover neccesary? (was Key rollover Work.)
  • From: Paul Vixie <paul@vix.com>
• Re: Is keyrollover neccesary? (was Key rollover Work.)
  • From: Ben Laurie <ben@algroup.co.uk>
• RE: draft-eastlake-dnsext-cookies-00.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Recall: Key rollover Work.
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: John Kristoff <jtk@ultradns.net>
• Re: Recall: Key rollover Work.
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• RE: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: "Scott Rose" <scottr@nist.gov>
• RE: I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: nsid last call (fwd)
  • From: Mark Townsley <townsley@cisco.com>
• Re: You saw this, right?
  • From: Joe Abley <jabley@ca.afilias.info>
• I-D ACTION:draft-ietf-dnsext-2929bis-03.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-dnssec-trans-04.txt
  • From: Internet-Drafts@ietf.org
• Re: nsid last call (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: Recall: Key rollover Work.
  • From: Wesley Griffin <wgriffin@sparta.com>
• Re: nsid last call (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call (fwd)
  • From: Mark Townsley <townsley@cisco.com>
• Re: Is keyrollover neccesary? (was Key rollover Work.)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• An out-of-scope analysis of in-scope TAK rollover proposals
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Recall: Key rollover Work.
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: nsid last call (fwd)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: nsid last call (fwd)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Is keyrollover neccesary? (was Key rollover Work.)
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Is keyrollover neccesary? (was Key rollover Work.)
  • From: Paul Vixie <paul@vix.com>
• Is keyrollover neccesary? (was Key rollover Work.)
  • From: Gustavo Lozano <glozano@nic.mx>
• I-D ACTION:draft-ietf-dnsext-dnssec-bis-updates-03.txt
  • From: Internet-Drafts@ietf.org
• Re: Recall: Key rollover Work.
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: nsid last call (fwd)
  • From: Dean Anderson <dean@av8.com>
• Re: Recall: Key rollover Work.
  • From: Paul Vixie <paul@vix.com>
• Re: Recall: Key rollover Work.
  • From: Sam Weiler <weiler@tislabs.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Your version of M-of-N (was Re: Recall: Key rollover Work.)
  • From: Paul Vixie <paul@vix.com>
• Re: Recall: Key rollover Work.
  • From: Paul Vixie <paul@vix.com>
• Re: Recall: Key rollover Work.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Recall: Key rollover Work.
  • From: Paul Vixie <paul@vix.com>
• Re: nsid last call
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Recall: Key rollover Work.
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Recall: Key rollover Work.
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Recall: Key rollover Work.
  • From: Paul Vixie <paul@vix.com>
• Trust anchor rollover review
  • From: "dr. W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nsid last call
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: Paul Vixie <paul@vix.com>
• Re: Recall: Key rollover Work.
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Recall: Key rollover Work.
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• I-D ACTION:draft-ietf-dnsext-nsec3-06.txt
  • From: Internet-Drafts@ietf.org
• Re: Recall: Key rollover Work.
  • From: Robert Story <rstory@sparta.com>
• Re: Recall: Key rollover Work.
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Recall: Key rollover Work.
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: Recall: Key rollover Work.
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Recall: Key rollover Work.
  • From: bmanning@vacation.karoshi.com
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: David Blacka <davidb@verisignlabs.com>
• Re: nsid last call
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Recall: Key rollover Work.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RE: draft-eastlake-dnsext-cookies-00.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: DNAME question
  • From: Roy Arends <roy@nominet.org.uk>
• Re: DNAME question
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME question
  • From: Roy Arends <roy@nominet.org.uk>
• Re: DNAME question
  • From: Roy Arends <roy@nominet.org.uk>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: DNAME question
  • From: Matt Larson <mlarson@verisign.com>
• RE: You saw this, right? / Cookies/ RE: stopping amplification
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: DNAME question
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: You saw this, right?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: You saw this, right?
  • From: Bill Woodcock <woody@pch.net>
• RE: You saw this, right?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: DNAME question
  • From: Peter Koch <pk@DENIC.DE>
• Re: You saw this, right?
  • From: Bill Woodcock <woody@pch.net>
• Re: Key rollover work, was Re: RFC2672bis DNAME update document
  • From: Gustavo Lozano <glozano@nic.mx>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME questions
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNAME question
  • From: Roy Arends <roy@nominet.org.uk>
• DNAME question
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: draft-eastlake-dnsext-cookies-00.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: draft-eastlake-dnsext-cookies-00.txt
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• draft-eastlake-dnsext-cookies-00.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: NSEC3 - proposed mods to draft
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: Ben Laurie <ben@algroup.co.uk>
• Fwd: Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: David Blacka <davidb@verisignlabs.com>
• Last Call: 'DNS Name Server Identifier Option (NSID)' to Proposed Standard (draft-ietf-dnsext-nsid)
  • From: The IESG <iesg-secretary@ietf.org>
• NSEC3 - proposed mods to draft
  • From: "David A. Wheeler" <dwheeler@dwheeler.com>
• Re: NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: David Blacka <davidb@verisignlabs.com>
• NSEC3 Issue 22: Defining new hash algorithms.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: usage of Server Failure Response code
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D ACTION:draft-ietf-dnsext-dnssec-opt-in-09.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-rollover-requirements-02.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-nsid-02.txt
  • From: Internet-Drafts@ietf.org
• Re: NSEC3 and the future
  • From: Paul Vixie <paul@vix.com>
• NSEC3 and the future
  • From: "David A. Wheeler" <dwheeler@dwheeler.com>
• usage of Server Failure Response code
  • From: "Hyo-Jeong Shin" <shinhj@hana.ne.kr>
• Re: NSEC3 Issue 10: Potential DoS on Servers, and partial resolution: separate queue for not-found
  • From: "David A. Wheeler" <dwheeler@dwheeler.com>
• Re: NSEC3 Issue 10: Potential DoS on Servers,
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 10: Potential DoS on Servers,
  • From: "David A. Wheeler" <dwheeler@dwheeler.com>
• NSEC3 nit
  • From: "David A. Wheeler" <dwheeler@dwheeler.com>
• draft-austein-dnsext-relax-gratuitous-tsig-00.txt
  • From: Rob Austein <sra@isc.org>
• I-D ACTION:draft-ietf-dnsext-signed-nonexistence-requirements-03.txt
  • From: Internet-Drafts@ietf.org
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: nsid last call
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nsid last call
  • From: <geoff@nominet.org.uk>
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME questions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME questions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNAME questions
  • From: bmanning@vacation.karoshi.com
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• Re: DNAME questions
  • From: Matt Larson <mlarson@verisign.com>
• Re: nsid last call
  • From: Matt Larson <mlarson@verisign.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• RE: ISSUE 10: Use of RFC 2119 terminology, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: "Scott Rose" <scottr@nist.gov>
• Re: nsid last call
  • From: jad@nominet.org.uk
• Re: DNAME questions
  • From: Paul Vixie <paul@vix.com>
• DNAME questions
  • From: David Blacka <davidb@verisignlabs.com>
• Re: nsid last call
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: nsid last call
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsid last call
  • From: "william(at)elan.net" <william@elan.net>
• Re: nsid last call
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: nsid last call
  • From: Peter Koch <pk@DENIC.DE>
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsid last call
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nsid last call
  • From: Dean Anderson <dean@av8.com>
• Re: nsid last call
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsid last call
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• A look at draft-...nsid-01.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsid last call
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: nsid last call
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: nsid last call
  • From: Peter Koch <pk@DENIC.DE>
• Key rollover work, was Re: RFC2672bis DNAME update document
  • From: Olaf M.Kolkman <olaf@NLnetLabs.nl>
• Re: nsid last call
  • From: Olaf M.Kolkman <olaf@NLnetLabs.nl>
• Re: RFC2672bis DNAME update document
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: RFC2672bis DNAME update document
  • From: Paul Vixie <paul@vix.com>
• Re: RFC2672bis DNAME update document
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: RFC2672bis DNAME update document
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: RFC2672bis DNAME update document
  • From: David Blacka <davidb@verisignlabs.com>
• ISSUE 10: Use of RFC 2119 terminology, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Issue 9: Relevance to working group charter, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 8: Wording of existing requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 6: draft-moreau-dnsext-tak-req-00 has other useful requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Pending issues for draft-ietf-dnsext-rollover-requirements-01
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• RE: RFC2672bis DNAME update document
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RFC2672bis DNAME update document
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Standardize RSA/SHA256 ?
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: Ben Laurie <ben@algroup.co.uk>
• DNSEXT @ IETF-66 agenda items
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• RE: NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: "Scott Rose" <scottr@nist.gov>
• Re: NSEC3 Issue 17: opt-out for delegation only is not enforcable.
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: David Blacka <davidb@verisignlabs.com>
• RE: NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: "Scott Rose" <scottr@nist.gov>
• RE: NSEC3 Issue 19: NSEC3 processing order
  • From: "Scott Rose" <scottr@nist.gov>
• Re: NSEC3 Issue 19: NSEC3 processing order
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 19: NSEC3 processing order
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: draft-ietf-dnsext-nsid issues to be reviewed
  • From: Dean Anderson <dean@av8.com>
• Re: draft-ietf-dnsext-nsid issues to be reviewed
  • From: Rob Austein <sra@isc.org>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• NSEC3 Issue 21: Signer behavior in case of hash collision.
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 20: Server behavior wrt unknown hash algorithms
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 17: opt-out for delegation only is not enforcable.
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 17: opt-out for delegation only is not enforcable.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• NSEC3 Issue 18: signalling complete NSEC3 chains
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 17: opt-out for delegation only is not enforcable.
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 16: The need for a Hash Length Field.
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 Issue 15: recommend against the use of partially opt-out zones.
  • From: Roy Arends <roy@nominet.org.uk>
• NSEC3 issues
  • From: Roy Arends <roy@nominet.org.uk>
• Re: SOA records in negative responses
  • From: Julian Mehnle <julian@mehnle.net>
• Re: ISSUE 6: Requirements in draft-moreau-dnsext-tak-req-00, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: SOA records in negative responses
  • From: Paul Vixie <paul@vix.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-01.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 6: Requirements in draft-moreau-dnsext-tak-req-00, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: Roy Arends <roy@nominet.org.uk>
• Re: ISSUE 6: Requirements in draft-moreau-dnsext-tak-req-00, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 5: Embedded requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: SOA records in negative responses
  • From: Jim Reid <jim@rfc1035.com>
• Re: SOA records in negative responses
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: SOA records in negative responses
  • From: "Robert Martin-Legene" <rlegene@gmail.com>
• Re: draft-ietf-dnsext-nsid issues to be reviewed
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-nsid issues to be reviewed
  • From: Peter Koch <pk@denic.de>
• Re: draft-ietf-dnsext-nsid issues to be reviewed
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• draft-ietf-dnsext-nsid issues to be reviewed
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Fwd: Internet-Drafts Submission Cutoff Dates for the 66th IETF Meeting in Montreal, Quebec, Canada
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: NSEC3 Dynamic Update (proposed)
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: some issues with NSEC3, based on the workshop last week
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Roy Arends <roy@nominet.org.uk>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: Alex Bligh <alex@alex.org.uk>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Proposed NSEC/NSEC3 transition mechanism
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: comments on rollover requirements
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: some issues with NSEC3, based on the workshop last week
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Standardize RSA/SHA256 ?
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: some issues with NSEC3, based on the workshop last week
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Dynamic Update (proposed)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• some issues with NSEC3, based on the workshop last week
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Proposed NSEC/NSEC3 transition mechanism
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• NSEC3 Dynamic Update (proposed)
  • From: Ben Laurie <ben@algroup.co.uk>
• comments on rollover requirements
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Proposed NSEC/NSEC3 transition mechanism
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: RR Type allocation for infrastructure ENUM BLR/EBL record
  • From: Sam Weiler <weiler@tislabs.com>
• RR Type allocation for infrastructure ENUM BLR/EBL record
  • From: Otmar Lendl <lendl@nic.at>
• SOA records in negative responses
  • From: Roy Arends <roy@nominet.org.uk>
• Re: Standardize RSA/SHA256 ?
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Standardize RSA/SHA256 ?
  • From: Ben Laurie <ben@algroup.co.uk>
• RFC 4509 on Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)
  • From: rfc-editor@rfc-editor.org
• Re: Standardize RSA/SHA256 ?
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Standardize RSA/SHA256 ?
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: Standardize RSA/SHA256 ?
  • From: Mark Feldman <feldman@shinkuro.com>
• Re: Standardize RSA/SHA256 ?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Standardize RSA/SHA256 ?
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Standardize RSA/SHA256 ?
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Standardize RSA/SHA256 ?
  • From: Simon Josefsson <jas@extundo.com>
• Re: Standardize RSA/SHA256 ?
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• RE: Standardize RSA/SHA256 ?
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: Standardize RSA/SHA256 ?
  • From: "Loomis, Rip" <GILBERT.R.LOOMIS@saic.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-01.txt
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-01.txt
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Standardize RSA/SHA256 ?
  • From: Simon Josefsson <jas@extundo.com>
• Re: Standardize RSA/SHA256 ?
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Standardize RSA/SHA256 ?
  • From: Simon Josefsson <jas@extundo.com>
• Re: Standardize RSA/SHA256 ?
  • From: Dean Anderson <dean@av8.com>
• I-D ACTION:draft-ietf-dnsext-nsec3-05.txt
  • From: Internet-Drafts@ietf.org
• Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: Standardize RSA/SHA256 ?
  • From: Simon Josefsson <jas@extundo.com>
• Re: Standardize RSA/SHA256 ?
  • From: "Hilarie Orman" <ho@alum.mit.edu>
• RE: Standardize RSA/SHA256 ?
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• RE: Standardize RSA/SHA256 ?
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: Standardize RSA/SHA256 ?
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Standardize RSA/SHA256 ?
  • From: Wes Hardaker <hardaker@tislabs.com>
• I-D ACTION:draft-ietf-dnsext-rollover-requirements-01.txt
  • From: Internet-Drafts@ietf.org
• Re: Standardize RSA/SHA256 ?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Standardize RSA/SHA256 ?
  • From: Rob Austein <sra@isc.org>
• Re: Standardize RSA/SHA256 ?
  • From: Francis Dupont <Francis.Dupont@point6.net>
• Re: Standardize RSA/SHA256 ?
  • From: Russ Mundy <mundy@sparta.com>
• Standardize RSA/SHA256 ?
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• RE: I-D ACTION:draft-ietf-dnsext-ecc-key-09.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• I-D ACTION:draft-ietf-dnsext-ecc-key-09.txt
  • From: Internet-Drafts@ietf.org
• RFC 4470 on Minimally Covering NSEC Records and DNSSEC On-line Signing
  • From: rfc-editor@rfc-editor.org
• PowerDNS recursor algorithm review
  • From: bert hubert <bert.hubert@netherlabs.nl>
• NSEC3 draft comments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Draft minutes posted
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: Roy Arends <roy@nominet.org.uk>
• Re: proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• proving NAME ERROR (was: Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name)
  • From: Roy Arends <roy@nominet.org.uk>
• I-D ACTION:draft-ietf-dnsext-mdns-46.txt
  • From: Internet-Drafts@ietf.org
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Rob Austein <sra@isc.org>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Rob Austein <sra@isc.org>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Roy Arends <roy@nominet.org.uk>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Rob Austein <sra@isc.org>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Roy Arends <roy@nominet.org.uk>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Roy Arends <roy@nominet.org.uk>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Rob Austein <sra@isc.org>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dns-operations] NXDOMAIN vs NODATA for suffixes of existing name
  • From: paul@vix.com
• isc dlv spec published
  • From: Paul Vixie <paul@vix.com>
• Re: heads up: some practical DNS real life things you might want to know
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: heads up: some practical DNS real life things you might want to know
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: heads up: some practical DNS real life things you might want to know
  • From: Roy Arends <roy@nominet.org.uk>
• heads up: some practical DNS real life things you might want to know
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Nomination of O.Kolkman at the IAB - good news for advances in DNS technology
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: ISSUE 4: Key "lifetimes", was Re: Pending issues for draft-i etf-dnsext-rollover-requirements-00
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• RE: ISSUE 5: Embedded requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Scott Rose" <scottr@nist.gov>
• draft-ietf-dnsext-dnssec-experiments-03.txt
  • From: Sam Weiler <weiler@tislabs.com>
• RE: ISSUE 4: Key "lifetimes", was Re: Pending issues for draft-i etf-dnsext-rollover-requirements-00
  • From: "Loomis, Rip" <GILBERT.R.LOOMIS@saic.com>
• New DSA key sizes RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: Paul Vixie <paul@vix.com>
• Re: should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: Peter Koch <pk@denic.de>
• Re: should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: Tony Finch <dot@dotat.at>
• should a pure recursor know about localhost/1.0.0.127.in-addr.arpa?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D ACTION:draft-ietf-dnsext-dnssec-experiments-03.txt
  • From: Internet-Drafts@ietf.org
• Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: ISSUE 8: Wording in existing requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: bmanning@vacation.karoshi.com
• Re: ISSUE 7: New requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: bmanning@vacation.karoshi.com
• Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Hilarie Orman" <hilarie@purplestreak.com>
• Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: ISSUE 6: Requirements in draft-moreau-dnsext-tak-req-00, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Ben Laurie <ben@algroup.co.uk>
• RE: ISSUE 4: Key "lifetimes", was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: "Scott Rose" <scottr@nist.gov>
• ISSUE 8: Wording in existing requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: ISSUE 7: New requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: ISSUE 4: Key "lifetimes", was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: ISSUE 2: Mandatory to Implement, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Continuing the work on key-rollover
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• ISSUE 7: New requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 6: Requirements in draft-moreau-dnsext-tak-req-00, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 5: Embedded requirements, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 4: Key "lifetimes", was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 3: presentation flaws, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 2: Mandatory to Implement, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• ISSUE 1: IPR, was Re: Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Pending issues for draft-ietf-dnsext-rollover-requirements-00
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: Continuing the work on key-rollover
  • From: bmanning@vacation.karoshi.com
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• RE: Continuing the work on key-rollover
  • From: "Scott Rose" <scottr@nist.gov>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Continuing the work on key-rollover
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: "D. J. Bernstein" <djb@cr.yp.to>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Paul Vixie <paul@vix.com>
• Re: Continuing the work on key-rollover
  • From: Gustavo Lozano <glozano@nic.mx>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Automatic key verification / CERT in DNS / RFC4398 (Was: [Announce] GnuPG 1.4.3 released)
  • From: Paul Vixie <paul@vix.com>
• Re: Automatic key verification / CERT in DNS / RFC4398 (Was: [Announce] GnuPG 1.4.3 released)
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: Automatic key verification / CERT in DNS / RFC4398
  • From: Julian Mehnle <julian@mehnle.net>
• Re: Automatic key verification / CERT in DNS / RFC4398
  • From: Julian Mehnle <julian@mehnle.net>
• Re: Automatic key verification / CERT in DNS / RFC4398 (Was: [Announce] GnuPG 1.4.3 released)
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Continuing the work on key-rollover
  • From: Andrew Newton <andy@hxr.us>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Ketil Froyn <isc_bind@ketil.froyn.name>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: David Blacka <davidb@verisignlabs.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Automatic key verification / CERT in DNS / RFC4398
  • From: Julian Mehnle <julian@mehnle.net>
• Automatic key verification / CERT in DNS / RFC4398 (Was: [Announce] GnuPG 1.4.3 released)
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: the RD bit is troubling me today
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: another question about interpretation of the scriptures: cname chains
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Ketil Froyn <isc_bind@ketil.froyn.name>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Josh Littlefield <joshl@cisco.com>
• Re: another question about interpretation of the scriptures: cname chains
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Alan Barrett <apb@cequrux.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• Re: another question about interpretation of the scriptures: cname chains
  • From: Josh Littlefield <joshl@cisco.com>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Emilio Perea <eperea@walkereng.com>
• another out-of-zone cname question-- anti-aliasing of zone servers?
  • From: Paul Vixie <paul@vix.com>
• another question about interpretation of the scriptures: cname chains
  • From: Paul Vixie <paul@vix.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• RFC 4398 on Storing Certificates in the Domain Name System (DNS)
  • From: rfc-editor@rfc-editor.org
• RE: I-D ACTION:draft-ietf-dnsext-rfc2536bis-dsa-07.txt & draft-ietf-dnsext-rfc2539bis-dhk-07.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Continuing the work on key-rollover
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• Re: ANY queries, recursing nameserver?
  • From: Paul Vixie <paul@vix.com>
• I-D ACTION:draft-ietf-dnsext-dnssec-rsasha256-01.txt
  • From: Internet-Drafts@ietf.org
• Re: ANY queries, recursing nameserver?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: ANY queries, recursing nameserver?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ANY queries, recursing nameserver?
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: ANY queries, recursing nameserver?
  • From: Paul Vixie <paul@vix.com>
• Re: ANY queries, recursing nameserver?
  • From: Josh Littlefield <joshl@cisco.com>
• Re: stopping amplification
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: Paul Vixie <paul@vix.com>
• Re: ANY queries, recursing nameserver?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• Re: stopping amplification
  • From: Roy Arends <roy@nominet.org.uk>
• Re: stopping amplification
  • From: Peter Koch <pk@DENIC.DE>
• Re: stopping amplification
  • From: Roy Arends <roy@nominet.org.uk>
• Re: stopping amplification
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: stopping amplification
  • From: Roy Arends <roy@nominet.org.uk>
• Re: stopping amplification
  • From: Peter Koch <pk@denic.de>
• Re: stopping amplification
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: ANY queries, recursing nameserver?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: stopping amplification
  • From: Roy Arends <roy@nominet.org.uk>
• RE: stopping amplification
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: stopping amplification
  • From: Robert Story <rstory@sparta.com>
• RE: stopping amplification
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: ANY queries, recursing nameserver?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ANY queries, recursing nameserver?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: ANY queries, recursing nameserver?
  • From: "Everhart, Craig" <Craig.Everhart@netapp.com>
• Re: ANY queries, recursing nameserver?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• upon reflection, was Re: stopping amplification
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• ANY queries, recursing nameserver?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• moving on from:? Re: stopping amplification
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: stopping amplification
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: stopping amplification
  • From: Paul Vixie <paul@vix.com>
• Protocol Action: 'The Role of Wildcards in the Domain Name System' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• Re: stopping amplification
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: stopping amplification
  • From: bmanning@vacation.karoshi.com
• stopping amplification
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• I-D ACTION:draft-ietf-dnsext-rfc2539bis-dhk-07.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-rfc2536bis-dsa-07.txt
  • From: Internet-Drafts@ietf.org
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Proposal, DSA 2048 with 256 bit subgroup
  • From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• comments on dnssec-experiments
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: "william(at)elan.net" <william@elan.net>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Usefulness of ECC-DSA algorithm for DNSSEC
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DH/DSA I-Ds
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: DH/DSA I-Ds
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: draft-ietf-dnsext-rfc2539bis-dhk-06.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• I-D ACTION:draft-ietf-dnsext-2929bis-02.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-dhcid-rr-13.txt
  • From: Internet-Drafts@ietf.org
• Re: I-D ACTION:draft-ietf-dnsext-wcard-clarify-11.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• I-D ACTION:draft-ietf-dnsext-wcard-clarify-11.txt
  • From: Internet-Drafts@ietf.org
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• DH/DSA I-Ds
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• RE: DSA and D-H I-Ds?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: David Blacka <davidb@verisignlabs.com>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DSA and D-H I-Ds?
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• DSA and D-H I-Ds?
  • From: Ben Laurie <ben@algroup.co.uk>
• draft-ietf-dnsext-rfc2539bis-dhk-06.txt
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• draft-ietf-dnsext-rfc2536bis-dsa-06.txt review
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Proposed RFC 2538bis AUTH48 problem resolution
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• draft-ietf-dnsext-rfc2536bis-dsa-06
  • From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
• draft-ietf-dnsext-dnssec-rsasha256 security considerations
  • From: Rob Austein <sra@isc.org>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 10: Potential DoS on Servers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Sam Weiler <weiler@tislabs.com>
• Re: NSEC3 Issue 8: NSEC3 Signaling Mechanism
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• test event report
  • From: Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>
• Re: Secure DNS is just weakly secure
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: RE-ISSUE 1: 5.6
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: RE-ISSUE 1: 5.6
  • From: Andras Salamon <andras@dns.net>
• Re: RE-ISSUE 1: 5.6
  • From: Brett Carr <brettcarr@ripe.net>
• RE-ISSUE 1: 5.6
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Review of draft-ietf-dnsext-dnssec-opt-in-08
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• RE: Secure DNS is just weakly secure
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• NSD patches available
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: ISSUE 2: Mandatory to implement
  • From: bmanning@vacation.karoshi.com
• Review of draft-ietf-dnsext-dnssec-experiments-02
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• RE: Secure DNS is just weakly secure
  • From: "Loomis, Rip" <GILBERT.R.LOOMIS@saic.com>
• Publication Request: LLMNR-45 to Informational
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• Re: Secure DNS is just weakly secure
  • From: Sean Leach <sleach@wiggum.com>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Secure DNS is just weakly secure
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Secure DNS is just weakly secure
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Secure DNS is just weakly secure
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: Secure DNS is just weakly secure
  • From: Jim Reid <jim@rfc1035.com>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Proposed RFC 2538bis AUTH48 problem resolution
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Proposed RFC 2538bis AUTH48 problem resolution
  • From: Simon Josefsson <jas@extundo.com>
• Re: Secure DNS is just weakly secure
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Secure DNS is just weakly secure
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: Secure DNS is just weakly secure
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Secure DNS is just weakly secure
  • From: Paul Vixie <paul@vix.com>
• Re: Secure DNS is just weakly secure
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Secure DNS is just weakly secure
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Secure DNS is just weakly secure
  • From: Tony Finch <dot@dotat.at>
• RE: Secure DNS is just weakly secure
  • From: "Brett Carr" <brettcarr@ripe.net>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Secure DNS is just weakly secure
  • From: "Anders Rundgren" <anders.rundgren@telia.com>
• Re: Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Secure DNS is just weakly secure
  • From: Paul Vixie <paul@vix.com>
• Secure DNS is just weakly secure
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: bmanning@vacation.karoshi.com
• Re: WGLC dnssec-experiments and dnssec-opt-in
  • From: Matt Larson <mlarson@verisign.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Rodney Joffe <rjoffe@centergate.com>
• Re: ISSUE 2: Mandatory to implement
  • From: Paul Vixie <paul@vix.com>
• ISSUE 2: Mandatory to implement
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Draft agenda
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• comments on draft-ietf-dnsext-dnssec-opt-in-08
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• review of draft-ietf-dnsext-dnssec-experiments-02
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• NSEC3 Pre-Workshop Report
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Protocol Action: 'HMAC SHA TSIG Algorithm Identifiers' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• I-D ACTION:draft-ietf-dnsext-nsec3-04.txt
  • From: Internet-Drafts@ietf.org
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Sam Hartman <hartmans-ietf@mit.edu>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• MUST vs SHOULD for trust anchor rollover, nameserver side
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RE: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Christian Huitema" <huitema@windows.microsoft.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• RE: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: David Blacka <davidb@verisignlabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Thomas Narten <narten@us.ibm.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Sam Weiler <weiler@tislabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Mark Kosters <markk@verisignlabs.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Thomas Narten <narten@us.ibm.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Russ Mundy <mundy@tislabs.com>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• RE: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Roy Arends" <roy@nominet.org.uk>
• Reminder: WGLC dnssec-experiments and dnssec-opt-in
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• DNSSEC Validator API
  • From: Suresh Krishnaswamy <suresh@tislabs.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Andrew Sullivan <ajs@crankycanuck.ca>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Simon Josefsson <jas@extundo.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Rob Austein <sra@isc.org>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Robert Story <rstory@tislabs.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Rob Austein <sra@isc.org>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thomas Narten <narten@us.ibm.com>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Simon Josefsson <jas@extundo.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ISSUE 1: IPR , response #2
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: bmanning@vacation.karoshi.com
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: "william(at)elan.net" <william@elan.net>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "william(at)elan.net" <william@elan.net>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Damien Miller <djm@mindrot.org>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Damien Miller <djm@mindrot.org>
• ISSUE 1: IPR was Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ted Lemon <mellon@fugue.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Mark Andrews <Mark_Andrews@isc.org>
• DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: DLV now an informational section of DNS protocol suite, plus the TA RR as a bonus
  • From: Thomas Narten <narten@us.ibm.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Matt Larson <mlarson@verisign.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ted Lemon <mellon@fugue.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: bmanning@vacation.karoshi.com
• Protocol Action: 'Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "Hilarie Orman" <hilarie@purplestreak.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: "The Purple Streak, Hilarie Orman" <ho@alum.mit.edu>
• Re: DNSSEC is almost worthless!
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Paul Vixie <paul@vix.com>
• Re: Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Section 5.2 (IPR encumberance) in TAK rollover requirement draft
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• DNSSEC is almost worthless!
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• I-D ACTION:draft-ietf-dnsext-dhcid-rr-12.txt
  • From: Internet-Drafts@ietf.org
• DNS conformance tester version 1.0 is available
  • From: Yukiyo Akisada <Yukiyo.Akisada@jp.yokogawa.com>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Updated draft - draft-ietf-dnsext-dhcid-rr-12.txt
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• NSEC3 Workshop - 8-10 May
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• RE: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: "Scott Rose" <scottr@nist.gov>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Paul Vixie <paul@vix.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: "Hilarie Orman" <ho@alum.mit.edu>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Simon Josefsson <jas@extundo.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Alex Bligh <alex@alex.org.uk>
• IETF-65 DNSEXT agenda items
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Alex Bligh <alex@alex.org.uk>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Simon Josefsson <jas@extundo.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Simon Josefsson <jas@extundo.com>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Mark Stapp <mjs@cisco.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Alex Bligh <alex@alex.org.uk>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Alex Bligh <alex@alex.org.uk>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Paul Vixie <paul@vix.com>
• WGLC dnssec-experiments and dnssec-opt-in
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Simon Josefsson <jas@extundo.com>
• Re: draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Alex Bligh <alex@alex.org.uk>
• draft-ietf-dnsext-rollover-requirements-00.txt 5.2
  • From: Simon Josefsson <jas@extundo.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Paul Vixie <paul@vix.com>
• RE: [dhcwg] Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• RE: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Alex Bligh <alex@alex.org.uk>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• I-D ACTION:draft-ietf-dnsext-dhcid-rr-11.txt
  • From: Internet-Drafts@ietf.org
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Russ Mundy <mundy@sparta.com>
• RE: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Russ Mundy <mundy@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Wes Hardaker <hardaker@tislabs.com>
• I-D ACTION:draft-ietf-dnsext-ds-sha256-05.txt
  • From: Internet-Drafts@ietf.org
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Peter Koch <pk@DENIC.DE>
• RE: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: "Scott Rose" <scottr@nist.gov>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: David Conrad <david.conrad@nominum.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Russ Mundy <mundy@sparta.com>
• Re: NSEC3 Issue 10: Potential DoS on Servers
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: NSEC3 Issue 10: Potential DoS on Servers
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: NSEC3 Issue 8: NSEC3 Signaling Mechanism
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: NSEC3 Issue 8: NSEC3 Signaling Mechanism
  • From: Roy Arends <roy@nominet.org.uk>
• Re: NSEC3 Issue 8: NSEC3 Signaling Mechanism
  • From: Mark Andrews <Mark_Andrews@isc.org>
• I-D ACTION:draft-ietf-dnsext-rollover-requirements-00.txt
  • From: Internet-Drafts@ietf.org
• NSEC3 issue: DNSSEC is too complex by half already
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Alex Bligh <alex@alex.org.uk>
• NSEC3 Issue 13: DDNS and Opt-In Determination
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Issue 10: Potential DoS on Servers
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Issue 9: Potential DoS on Resolvers
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Issue 8: NSEC3 Signaling Mechanism
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Resolved Issues
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Issues
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Paul Vixie <paul@vix.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Sam Weiler <weiler@tislabs.com>
• Re: LLMNR consensus statement
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: David Blacka <davidb@verisignlabs.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: LLMNR consensus statement
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: LLMNR consensus statement
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: I-D ACTION:draft-ietf-dnsext-dnssec-rsasha256-00.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: LLMNR consensus statement
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: LLMNR consensus statement
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Paul Vixie <paul@vix.com>
• DNSSECbis clarifications: QTYPE ANY & "DNSSEC RRSets"
  • From: Peter Koch <pk@DENIC.DE>
• Re: LLMNR consensus statement
  • From: Bernard Aboba <aboba@internaut.com>
• Re: LLMNR consensus statement
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: LLMNR consensus statement
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: LLMNR consensus statement
  • From: Simon Josefsson <jas@extundo.com>
• Re: LLMNR consensus statement
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: LLMNR consensus statement
  • From: Simon Josefsson <jas@extundo.com>
• Re: LLMNR consensus statement
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: LLMNR consensus statement
  • From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
• Re: LLMNR consensus statement
  • From: Stuart Cheshire <cheshire@apple.com>
• LLMNR consensus statement
  • From: Ólafur Guðmundsson <ogud@ogud.com>
• I-D ACTION:draft-ietf-dnsext-dnssec-rsasha256-00.txt
  • From: Internet-Drafts@ietf.org
• RE: DDNS IESG Issue resolution.
  • From: "Christian Huitema" <huitema@windows.microsoft.com>
• Re: DDNS IESG Issue resolution.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DDNS IESG Issue resolution.
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: DDNS IESG Issue resolution.
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DDNS IESG Issue resolution.
  • From: Ben Laurie <ben@algroup.co.uk>
• Re: DNSEXT Document Review: LLMNR-45
  • From: "Eric A. Hall" <ehall@ehsco.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: "Eric A. Hall" <ehall@ehsco.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Bernard Aboba <aboba@internaut.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: "Eric A. Hall" <ehall@ehsco.com>
• Re: A least a draft now exists for trust anchor key rollover requirements.
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• A least a draft now exists for trust anchor key rollover requirements.
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: DDNS IESG Issue resolution.
  • From: Ralph Droms <rdroms@cisco.com>
• Re: DDNS IESG Issue resolution.
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dhcwg] Re: DDNS IESG Issue resolution.
  • From: "David W. Hankins" <David_Hankins@isc.org>
• Re: DDNS IESG Issue resolution.
  • From: Sam Hartman <hartmans-ietf@mit.edu>
• Re: DDNS IESG Issue resolution.
  • From: Ralph Droms <rdroms@cisco.com>
• Re: DDNS IESG Issue resolution.
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ted Lemon <mellon@fugue.com>
• Limiting recursion...was Re: the RD bit is troubling me today
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: the RD bit is troubling me today
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: the RD bit is troubling me today
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: the RD bit is troubling me today
  • From: Paul Vixie <paul@vix.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Harald Tveit Alvestrand <harald@alvestrand.no>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Sam Hartman <hartmans-ietf@mit.edu>
• Re: the RD bit is troubling me today
  • From: Paul Vixie <paul@vix.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "David W. Hankins" <David_Hankins@isc.org>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ted Lemon <mellon@fugue.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Harald Tveit Alvestrand <harald@alvestrand.no>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: the RD bit is troubling me today
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: the RD bit is troubling me today
  • From: "Paul V. Mockapetris" <Paul.Mockapetris@nominum.com>
• FW: Document Action: 'US Secure Hash Algorithms (SHA and HMAC-SH A)' to Informational RFC
  • From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
• Re: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ted Lemon <mellon@fugue.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: "Dave Thaler" <dthaler@windows.microsoft.com>
• Re: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: the RD bit is troubling me today
  • From: Paul Vixie <paul@vix.com>
• Re: the RD bit is troubling me today
  • From: Paul Vixie <paul@vix.com>
• Re: the RD bit is troubling me today
  • From: Peter Koch <pk@denic.de>
• RE: [dhcwg] Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: the RD bit is troubling me today
  • From: Simon Josefsson <jas@extundo.com>
• Re: the RD bit is troubling me today
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: the RD bit is troubling me today
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• the RD bit is troubling me today
  • From: Paul Vixie <paul@vix.com>
• RE: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
  • From: Harald Tveit Alvestrand <harald@alvestrand.no>
• RE: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: Implementation work done on DNSSEC trust anchor key rollover solution
  • From: Paul Vixie <paul@vix.com>
• Implementation work done on DNSSEC trust anchor key rollover solution
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• RE: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
  • From: Harald Tveit Alvestrand <harald@alvestrand.no>
• RE: [dhcwg] Re: UTF-8 issues (Re: Open issues in DHCP FQDN,DHCID and DDNS-DHCP Related RFCs)
  • From: "Bernie Volz \(volz\)" <volz@cisco.com>
• Re: UTF-8 issues (Re: Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: UTF-8 issues (Re: Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• UTF-8 issues (Re: Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs)
  • From: Harald Tveit Alvestrand <harald@alvestrand.no>
• Open issues in DHCP FQDN, DHCID and DDNS-DHCP Related RFCs
  • From: Ralph Droms <rdroms@cisco.com>
• RE: [question]What is an accurate meaning of "client" in RFC2181?
  • From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
• Re: [question]What is an accurate meaning of "client" in RFC2181?
  • From: Paul Vixie <paul@vix.com>
• Re: [question]What is an accurate meaning of "client" in RFC2181?
  • From: Hideshi Enokihara <Hideshi.Enokihara@jp.yokogawa.com>
• Re: [question]What is an accurate meaning of "client" in RFC2181?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [question]What is an accurate meaning of "client" in RFC2181?
  • From: Hideshi Enokihara <Hideshi.Enokihara@jp.yokogawa.com>
• I-D ACTION:draft-ietf-dnsext-tsig-sha-06.txt
  • From: Internet-Drafts@ietf.org
• Last Call: 'Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• Re: RFC 2538bis security problem with the indirect types
  • From: "william(at)elan.net" <william@elan.net>
• Re: RFC 2538bis security problem with the indirect types
  • From: Simon Josefsson <jas@extundo.com>
• Re: RFC 2538bis security problem with the indirect types
  • From: "Stuart E. Schechter" <ses@ll.mit.edu>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Protocol Action: 'Minimally Covering NSEC Records and DNSSEC On-line Signing' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• Re: RFC 2538bis security problem with the indirect types
  • From: Simon Josefsson <jas@extundo.com>
• Re: RFC 2538bis security problem with the indirect types
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: RFC 2538bis security problem with the indirect types
  • From: David Shaw <dshaw@jabberwocky.com>
• Re: RFC 2538bis security problem with the indirect types
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: DNSEXT WGLC: RFC2536bis and RFC2539bis
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• RFC 2538bis security problem with the indirect types
  • From: Simon Josefsson <jas@extundo.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: "Eric A. Hall" <ehall@ehsco.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Bernard Aboba <aboba@internaut.com>
• RE: DNSEXT WGLC: RFC2536bis and RFC2539bis
  • From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
• RE: DNSEXT WGLC: RFC2536bis and RFC2539bis
  • From: "Scott Rose" <scottr@nist.gov>
• I-D ACTION:draft-ietf-dnsext-dnssec-online-signing-02.txt
  • From: Internet-Drafts@ietf.org
• Re: DNSEXT WGLC: RFC2536bis and RFC2539bis
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• DNSEXT publication request: DS SHA-256
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Request to publish draft-ietf-dnsext-nsid
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Andrew Sullivan <ajs@crankycanuck.ca>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Tony Finch <dot@dotat.at>
• Re: DNSEXT Document Review: LLMNR-45
  • From: bmanning@vacation.karoshi.com
• Re: DNSEXT Document Review: LLMNR-45
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• RE: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: "Scott Rose" <scottr@nist.gov>
• Even newer version of draft-ietf-dnsext-dnssec-online-signing
  • From: Samuel Weiler <weiler@tislabs.com>
• RE: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: Trust Anchor Key management issue, stalled or slow progress?
  • From: Paul Vixie <paul@vix.com>
• Trust Anchor Key management issue, stalled or slow progress?
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: Trust Anchor Key management issue, stalled or slow progress?
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Paul Vixie <vixie@vix.com>
• I-D ACTION:draft-ietf-dnsext-ds-sha256-04.txt
  • From: Internet-Drafts@ietf.org
• Re: WG LC results summary: draft-ietf-dnsext-ds-sha256-03.txt
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: WG LC results summary: draft-ietf-dnsext-ds-sha256-03.txt
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• WG LC results summary: draft-ietf-dnsext-ds-sha256-03.txt
  • From: Wes Hardaker <hardaker@tislabs.com>
• [Reminder IETF 65 Dallas]
  • From: bmanning@vacation.karoshi.com
• DNSEXT document status and actions 200601
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• I-D ACTION:draft-ietf-dnsext-nsid-01.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-dnssec-bis-updates-02.txt
  • From: Internet-Drafts@ietf.org
• Re: DNSEXT Document Review: LLMNR-45
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• Re: IANA considerations in RFC 2538bis
  • From: Simon Josefsson <jas@extundo.com>
• Re: IANA considerations in RFC 2538bis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Paul Vixie <paul@vix.com>
• Re: I-D ACTION:draft-ietf-dnsext-ds-sha256-03.txt
  • From: Wes Hardaker <hardaker@tislabs.com>
• IANA considerations in RFC 2538bis
  • From: Simon Josefsson <jas@extundo.com>
• Re: DNSEXT Document Review: LLMNR-45
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• DNSEXT Document Review: LLMNR-45
  • From: Ólafur Guðmundsson /DNSEXT co-chair <ogud@ogud.com>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• RFC 4343 on Domain Name System (DNS) Case Insensitivity Clarification
  • From: rfc-editor@rfc-editor.org
• Re: NSEC3 Testing Mailing List
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: NSEC3 Testing Mailing List
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• NSEC3 Testing Mailing List
  • From: Geoffrey Sisson <geoff@nominet.org.uk>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: David Blacka <davidb@verisignlabs.com>
• Re: I-D ACTION:draft-ietf-dnsext-ds-sha256-03.txt
  • From: David Blacka <davidb@verisignlabs.com>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: I-D ACTION:draft-ietf-dnsext-trustupdate-timers-02.txt
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: I-D ACTION:draft-ietf-dnsext-trustupdate-timers-02.txt
  • From: Mike StJohns <Mike.StJohns@nominum.com>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• Re: I-D ACTION:draft-ietf-dnsext-trustupdate-timers-02.txt
  • From: Paul Vixie <paul@vix.com>
• Re: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: Andrew Sullivan <andrew@ca.afilias.info>
• I-D ACTION:draft-ietf-dnsext-trustupdate-timers-02.txt
  • From: Internet-Drafts@ietf.org
• RE: New version of draft-ietf-dnsext-dnssec-online-signing
  • From: "Scott Rose" <scottr@nist.gov>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• New version of draft-ietf-dnsext-dnssec-online-signing
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Kevin Darcy <kcd@daimlerchrysler.com>
• I-D ACTION:draft-ietf-dnsext-wcard-clarify-10.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-ds-sha256-03.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-dnssec-online-signing-01.txt
  • From: Internet-Drafts@ietf.org
• Fwd: RFC 4255
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: DNSEXT WGLC: DS SHA-256
  • From: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
• DNSEXT list policy
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>