Mail Index

• Thread Index

• Re: [dnsext] hopefully axfr-clarify-10 will appear soon
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] hopefully axfr-clarify-10 will appear soon
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] hopefully axfr-clarify-10 will appear soon
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Zone Immortality
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] AXFR Clarify -- open issue w/ 'zone loading'
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] axfr clarify update is in the works
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] [IANA #206165] Resut of expert review for RRTYPE request: ZS(NINFO)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] [dns-rrtype-applications] [IANA #206166] Resut of expert review for RRTYPE request: RKEY
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] [IANA #206165] Resut of expert review for RRTYPE request: ZS (NINFO)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] [IANA #206165] Resut of expert review for RRTYPErequest: ZS(NINFO)
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] [IANA #206165] Resut of expert review for RRTYPE request: ZS(NINFO)
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] San Francisco IETF meeting
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RFC 5378, the IETF Trust, and consequences on DNSEXT
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] EDNS0 options open issues
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Some remarks about new governing rules (Re: [dnsext] DNSEXT List Policy)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Some remarks about new governing rules (Re: [dnsext] DNSEXT List Policy)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: "Donald Eastlake" <d3e3e3@gmail.com>
• [dnsext] DNSEXT List Policy
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: Matt Larson <mlarson@verisign.com>
• [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] ASSET and NEGATIVE RRTYPE requests
  • From: Matt Larson <mlarson@verisign.com>
• [dnsext] Disposition of request for assignment: NEGATIVE (IANA #186451)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Disposition of request for assignment: ASSET (IANA #164632)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Re: ASSET and NEGATIVE RRTYPE requests
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] ASSET and NEGATIVE RRTYPE requests
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Protocol Action: 'Measures for making DNS more resilient against forged answers' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] RSA/SHA2 new NSEC3 text proposal
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] IANA DNS params registry typo w.r.t. label types
  • From: Michelle Cotton <michelle.cotton@icann.org>
• Re: FW: [dnsext] IANA DNS params registry typo w.r.t. label types
  • From: Rob Austein <sra@isc.org>
• [dnsext] I-D Action:draft-ietf-dnsext-forgery-resilience-10.txt
  • From: Internet-Drafts@ietf.org
• FW: [dnsext] IANA DNS params registry typo w.r.t. label types
  • From: Michelle Cotton <michelle.cotton@icann.org>
• Re: [dnsext] one algorithm number or two
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] one algorithm number or two
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  • From: "Blacka, David" <davidb@verisign.com>
• Re: [dnsext] one algorithm number or two
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] one algorithm number or two
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] draft-ietf-dnsext-dnssec-bis-updates and NSEC3
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] one algorithm number or two
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] IANA DNS params registry typo w.r.t. label types
  • From: Nicolas Williams <Nicolas.Williams@sun.com>
• Re: [dnsext] one algorithm number or two
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] one algorithm number or two
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] one algorithm number or two
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] one algorithm number or two
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] one algorithm number or two
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: [rt.amsl.com #12130] Resolved: Publication request for draft-ietf-dnsext-dnssec-rsasha256-09.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: "Blacka, David" <davidb@verisign.com>
• [dnsext] Re: implied NSEC3 support in rsasha256
  • From: Wes Hardaker <wjhns1@hardakers.net>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Scott Rose <scottr@nist.gov>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Matt Larson <mlarson@verisign.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Samuel Weiler <weiler@watson.org>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Working group workflow
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] Working group workflow (nsec3 in draft-sha256)
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Working group workflow (nsec3 in draft-sha256)
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] Working group workflow (nsec3 in draft-sha256)
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Working group workflow
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Working group workflow
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] explicit non-support of NSEC3
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Assistance in helping in securing and investing
  • From: "Ian Nuri"<ian.nuri@solicitors.org.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Online survey from Wal-Mart Stores !!!!!!!!!
  • From: "Wal-Mart Store"<no-reply@wal-mart.com>
• Re: [dnsext] errata 4034 - 5011
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] Publication request for draft-ietf-dnsext-dnssec-rsasha256-09.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-crocker-dnssec-algo-signal as WG item
  • From: JFC Morfin <jefsey@jefsey.com>
• Re: [dnsext] errata 4034 - 5011
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] Report on NSEC3 interop workshop during IETF73
  • From: Joao Damas <Joao_Damas@isc.org>
• Re: [dnsext] errata 4034 - 5011
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-09.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] errata 4034 - 5011
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RRs with 0 TTL
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-08.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-08.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] errata 4034 - 5011
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-07.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Samuel Weiler <weiler@watson.org>
• Re: [dnsext] RRTYPE request for NINFO
  • From: Samuel Weiler <weiler@watson.org>
• [dnsext] Minutes from IETF73 uploaded
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] DNS RR (RFC 4701) impacts from draft-arkko-arp-iana-rules
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: [dnsext] RRTYPE request for NINFO
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] DNS RR (RFC 4701) impacts from draft-arkko-arp-iana-rules
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] RRTYPE request for NINFO
  • From: Ted Hardie <hardie@qualcomm.com>
• [dnsext] DNS RR (RFC 4701) impacts from draft-arkko-arp-iana-rules
  • From: Jari Arkko <jari.arkko@piuha.net>
• Re: RRTYPE love, was Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: RRTYPE love, was Re: [dnsext] RRTYPE request: template for ZS record
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-00.txt
  • From: Internet-Drafts@ietf.org
• RRTYPE love, was Re: [dnsext] RRTYPE request: template for ZS record
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] EDNS0 options open issues
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• [dnsext] BCP 42, RFC 5395 on Domain Name System (DNS) IANA Considerations
  • From: rfc-editor@rfc-editor.org
• Re: [dnsext] EDNS0 options open issues
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Re: s/ZS/NI/
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: s/ZS/NI/
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: s/ZS/NI/
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] Re: s/ZS/NI/
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: [dnsext] Re: s/ZS/NI/
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Re: s/ZS/NI/
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: s/ZS/NI/
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] EDNS0 options open issues
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] s/ZS/NI/
  • From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
• Re: [dnsext] s/ZS/NI/
  • From: Kim Davies <kim.davies@icann.org>
• Re: [dnsext] s/ZS/NI/
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] s/ZS/NI/
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] s/ZS/NI/
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Peter Koch <pk@DENIC.DE>
• [dnsext] s/ZS/NI/
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] EDNS0 options open issues
  • From: Stuart Cheshire <cheshire@apple.com>
• [dnsext] whois vs. Re:...template for ZS record
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] EDNS0 options open issues
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] EDNS0 options open issues
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] 2929bis DNS assumptions [was RRTYPE request: template for ZS record]
  • From: Peter Koch <pk@DENIC.DE>
• [dnsext] Re: RRTYPE request: template for proposed RKEY RRtype
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: [dnsext] 2929bis DNS assumptions [was RRTYPE request: template for ZS record]
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] 2929bis DNS assumptions [was RRTYPE request: template for ZS record]
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: [dnsext] 2929bis DNS assumptions [was RRTYPE request: template for ZS record]
  • From: Patrik Fältström <paf@cisco.com>
• [dnsext] 2929bis DNS assumptions [was RRTYPE request: template for ZS record]
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] RRTYPE request: template for ZS record
  • From: Ted Hardie <hardie@qualcomm.com>
• [dnsext] RRTYPE request: template for proposed RKEY RRtype
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RRTYPE request: template for ZS record
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• solution space discussion, was Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: EDNS0 options open issues
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Patrik Fältström <paf@cisco.com>
• [dnsext] Infinity and draft-andrews-dnsext-expire-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Timing down a zone
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Dean Anderson <dean@av8.com>
• Re: [dnsext] Timing down a zone
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Timing down a zone
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Timing down a zone
  • From: bmanning@vacation.karoshi.com
• [dnsext] Timing down a zone
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] EDNS0 options open issues
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] dns64
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-01.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] request to adopt draft-andrews-dnsext-expire-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] dns64
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• [dnsext] Document Adoption: DNS Proxy Implementation Guidelines
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Frederico A C Neves <fneves@registro.br>
• [dnsext] RE: (Off-Topic) DNSSEC Technical Testing update
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• [dnsext] Re: (Off-Topic) DNSSEC Technical Testing update
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] I-D Action:draft-ietf-dnsext-forgery-resilience-09.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] A contradiction in RFC 5155
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] A contradiction in RFC 5155
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] A contradiction in RFC 5155
  • From: "Roy Arends" <roy@nominet.org.uk>
• [dnsext] I-D Action:draft-ietf-dnsext-forgery-resilience-08.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] [DNSOP] (Off-Topic) DNSSEC Technical Testing update
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• Re: [dnsext] My Final Thoughts/Conclusions for forgery resistance...
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• RE: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• [dnsext] EDNS0 Option Code
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] My Final Thoughts/Conclusions for forgery resistance...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] My Final Thoughts/Conclusions for forgery resistance...
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] My Final Thoughts/Conclusions for forgery resistance...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] draft-crocker-dnssec-algo-signal as WG item
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Clarification of RFC 4035, Section 4.3
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] draft-crocker-dnssec-algo-signal as WG item
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Draft agenda for IETF 73
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Zones suitable for AXFR
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• [dnsext] Call for scribe volunteers
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Zones suitable for AXFR
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Draft agenda for IETF 73
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Re: draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Draft agenda for IETF 73
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Draft agenda for IETF 73 (corrected)
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] Draft agenda for IETF 73
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] Draft agenda for IETF 73
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Zones suitable for AXFR
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Draft agenda for IETF 73
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Zones suitable for AXFR
  • From: Stephen.Morris@nominet.org.uk
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• RE: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: "Avirneni, Srini" <Srini_Avirneni@Cable.Comcast.com>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Patrik Wallstrom <pawal@blipp.com>
• [dnsext] draft-bellis-dnsext-dnsproxy-00 - WG Item?
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Ray.Bellis@nominet.org.uk
• RE: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: "Dan Wing" <dwing@cisco.com>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] draft-ietf-dnsext-dnssec-rsasha256-06 nits
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] Agenda items for Minneapolis, IETF-73
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Agenda items for Minneapolis, IETF-73
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RE: [DNSOP] (Off-Topic) DNSSEC Technical Testing
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• Re: [dnsext] Agenda items for Minneapolis, IETF-73
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] draft-bellis-dnsext-dnsproxy-00
  • From: Ray.Bellis@nominet.org.uk
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] Agenda items for Minneapolis, IETF-73
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Re: Results of WGLC: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-06.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] FR: An argument against 0x20 and mitigation by standard labels
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Source Port and QID selection for re-transmits?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Fwd: Posting of IPR Disclosure
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Source Port and QID selection for re-transmits?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] Source Port and QID selection for re-transmits?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• [dnsext] Source Port and QID selection for re-transmits?
  • From: Ray.Bellis@nominet.org.uk
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] Results of WGLC: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] FR: An argument against 0x20 and mitigation by standard labels
  • From: Dean Anderson <dean@av8.com>
• Re: [dnsext] FR: An argument against 0x20 and mitigation by standard labels
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] FR: An argument against 0x20 and mitigation by standard labels
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] FR: An argument against 0x20 and mitigation by standard labels
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] FR: comments re draft-weaver-dnsext-fr-comprehensive-00.txt
  • From: "George Barwood" <george@emsv.co.uk>
• [dnsext] Re: Time-line for forgery resilience phase #2
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] draft-barwood-dnsext-fr-resolver-mitigations-03
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] draft-barwood-dnsext-fr-resolver-mitigations-03
  • From: Dean Anderson <dean@av8.com>
• [dnsext] DNS profile effort
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] One other argument for local scope...
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: [dnsext] Some notes on ipv4/ipv6 co-existence
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Re: George Barwood's Birthday Observation...
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Some notes on ipv4/ipv6 co-existence
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: George Barwood's Birthday Observation...
  • From: Dean Anderson <dean@av8.com>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• [dnsext] DNS Extensions session scheduled
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: CNAME/DNAME - Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: George Barwood's Birthday Observation...
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] One other argument for local scope...
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] One other argument for local scope...
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] One other argument for local scope...
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] One other argument for local scope...
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: CNAME/DNAME - Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: CNAME/DNAME - Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: CNAME/DNAME - Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Interpreting DNSSEC was Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• CNAME/DNAME - Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• [dnsext] draft-barwood-dnsext-fr-resolver-mitigations-03
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Firewall support for large DNS names (>255) and packets (>512)?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Last Call: draft-ietf-dnsext-forgery-resilience (Measures for making DNS more resilient against forged answers) to Proposed Standard
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] One other argument for local scope...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] One other argument for local scope...
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Dean Anderson <dean@av8.com>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Dean Anderson <dean@av8.com>
• Re: Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Why an ID? was [dnsext] Re: No spec for DNSCurve
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: No spec for DNSCurve
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Re: No spec for DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: No spec for DNSCurve
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Last Call: draft-ietf-dnsext-forgery-resilience (Measures for making DNS more resilient against forged answers) to Proposed Standard
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Last Call: draft-ietf-dnsext-forgery-resilience (Measures for making DNS more resilient against forged answers) to Proposed Standard
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: "Adam Langley" <agl@imperialviolet.org>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: "Adam Langley" <agl@imperialviolet.org>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Notice of Inquiry regarding DNSSEC]
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Notice of Inquiry regarding DNSSEC]
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] No spec for DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Notice of Inquiry regarding DNSSEC]
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Rabin-Williams signatures for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: "Adam Langley" <agl@imperialviolet.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Dean Anderson <dean@av8.com>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: "Matthew Dempsky" <matthew@dempsky.org>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] implementations of RFC 5155 (aka NSEC3)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: [dnsext] Re: Protecting caches?
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Re: SCTP (and DCCP)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Brian Dickson <briand@ca.afilias.info>
• [dnsext] Rabin-Williams signatures for DNSSEC
  • From: "Adam Langley" <agl@imperialviolet.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Err, CORRECT link for my comments...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Err, CORRECT link for my comments...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Err, CORRECT link for my comments...
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: the DO bit Re: [dnsext] Reminder: two WGLC closing in one week
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: the DO bit Re: [dnsext] Reminder: two WGLC closing in one week
  • From: bmanning@vacation.karoshi.com
• the DO bit Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] One other argument for local scope...
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] One other argument for local scope...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: REMINDER: rfc2672bis WGLC expiring!
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] Re: Protecting caches?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: REMINDER: rfc2672bis WGLC expiring!
  • From: Peter Koch <pk@DENIC.DE>
• [dnsext] Protocol Action: 'Domain Name System (DNS) IANA Considerations' to BCP
  • From: The IESG <iesg-secretary@ietf.org>
• Re: [dnsext] Last Call: draft-ietf-dnsext-forgery-resilience (Measures for making DNS more resilient against forged answers) to Proposed Standard
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Last Call: draft-ietf-dnsext-forgery-resilience (Measures for making DNS more resilient against forged answers) to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• [dnsext] Re: [DNSOP] (Off-Topic) DNSSEC Technical Testing
  • From: Paul Wouters <paul@xelerance.com>
• [dnsext] (Off-Topic) DNSSEC Technical Testing
  • From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Protecting caches?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Protecting caches?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: Protecting caches?
  • From: Danny Mayer <mayer@gis.net>
• [dnsext] Re: Protecting caches?
  • From: Danny Mayer <mayer@ntp.isc.org>
• [dnsext] Err, CORRECT link for my comments...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] draft-weaver-dnsext-fr-comprehensive-00.txt
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Sam Weiler <weiler@tislabs.com>
• [dnsext] Re: Protecting caches?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] review and support of rsasha256
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] review and support of rsasha256
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: [dnsext] alternatives to the proposed NEGATIVE pseudo-RR
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] review and support of rsasha256
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] alternatives to the proposed NEGATIVE pseudo-RR
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• [dnsext] Re: DNAME (and CNAME) vs DNSSEC
  • From: Wes Hardaker <hardaker@tislabs.com>
• Re: [dnsext] recommeded contents for Re: DNAME (and CNAME) vs DNSSEC
  • From: Scott Rose <scottr@nist.gov>
• [dnsext] flip-flopping secure and unsecure DNAME/CNAME
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] recommeded contents for Re: DNAME (and CNAME) vs DNSSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNAME (and CNAME) vs DNSSEC (Was: [dnsext] Reminder: two WGLC closing in one week)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: DNAME (and CNAME) vs DNSSEC
  • From: Wes Hardaker <wjhns1@hardakers.net>
• [dnsext] Re: Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Paul Vixie <vixie@isc.org>
• DNAME (and CNAME) vs DNSSEC (Was: [dnsext] Reminder: two WGLC closing in one week)
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] To whomever asked for this, hope you're happy
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] (fwd) Notice of Annual KSK rollover for dlv.isc.org
  • From: Jacco Tunnissen <jacco@dnssec.net>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• implied NSEC3 support in rsasha256 (was: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05)
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] Reminder: two WGLC closing in one week
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] Reminder: two WGLC closing in one week
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Rob Austein <sra@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Re: Zone Immortality
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Rob Austein <sra@isc.org>
• Re: [dnsext] Re: Zone Immortality
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] Re: Zone Immortality
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] Re: Zone Immortality
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Re: Zone Immortality
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Rob Austein <sra@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Rob Austein <sra@isc.org>
• Re: [dnsext] Re: Protecting caches?
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: Protecting caches?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Announcement: Test Report on DNSSEC impact on SOHO CPE
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] Re: Proposed addition to dnssec-bis-updated: CD bit
  • From: Peter Koch <pk@DENIC.DE>
• [dnsext] Re: Protecting caches?
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Dean Anderson <dean@av8.com>
• [dnsext] [nomcom-chair@ietf.org: Nomcom call for candidates]
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Stuart Cheshire <cheshire@apple.com>
• [dnsext] On 2929bis procedures and current expert reviews
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: RRTYPE request for review and comment
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: RRTYPE request for review and comment
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Ted Hardie <hardie@qualcomm.com>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Request for new RRTYPE assignment: "ASSET"
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: RRTYPE request for review and comment
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Re: RRTYPE request for review and comment
  • From: Joe Abley <jabley@ca.afilias.info>
• [dnsext] Re: RRTYPE request for review and comment
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: David Ulevitch <davidu@everydns.net>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RRTYPE request for review and comment
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Wes Hardaker <wjhns1@hardakers.net>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] RRTYPE request for review and comment
  • From: ajs@commandprompt.com
• Re: [dnsext] Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Klaus Malorny <Klaus.Malorny@knipp.de>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Klaus Malorny <Klaus.Malorny@knipp.de>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Re: Possible materials for meeting in Minneapolis?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Ralf Weber <denic@eng.colt.net>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Antibozo <xen-users@antibozo.net>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Dean Anderson <dean@av8.com>
• Re: [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Proposed addition to dnssec-bis-updates: Nested Trust Anchors
  • From: "Blacka, David" <davidb@verisign.com>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] Re: Some notes on DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: Some notes on DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ben Laurie <ben@links.org>
• Re: [dnsext] Re: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] DNSKEY / multiprecision number format?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Eric Rescorla <ekr@networkresonance.com>
• [dnsext] Re: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Jefferson Ogata <bind-users@antibozo.net>
• [dnsext] Re: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• [dnsext] a note on the discussion about DNSCurve and DNSSEC
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• [dnsext] Re: Some notes on DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Some notes on DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• [dnsext] Re: Some notes on DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• [dnsext] AXFR Clarify -- open issue w/ 'zone loading'
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: [dnsext] draft-ietf-dnsext-rfc2672bis-dname WGLC
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] Re: Some notes on DNSCurve
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext]: draft-ietf-dnsext-dnssec-rsasha256-05 -- WGLC
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Re: Some notes on DNSCurve
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• [dnsext] Outstanding WG last calls
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Re: Some notes on DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: [dnsext] Mailing list change
  • From: "Jay R. Ashworth" <jra@baylink.com>
• [dnsext] Re: Some notes on DNSCurve
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• [dnsext] Re: draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Andrew Sullivan <ajs@commandprompt.com>
• [dnsext] Re: Some notes on DNSCurve
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• [dnsext] Re: Some notes on DNSCurve
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Mailing list change
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Time-line for forgery resilience phase #2
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Some notes on DNSCurve
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Alfred Hönes <ah@tr-sys.de>
• draft-ietf-dnsext-2929bis-07
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Some notes on DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: George Barwood's Birthday Observation...
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Some notes on DNSCurve
  • From: Duane at e164 dot org <duane@e164.org>
• Some notes on DNSCurve
  • From: "Jon A. Solworth" <solworth@rites.uic.edu>
• Re: George Barwood's Birthday Observation...
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: George Barwood's Birthday Observation...
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: George Barwood's Birthday Observation...
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: George Barwood's Birthday Observation...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: George Barwood's Birthday Observation...
  • From: Paul Vixie <vixie@isc.org>
• Re: George Barwood's Birthday Observation...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: George Barwood's Birthday Observation...
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• George Barwood's Birthday Observation...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: The Birthday Defense
  • From: Olaf Kolkman <Olaf@NLnetLabs.nl>
• Re: The Birthday Defense
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: The Birthday Defense
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Outstanding queries vs. source port randomization entropy
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: The Birthday Defense
  • From: list-namedroppers@pwns.ms
• Re: The Birthday Defense
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: DJB about NSEC3
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: The Birthday Defense
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: DJB about NSEC3
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DJB about NSEC3
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DJB about NSEC3
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: The Birthday Defense
  • From: list-namedroppers@pwns.ms
• Re: DJB about NSEC3
  • From: bert hubert <bert.hubert@netherlabs.nl>
• DJB about NSEC3
  • From: "Roy Arends" <roy@nominet.org.uk>
• The Birthday Defense
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: dnscurve -- new or did I just miss this?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: ECDSA (was dnscurve -- new or did I just miss this?)
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: dnscurve -- new or did I just miss this?
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Possible materials for meeting in Minneapolis?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Protecting caches?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Danny Mayer <mayer@gis.net>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dnscurve -- new or did I just miss this?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: Outstanding queries vs. source port randomization entropy
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dnscurve -- new or did I just miss this?
  • From: Paul Vixie <vixie@isc.org>
• Re: dnscurve -- new or did I just miss this?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dnscurve -- new or did I just miss this?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Outstanding queries vs. source port randomization entropy
  • From: Jefferson Ogata <bind-users@antibozo.net>
• Re: Repeat queries to non-deterministic servers
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Repeat queries to non-deterministic servers
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Repeat queries to non-deterministic servers
  • From: Paul Vixie <vixie@isc.org>
• Re: dnscurve -- new or did I just miss this?
  • From: "Blacka, David" <davidb@verisign.com>
• Re: dnscurve -- new or did I just miss this?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Repeat queries to non-deterministic servers
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• about EDNS0 PING
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: David Dagon <dagon@cc.gatech.edu>
• Re: dnscurve -- new or did I just miss this?
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Repeat queries to non-deterministic servers
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] DNSKEY / multiprecision number format?
  • From: Dean Anderson <dean@av8.com>
• Re: dnscurve -- new or did I just miss this?
  • From: list-namedroppers@pwns.ms
• Re: dnscurve -- new or did I just miss this?
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: dnscurve -- new or did I just miss this?
  • From: list-namedroppers@pwns.ms
• Re: dnscurve -- new or did I just miss this?
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: Zone Immortality
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• dnscurve -- new or did I just miss this?
  • From: David Ulevitch <davidu@everydns.net>
• Re: Protecting caches?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: list-namedroppers@pwns.ms
• Re: Defending against the Kaminsky attack
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Possible materials for meeting in Minneapolis?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: nonce label prefix (was Re: More 0x20 craziness)
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Paul Vixie <vixie@isc.org>
• Re: Protecting caches?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: nonce label prefix (was Re: More 0x20 craziness)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: nonce label prefix (was Re: More 0x20 craziness)
  • From: Ray.Bellis@nominet.org.uk
• Re: Protecting caches?
  • From: Paul Vixie <vixie@isc.org>
• Re: Protecting caches?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Protecting caches?
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Alex Bligh <alex@alex.org.uk>
• Re: nonce label prefix (was Re: More 0x20 craziness)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: Possible materials for meeting in Minneapolis?
  • From: Paul Vixie <vixie@isc.org>
• Re: nonce label prefix (was Re: More 0x20 craziness)
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Paul Vixie <vixie@isc.org>
• Re: Protecting caches?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Possible materials for meeting in Minneapolis?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• nonce label prefix (was Re: More 0x20 craziness)
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: More 0x20 craziness
  • From: Alex Bligh <alex@alex.org.uk>
• Re: More 0x20 craziness
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Florian Weimer <fweimer@bfk.de>
• Re: kaminsky resistance, section by section
  • From: Paul Vixie <vixie@isc.org>
• Re: kaminsky resistance, section by section
  • From: Tony Finch <dot@dotat.at>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Paul Vixie <vixie@isc.org>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Florian Weimer <fweimer@bfk.de>
• Re: More 0x20 craziness
  • From: Alex Bligh <alex@alex.org.uk>
• Re: More 0x20 craziness
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Paul Vixie <vixie@isc.org>
• Re: Defending against the Kaminsky attack
  • From: Paul Vixie <vixie@isc.org>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Paul Vixie <vixie@isc.org>
• Re: More 0x20 craziness
  • From: Ray.Bellis@nominet.org.uk
• Re: More 0x20 craziness
  • From: Evan Hunt <Evan_Hunt@isc.org>
• Re: More 0x20 craziness
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: More 0x20 craziness
  • From: Mohsen Souissi <mohsen.souissi@nic.fr>
• Re: More 0x20 craziness
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: More 0x20 craziness
  • From: Alex Bligh <alex@alex.org.uk>
• Re: More 0x20 craziness
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: More 0x20 craziness
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: More 0x20 craziness
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• More 0x20 craziness
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defending against the Kaminsky attack
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Stupid questions on stub resolvers...
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Ray.Bellis@nominet.org.uk
• Re: Protecting caches?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Paul Vixie <vixie@isc.org>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: kaminsky resistance, section by section
  • From: Paul Vixie <vixie@isc.org>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Paul Vixie <vixie@isc.org>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Ray.Bellis@nominet.org.uk
• kaminsky resistance, section by section
  • From: Paul Vixie <vixie@isc.org>
• Re: REMINDER: rfc2672bis WGLC expiring!
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: resolver side mitigation
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Jim Reid <jim@rfc1035.com>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• REMINDER: rfc2672bis WGLC expiring!
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Stupid questions on stub resolvers...
  • From: David Conrad <drc@virtualized.org>
• Re: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Jim Reid <jim@rfc1035.com>
• Re: resolver side mitigation
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Stupid questions on stub resolvers...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Fwd: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: resolver side mitigation
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: EDNS PING first draft uploaded
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Protecting caches?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: SCTP (and DCCP)
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Treatment of Bad IDs in entropy calculation
  • From: David Dagon <dagon@cc.gatech.edu>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Treatment of Bad IDs in entropy calculation
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Treatment of Bad IDs in entropy calculation
  • From: Evan Hunt <Evan_Hunt@isc.org>
• Treatment of Bad IDs in entropy calculation
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Defining defense levels...
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: resolver side mitigation
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: resolver side mitigation
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: resolver side mitigation
  • From: Florian Weimer <fweimer@bfk.de>
• Re: resolver side mitigation
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: resolver side mitigation
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Defining defense levels...
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Some Observations on Entropy Re: Some observations on dns-0x20
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Zone Immortality
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Zone Immortality
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Defining defense levels...
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Publication request for draft-ietf-dnsext-forgery-resilience-07.txt
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Agile countermeasures
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Agile countermeasures
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Defining defense levels...
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• resolver side mitigation
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: Agile countermeasures
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Agile countermeasures
  • From: Paul Vixie <vixie@isc.org>
• Re: Agile countermeasures
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Agile countermeasures
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: SCTP (and DCCP)
  • From: Paul Vixie <vixie@isc.org>
• Re: SCTP (and DCCP)
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Agile countermeasures
  • From: Paul Vixie <vixie@isc.org>
• Re: Agile countermeasures
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Agile countermeasures
  • From: Paul Vixie <vixie@isc.org>
• Re: Agile countermeasures
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Defining defense levels...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defending against the Kaminsky attack
  • From: Paul Vixie <vixie@isc.org>
• Re: Defining defense levels...
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Defining defense levels...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Defining defense levels...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: Active countermeasures (threat or danger?)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Defining defense levels...
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Active countermeasures (threat or danger?)
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Defining defense levels...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: SCTP (and DCCP)
  • From: Paul Vixie <vixie@isc.org>
• Defending against the Kaminsky attack
  • From: "George Barwood" <george@emsv.co.uk>
• Re: SCTP (and DCCP)
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: SCTP (and DCCP)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: SCTP (and DCCP)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: SCTP (and DCCP)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: SCTP (and DCCP)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: SCTP (and DCCP)
  • From: Michael Renner <robe@amd.co.at>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Agile countermeasures
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: Agile countermeasures
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Agile countermeasures
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• how to spoof . by Kaminsky's method (Re: Agile countermeasures)
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Agile countermeasures
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: SCTP (and DCCP)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: SCTP (and DCCP)
  • From: Paul Vixie <vixie@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Mohsen Souissi <mohsen.souissi@nic.fr>
• Re: SCTP (and DCCP)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Some Observations on Entropy Re: Some observations on dns-0x20
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• SCTP (and DCCP)
  • From: Paul Vixie <vixie@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Zone Immortality
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Zone Immortality
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Zone Immortality
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Zone Immortality
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Ray.Bellis@nominet.org.uk
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Paul Vixie <vixie@isc.org>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Mohsen Souissi <mohsen.souissi@nic.fr>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Florian Weimer <fweimer@bfk.de>
• Re: deprecating dangerous bit patterns and non-TC non-AXFR
  • From: Paul Vixie <vixie@isc.org>
• Some observations on dns-0x20
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Some observations on dns-0x20
  • From: "George Barwood" <george@emsv.co.uk>
• Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Scott Rose <scottr@nist.gov>
• Text added to DNAME-bis draft Section 3.4
  • From: Scott Rose <scottr@nist.gov>
• EDNS PING first draft uploaded
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: A note of apology (Was: Kaminsky, Cache Poisoning, and Censorship)
  • From: Dean Anderson <dean@av8.com>
• Re: Kaminsky, Cache Poisoning, and Censorship
  • From: Dean Anderson <dean@av8.com>
• A note of apology (Was: Kaminsky, Cache Poisoning, and Censorship)
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Working Group Last Call for draft-ietf-dnsext-dnssec-rsasha256-05
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-07.txt
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D Action:draft-ietf-dnsext-forgery-resilience-07.txt
  • From: Internet-Drafts@ietf.org
• Re: Kaminsky, Cache Poisoning, and Censorship
  • From: Brian Dickson <briand@ca.afilias.info>
• Kaminsky, Cache Poisoning, and Censorship
  • From: Dean Anderson <dean@av8.com>
• Re: Working Group Last Call for draft-ietf-dnsext-rfc2672bis-dname-14
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Duane at e164 dot org <duane@e164.org>
• Why Kaminsky's variation is not so serious, or ...
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: transfering vs. loading a zone
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: transfering vs. loading a zone
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Paul Vixie <vixie@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Duane at e164 dot org <duane@e164.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jim Fenton <fenton@cisco.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: "David W. Hankins" <David_Hankins@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@vacation.karoshi.com
• Re: transfering vs. loading a zone
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Ray.Bellis@nominet.org.uk
• Re: DNSSEC on autopilot (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: transfering vs. loading a zone
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: Dealing with the NS RRSet [Re: Why *can* cached DNS replies be overwritten?]
  • From: Tony Finch <dot@dotat.at>
• Re: transfering vs. loading a zone
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: DNSSEC on autopilot (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: transfering vs. loading a zone
  • From: Mark Andrews <Mark_Andrews@isc.org>
• DNSSEC and alternatives
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSSEC on autopilot (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Otmar Lendl <lendl@nic.at>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Dean Anderson <dean@av8.com>
• Re: WGLC summary for draft-ietf-dnsext-forgery-resilience
  • From: Peter Koch <pk@DENIC.DE>
• Re: Dealing with the NS RRSet [Re: Why *can* cached DNS replies be overwritten?]
  • From: Peter Koch <pk@DENIC.DE>
• Re: Why *can* cached DNS replies be overwritten?
  • From: Paul Vixie <vixie@isc.org>
• Re: Dealing with the NS RRSet [Re: Why *can* cached DNS replies be overwritten?]
  • From: Florian Weimer <fweimer@bfk.de>
• Re: DNSSEC on autopilot (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• DNSSEC on autopilot (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Otmar Lendl <lendl@nic.at>
• transfering vs. loading a zone
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Havard Eidnes <he@uninett.no>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Tony Finch <dot@dotat.at>
• request for draft-crocker-dnssec-algo-signal-01 to become WG item
  • From: Scott Rose <scottr@nist.gov>
• Re: Dealing with the NS RRSet [Re: Why *can* cached DNS replies be overwritten?]
  • From: Tony Finch <dot@dotat.at>
• Dealing with the NS RRSet [Re: Why *can* cached DNS replies be overwritten?]
  • From: Peter Koch <pk@DENIC.DE>
• RE: Why *can* cached DNS replies be overwritten?
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Why *can* cached DNS replies be overwritten?
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Why *can* cached DNS replies be overwritten?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Michael StJohns <mstjohns@comcast.net>
• Why *can* cached DNS replies be overwritten?
  • From: "Jay R. Ashworth" <jra@baylink.com>
• Re: how many angels can dance on the head of a pin?
  • From: bmanning@vacation.karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: Paul Vixie <vixie@isc.org>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Danny Mayer <mayer@gis.net>
• Re: how many angels can dance on the head of a pin?
  • From: Paul Vixie <vixie@isc.org>
• Re: how many angels can dance on the head of a pin?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: how many angels can dance on the head of a pin?
  • From: Ben Laurie <ben@links.org>
• Re: how many angels can dance on the head of a pin?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: how many angels can dance on the head of a pin?
  • From: Ben Laurie <ben@links.org>
• Re: how many angels can dance on the head of a pin?
  • From: sthaug@nethelp.no
• Re: how many angels can dance on the head of a pin?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: how many angels can dance on the head of a pin?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: how many angels can dance on the head of a pin?
  • From: Duane at e164 dot org <duane@e164.org>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: Alex Bligh <alex@alex.org.uk>
• Re: how many angels can dance on the head of a pin?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: sthaug@nethelp.no
• Re: how many angels can dance on the head of a pin?
  • From: Duane at e164 dot org <duane@e164.org>
• how many angels can dance on the head of a pin?
  • From: bmanning@vacation.karoshi.com
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Ben Laurie <ben@links.org>
• Re: Please stop this thread (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: David Conrad <drc@virtualized.org>
• Re: list policies
  • From: Duane at e164 dot org <duane@e164.org>
• Re: Please stop this thread (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Matt Larson <mlarson@verisign.com>
• Re: list policies
  • From: bmanning@vacation.karoshi.com
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Otmar Lendl <lendl@nic.at>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: Jeroen Massar <jeroen@unfix.org>
• Please stop this thread (was: OFFTOPIC: DNSSEC groupthink versus improving DNS)
  • From: Andrew Sullivan <ajs@commandprompt.com>
• majordomo is broken
  • From: Mark_Andrews@isc.org
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• DNSEXT/namedroppers list policy
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: first succesful (lab) spoof of a fully source port randomized server reported
  • From: sthaug@nethelp.no
• first succesful (lab) spoof of a fully source port randomized server reported
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Ralf Weber <denic@eng.colt.net>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane at e164 dot org <duane@e164.org>
• Re: Additional filtering of responses
  • From: Peter Koch <pk@DENIC.DE>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane at e164 dot org <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: "Ondřej Surý" <ondrej.sury@nic.cz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: sthaug@nethelp.no
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane at e164 dot org <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane at e164 dot org <duane@e164.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Florian Weimer <fweimer@bfk.de>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Alex Bligh <alex@alex.org.uk>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Ralf Weber <denic@eng.colt.net>
• Re: Additional filtering of responses
  • From: Duane at e164 dot org <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane at e164 dot org <duane@e164.org>
• Re: Additional filtering of responses
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Ralf Weber <denic@eng.colt.net>
• Re: Additional filtering of responses
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: Additional filtering of responses
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: list policies
  • From: Duane at e164 dot org <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: The problem I see with DNSSEC as a potential end user and administrator.
  • From: David Ulevitch <davidu@everydns.net>
• Re: Additional filtering of responses
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Brian Dickson <briand@ca.afilias.info>
• The problem I see with DNSSEC as a potential end user and administrator.
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Additional filtering of responses
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Additional filtering of responses
  • From: Paul Vixie <vixie@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Additional filtering of responses
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: David Conrad <drc@virtualized.org>
• Re: Additional filtering of responses
  • From: Tony Finch <dot@dotat.at>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Forgery resilience idea - wildcard cooperative defense
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Additional filtering of responses
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Forgery resilience idea - wildcard cooperative defense
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Additional filtering of responses
  • From: Tony Finch <dot@dotat.at>
• Re: Additional filtering of responses
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: Forgery resilience idea - wildcard cooperative defense
  • From: Paul Vixie <vixie@isc.org>
• Forgery resilience idea - wildcard cooperative defense
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Additional filtering of responses
  • From: Paul Vixie <vixie@isc.org>
• Re: Additional filtering of responses
  • From: "Roy Arends" <roy@nominet.org.uk>
• RE: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: Additional filtering of responses
  • From: Paul Vixie <vixie@isc.org>
• Re: OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: Duane <duane@e164.org>
• OFFTOPIC: DNSSEC groupthink versus improving DNS
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Additional filtering of responses
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Fwd: New Version Notification for draft-reid-dnsext-aleatoric-00
  • From: Jim Reid <jim@rfc1035.com>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Tony Finch <dot@dotat.at>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Florian Weimer <fweimer@bfk.de>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: Florian Weimer <fweimer@bfk.de>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: IETF-72 DNSEXT draft minutes
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: IETF-72 DNSEXT draft minutes
  • From: Ben Laurie <ben@links.org>
• IETF-72 DNSEXT draft minutes
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: calculating the chance of spoofing an agile source port randomised resolver
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: Florian Weimer <fweimer@bfk.de>
• Re: calculating the chance of spoofing an agile source port randomised resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: calculating the chance of spoofing an agile source port randomised resolver
  • From: Alex Bligh <alex@alex.org.uk>
• Re: calculating the chance of spoofing an agile source port randomised resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: calculating the chance of spoofing an agile source port randomised resolver
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: Large EDNS0 buffer sizes and IPv6
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• calculating the chance of spoofing an agile source port randomised resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: correction! Re: The math of RFC3833.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• NomCom call for volunteers
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Bryan Seitz <seitz@bsd-unix.net>
• Large EDNS0 buffer sizes and IPv6
  • From: Florian Weimer <fweimer@bfk.de>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Florian Weimer <fweimer@bfk.de>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Paul Vixie <vixie@isc.org>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Florian Weimer <fweimer@bfk.de>
• Re: correction! Re: The math of RFC3822.2.2-spoofing a randomising source port resolver
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• correction! Re: The math of kaminsky-spoofing a randomising source port resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Some lighter thoughts..
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: transaction security in the last mile
  • From: Duane <duane@e164.org>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Danny Mayer <mayer@gis.net>
• Re: The math of kaminsky-spoofing a randomising source port resolver
  • From: Alex Bligh <alex@alex.org.uk>
• The math of kaminsky-spoofing a randomising source port resolver
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNS-spoofing
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: DNS-spoofing
  • From: Andrew Sullivan <ajs@commandprompt.com>
• DNS-spoofing
  • From: Patrik Wallstrom <pawal@blipp.com>
• Working Group Last Call for draft-ietf-dnsext-rfc2672bis-dname-14
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Bruce Campbell <bc-namedroppers@vicious.dropbear.id.au>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: bmanning@vacation.karoshi.com
• Re: increasing DNS message entropy, a solution for NATs
  • From: bmanning@vacation.karoshi.com
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ray.Bellis@nominet.org.uk
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: bmanning@vacation.karoshi.com
• Re: increasing DNS message entropy, a solution for NATs
  • From: Antoin Verschuren <antoin.verschuren@sidn.nl>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ray.Bellis@nominet.org.uk
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ray.Bellis@nominet.org.uk
• Re: increasing DNS message entropy, a solution for NATs
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Ben Laurie <ben@links.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Ben Laurie <ben@links.org>
• Proposed addition to dnssec-bis-updated: CD bit
  • From: "Blacka, David" <davidb@verisign.com>
• Proposed addition for dnssec-bis-updates: AD bit
  • From: "Blacka, David" <davidb@verisign.com>
• Re: XQID (Re: Forgery Resistance phase #2 )
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: XQID (Re: Forgery Resistance phase #2 )
  • From: Paul Vixie <vixie@isc.org>
• I-D Action:draft-ietf-dnsext-forgery-resilience-06.txt
  • From: Internet-Drafts@ietf.org
• Re: WGLC summary for draft-ietf-dnsext-forgery-resilience
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: XQID (Re: Forgery Resistance phase #2 )
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: XQID (Re: Forgery Resistance phase #2 )
  • From: Paul Vixie <vixie@isc.org>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: New version of draft-ietf-dnsext-rfc2672bis-dname available
  • From: Paul Vixie <vixie@isc.org>
• Re: XQID (Re: Forgery Resistance phase #2 )
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: New version of draft-ietf-dnsext-rfc2672bis-dname available
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Forgery resilience: straw man proposal
  • From: Alex Bligh <alex@alex.org.uk>
• Forgery resilience: straw man proposal
  • From: Alex Bligh <alex@alex.org.uk>
• XQID (Re: Forgery Resistance phase #2 )
  • From: Paul Vixie <vixie@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Alex Bligh <alex@alex.org.uk>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Alex Bligh <alex@alex.org.uk>
• RE: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: Forgery Resistance phase #2
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: I-D Action:draft-ietf-dnsext-dnssec-rsasha256-05.txt
  • From: "Scott Rose" <scottr@nist.gov>
• Re: I-D Action:draft-ietf-dnsext-dnssec-rsasha256-05.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• I-D Action:draft-ietf-dnsext-dnssec-rsasha256-05.txt
  • From: Internet-Drafts@ietf.org
• Re: Forgery Resistance phase #2
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: "Paul Ferguson" <fergdawg@netzero.net>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Patrik Fältström <paf@cisco.com>
• Re: Forgery Resistance phase #2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Richard Johnson <raj@cisco.com>
• Re: Forgery Resistance phase #2
  • From: Alex Bligh <alex@alex.org.uk>
• Forgery Resistance phase #2
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@vacation.karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Peter Koch <pk@DENIC.DE>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@vacation.karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@vacation.karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@vacation.karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• New agenda posted
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@karoshi.com
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bmanning@karoshi.com
• DNS exploit in the wild
  • From: Duane <duane@e164.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Tony Finch <dot@dotat.at>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: David Conrad <drc@virtualized.org>
• Re: How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Alex Bligh <alex@alex.org.uk>
• How do we get the whole world to upgrade to DNSSEC capable resolvers?
  • From: Ben Laurie <ben@links.org>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Paul Vixie <paul@vix.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Alex Bligh <alex@alex.org.uk>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Paul Vixie <paul@vix.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Brian Dickson <briand@ca.afilias.info>
• please adopt http://tools.ietf.org/html/draft-vixie-dnsext-dns0x20
  • From: Paul Vixie <paul@vix.com>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Tony Finch <dot@dotat.at>
• Re: ignoring icmp to make dtls work for the stub/RDNS relationship
  • From: "Roy Arends" <roy@nominet.org.uk>
• ignoring icmp to make dtls work for the stub/RDNS relationship
  • From: Paul Vixie <paul@vix.com>
• Re: there is a leak: message entropy increase urgent
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: there is a leak: message entropy increase urgent
  • From: Paul Vixie <paul@vix.com>
• Re: there is a leak: message entropy increase urgent
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Alex Bligh <alex@alex.org.uk>
• Re: there is a leak: message entropy increase urgent
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Alex Bligh <alex@alex.org.uk>
• there is a leak: message entropy increase urgent
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Doug Barton <dougb@dougbarton.us>
• Re: dns hop by hop transaction security for queries
  • From: David Conrad <drc@virtualized.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Paul Vixie <paul@vix.com>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Duane <duane@e164.org>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: increasing DNS message entropy, a solution for NATs
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: increasing DNS message entropy, a solution for NATs
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: increasing DNS message entropy, a solution for NATs
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: increasing DNS message entropy, a solution for NATs
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: transaction security in the last mile
  • From: Tony Finch <dot@dotat.at>
• Re: increasing DNS message entropy, a solution for NATs
  • From: Paul Vixie <paul@vix.com>
• Re: increasing DNS message entropy, a solution for NATs
  • From: bmanning@vacation.karoshi.com
• Re: increasing DNS message entropy, a solution for NATs
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: dns hop by hop transaction security for queries
  • From: "Donald Eastlake" <d3e3e3@gmail.com>
• Re: transaction security in the last mile
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: dns hop by hop transaction security for queries
  • From: Tony Finch <dot@dotat.at>
• increasing DNS message entropy, a solution for NATs
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: dns hop by hop transaction security for queries
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: "Donald Eastlake" <d3e3e3@gmail.com>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: dns hop by hop transaction security for queries
  • From: Duane <duane@e164.org>
• Re: dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: dns hop by hop transaction security for queries
  • From: Alex Bligh <alex@alex.org.uk>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: Eric Rescorla <ekr@networkresonance.com>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• dns hop by hop transaction security for queries
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: transaction security in the last mile
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: Alex Bligh <alex@alex.org.uk>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: transaction security in the last mile
  • From: Duane <duane@e164.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Duane <duane@e164.org>
• Re: transaction security in the last mile
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Duane <duane@e164.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul@vix.com>
• Re: transaction security in the last mile
  • From: David Ulevitch <davidu@everydns.net>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: David Ulevitch <davidu@everydns.net>
• Re: transaction security in the last mile
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: transaction security in the last mile
  • From: David Conrad <drc@virtualized.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Ben Laurie <ben@links.org>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: transaction security in the last mile
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: David Conrad <drc@virtualized.org>
• Re: transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: transaction security in the last mile
  • From: David Ulevitch <davidu@everydns.net>
• Re: transaction security in the last mile
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: transaction security in the last mile
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: transaction security in the last mile
  • From: David Conrad <drc@virtualized.org>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: IPv4 and IPv6 Co-existence discussions in Dublin
  • From: Alain Durand <alain_durand@cable.comcast.com>
• Re: transaction security in the last mile
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul_vixie@isc.org>
• Re: transaction security in the last mile
  • From: Florian Weimer <fw@deneb.enyo.de>
• WGLC summary for draft-ietf-dnsext-forgery-resilience
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: transaction security in the last mile
  • From: Paul Vixie <paul_vixie@isc.org>
• Re: transaction security in the last mile
  • From: Alex Bligh <alex@alex.org.uk>
• IPv4 and IPv6 Co-existence discussions in Dublin
  • From: Mark Townsley <townsley@cisco.com>
• transaction security in the last mile
  • From: Paul Vixie <vixie@isc.org>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: DNS Encryption
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: NSEC design question wrt synthesized RCODE 3 (NXDOMAIN)
  • From: Florian Weimer <fw@deneb.enyo.de>
• Updated draft-groth-dns-encryption
  • From: Duane <duane@e164.org>
• Re: New version of draft-ietf-dnsext-rfc2672bis-dname available
  • From: Andrew Sullivan <ajs@commandprompt.com>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-14.txt
  • From: Internet-Drafts@ietf.org
• New version of draft-ietf-dnsext-rfc2672bis-dname available
  • From: Scott Rose <scottr@nist.gov>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: DNS Encryption
  • From: David Shaw <dshaw@jabberwocky.com>
• Re: DNS Encryption
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: Out of the blue... Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: Out of the blue... Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Fwd: I-D ACTION:draft-ietf-dnsext-2929bis-07.txt
  • From: "Donald Eastlake" <d3e3e3@gmail.com>
• I-D Action:draft-ietf-dnsext-dnssec-trans-06.txt
  • From: Internet-Drafts@ietf.org
• I-D Action:draft-ietf-dnsext-dnssec-bis-updates-07.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-2929bis-07.txt
  • From: Internet-Drafts@ietf.org
• I-D ACTION:draft-ietf-dnsext-axfr-clarify-09.txt
  • From: Internet-Drafts@ietf.org
• Draft agenda for IETF 72 meeting
  • From: Andrew Sullivan <ajs@commandprompt.com>
• -09 of AXFR clarify submitted
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Out of the blue... Re: DNS Encryption
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNS Encryption
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: DNS Encryption
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: DNS Encryption
  • From: Duane <duane@e164.org>
• Re: DNS Encryption
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Peter Koch <pk@DENIC.DE>
• DNS Encryption
  • From: Duane <duane@e164.org>
• Question on BCP vs Standard (Was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: Question on BCP vs Standard (Was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Question on BCP vs Standard (Was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Vixie <vixie@isc.org>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Florian Weimer <fweimer@bfk.de>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Email change for Donald Eastlake
  • From: "Donald Eastlake" <d3e3e3@gmail.com>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: Issue for discussion in draft-ietf-dnsext-dnssec-rsasha256
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Paul Vixie <paul@vix.com>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Intended status
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Intended status
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: Intended status
  • From: Paul Vixie <paul@vix.com>
• Re: Intended status
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Paul Vixie <paul@vix.com>
• Re: Intended status
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Paul Vixie <paul@vix.com>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Paul Vixie <paul@vix.com>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Scott Rose <scottr@nist.gov>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Paul Vixie <paul@vix.com>
• Logical inconsistencies in draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Paul Vixie <paul@vix.com>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Paul Vixie <paul@vix.com>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Intended status (Was: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers")
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Scott Rose <scottr@nist.gov>
• I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-00.txt
  • From: Internet-Drafts@ietf.org
• Re: NSEC design question wrt synthesized RCODE 3 (NXDOMAIN)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: NSEC design question wrt synthesized RCODE 3 (NXDOMAIN)
  • From: "Blacka, David" <davidb@verisign.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Vixie <paul@vix.com>
• NSEC design question wrt synthesized RCODE 3 (NXDOMAIN)
  • From: Paul Vixie <paul@vix.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Vixie <paul@vix.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Tony Finch <dot@dotat.at>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Tony Finch <dot@dotat.at>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Vixie <paul@vix.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Paul Vixie <paul@vix.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Scott Rose <scottr@nist.gov>
• Re: Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Vixie <paul@vix.com>
• Name sensitivity, was Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Requirements levels in draft-ietf-dnsext-forgery-resilience-05.txt
  • From: Olafur Gudmundsson <ogud@ogud.com>
• DNSEXT WGLC: "Measures for making DNS more resilient against forged answers"
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Michael StJohns <mstjohns@comcast.net>
• Requirements levels in draft-ietf-dnsext-forgery-resilience-05.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D Action:draft-ietf-dnsext-forgery-resilience-05.txt
  • From: Internet-Drafts@ietf.org
• Re: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Scott Rose <scottr@nist.gov>
• RE: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Michael StJohns <mstjohns@comcast.net>
• RE: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• RE: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: "Scott Rose" <scottr@nist.gov>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Suresh Krishnaswamy <suresh@sparta.com>
• Re: new draft of Forgery Resilience posted - summary of changes
  • From: Olafur Gudmundsson <ogud@ogud.com>
• new draft of Forgery Resilience posted - summary of changes
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D Action:draft-ietf-dnsext-forgery-resilience-04.txt
  • From: Internet-Drafts@ietf.org
• Re: [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Happy Birthday: DNS is 25 years old
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Happy Birthday: DNS is 25 years old
  • From: Wes Hardaker <wjhns1@hardakers.net>
• Happy Birthday: DNS is 25 years old
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [Fwd: New Version Notification for draft-crocker-dnssec-algo-signal-00]
  • From: Scott Rose <scottr@nist.gov>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: Issue for discussion in draft-ietf-dnsext-dnssec-rsasha256
  • From: Scott Rose <scottr@nist.gov>
• Re: Issue for discussion in draft-ietf-dnsext-dnssec-rsasha256
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Issue for discussion in draft-ietf-dnsext-dnssec-rsasha256
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: another open question on AXFR clarify
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Issue for discussion in draft-ietf-dnsext-dnssec-rsasha256
  • From: Andrew Sullivan <ajs@commandprompt.com>
• more "reactions" Re: review of draft-ietf-dnsext-axfr-clarify-08
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR open question
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• suggestion 5e Re: review of draft-ietf-dnsext-axfr-clarify-08
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• another open question on AXFR clarify
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: AXFR open question
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Vixie <paul@vix.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Patrik Fältström <paf@cisco.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Vixie <paul@vix.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Patrik Fältström <paf@cisco.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Vixie <paul@vix.com>
• Re: review of draft-ietf-dnsext-axfr-clarify-08
  • From: Alfred Hönes <ah@tr-sys.de>
• AXFR open question
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: review of draft-ietf-dnsext-axfr-clarify-08
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Clarification questions for trust anchor handling
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Agenda for IETF 72
  • From: Andrew Sullivan <ajs@commandprompt.com>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Vixie <paul@vix.com>
• Re: Editors change dnssec-bis-update
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Editors change dnssec-bis-update
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Frederico A C Neves <fneves@registro.br>
• Re: I-D ACTION:draft-hayatnagarkar-dnsext-validator-api-06.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Clarification questions for trust anchor handling
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Clarification questions for trust anchor handling
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: Clarification questions for trust anchor handling
  • From: bmanning@vacation.karoshi.com
• Re: Clarification questions for trust anchor handling
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Clarification questions for trust anchor handling
  • From: roy@nominet.org.uk
• Re: Clarification questions for trust anchor handling
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Clarification questions for trust anchor handling
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Clarification questions for trust anchor handling
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Clarification questions for trust anchor handling
  • From: roy@nominet.org.uk
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: Confusion about trust anchors and DS records from the parent?
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Clarification questions for trust anchor handling
  • From: Andrew Sullivan/dnsext co-chair <ajs@commandprompt.com>
• review of draft-ietf-dnsext-axfr-clarify-08
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: expired draft
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: expired draft
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: expired draft
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• expired draft
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: bmanning@vacation.karoshi.com
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Peter Koch <pk@DENIC.DE>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Peter Koch <pk@DENIC.DE>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: David Blacka <davidb@verisign.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Vixie <paul@vix.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Frederico A C Neves <fneves@registro.br>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Patrik Fältström <paf@cisco.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Confusion about trust anchors and DS records from the parent?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Confusion about trust anchors and DS records from the parent?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Adoption of draft-dupont-dnsext-tsig-md5-deprecated
  • From: Andrew Sullivan/dnsext co-chair <ajs@commandprompt.com>
• Re: Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Alfred Hönes <ah@tr-sys.de>
• comment #2 Re: draft-ietf-dnsext-axfr-clarify-08.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-axfr-clarify-08.txt
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: draft-ietf-dnsext-axfr-clarify-08.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• I-D ACTION:draft-ietf-dnsext-axfr-clarify-08.txt
  • From: Internet-Drafts@ietf.org
• Re: rsa/sha2 draft status
  • From: Scott Rose <scottr@nist.gov>
• I-D ACTION:draft-ietf-dnsext-axfr-clarify-08.txt
  • From: Internet-Drafts@ietf.org
• Re: rsa/sha2 draft status
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• rsa/sha2 draft status
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Peter Koch <pk@DENIC.DE>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: DNSSEC Validator API Draft - 06
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: DNSSEC Validator API Draft - 06
  • From: Alex Bligh <alex@alex.org.uk>
• DNSSEC Validator API Draft - 06
  • From: Suresh Krishnaswamy <suresh@sparta.com>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Joe Abley <jabley@ca.afilias.info>
• Review of draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Peter Koch <pk@DENIC.DE>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Patrik Fältström <paf@cisco.com>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: "Roy Arends" <roy@nominet.org.uk>
• Adopt draft-dupont-dnsext-tsig-md5-deprecated as WG draft?
  • From: Andrew Sullivan <ajs@commandprompt.com>
• Re: Meeting at IETF-71 in Dublin
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• RE: Meeting at IETF-71 in Dublin
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Meeting at IETF-71 in Dublin
  • From: Scott Rose <scottr@nist.gov>
• Re: Meeting at IETF-71 in Dublin
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Meeting at IETF-71 in Dublin
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Please welcome Andrew Sullivan as DNSEXT Co-Chair
  • From: Mark Townsley <townsley@cisco.com>
• Re: TCP mandatory? Re: DNS is mandatory text
  • From: Paul Vixie <paul@vix.com>
• Re: DNS is mandatory text
  • From: Danny Mayer <mayer@gis.net>
• Re: TCP mandatory? Re: DNS is mandatory text
  • From: Dean Anderson <dean@av8.net>
• Re: how to deprecate HMAC-MD5 TSIG
  • From: Scott Rose <scottr@nist.gov>
• Re: how to deprecate HMAC-MD5 TSIG
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• how to deprecate HMAC-MD5 TSIG
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: DNS is mandatory text
  • From: bmanning@vacation.karoshi.com
• Re: DNS is mandatory text
  • From: Paul Vixie <paul@vix.com>
• draft-ietf-dnsext-rfc2672bis-dname-13 -- another iteration
  • From: Alfred Hönes <ah@tr-sys.de>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-13.txt
  • From: Internet-Drafts@ietf.org
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: "Roy Arends" <roy@nominet.org.uk>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: "Roy Arends" <roy@nominet.org.uk>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: bmanning@vacation.karoshi.com
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Paul Vixie <paul@vix.com>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• draft-ietf-dnsext-rfc2672bis-dname-12
  • From: Alfred Hönes <ah@tr-sys.de>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Joe Abley <jabley@ca.afilias.info>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Paul Vixie <paul@vix.com>
• RE: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Paul Vixie <paul@vix.com>
• Re: Anti DNS spoofing - Extended Query ID (XQID)
  • From: Florian Weimer <fweimer@bfk.de>
• Anti DNS spoofing - Extended Query ID (XQID)
  • From: Jesper G. Høy <jesper@jhsoft.com>
• Re: Some musings on forgery resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Some musings on forgery resilience
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Some musings on forgery resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Some musings on forgery resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Some musings on forgery resilience
  • From: Otmar Lendl <lendl@nic.at>
• Re: Some musings on forgery resilience
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: Some musings on forgery resilience
  • From: Paul Vixie <paul@vix.com>
• Re: Some musings on forgery resilience
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Some musings on forgery resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Some musings on forgery resilience
  • From: Jim Reid <jim@rfc1035.com>
• Re: Some musings on forgery resilience
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Some musings on forgery resilience
  • From: Otmar Lendl <lendl@nic.at>
• draft-ietf-dnsext-rfc2672bis-dname-12
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-12.txt
  • From: Internet-Drafts@ietf.org
• Re: draft-ietf-dnsext-forgery-resilience-03
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNS is mandatory text
  • From: Peter Koch <pk@DENIC.DE>
• Re: DNS is mandatory text
  • From: Danny Mayer <mayer@gis.net>
• Re: DNS is mandatory text
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNS is mandatory text
  • From: Peter Koch <pk@DENIC.DE>
• Re: I-D Action:draft-ietf-dnsext-dnssec-rsasha256-04.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• I-D Action:draft-ietf-dnsext-dnssec-rsasha256-04.txt
  • From: Internet-Drafts@ietf.org
• [Fwd: [Int-area] TSVWG last call on "UDP Usage Guidelines for Application Designers" to BCP]
  • From: Danny Mayer <mayer@gis.net>
• Mr. Secure64...
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: I-D Action:draft-ietf-dnsext-rfc2672bis-dname-11.txt
  • From: Kevin Darcy <kcd@chrysler.com>
• draft-ietf-dnsext-rfc2672bis-dname-09 UD definition placement
  • From: Alfred Hönes <ah@tr-sys.de>
• draft-ietf-dnsext-rfc2672bis-dname-11 -- fate of 2672 ??
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: I-D Action:draft-ietf-dnsext-rfc2672bis-dname-11.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• draft-ietf-dnsext-forgery-resilience-03
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• dname-bis -11 draft submitted
  • From: Scott Rose <scottr@nist.gov>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-11.txt
  • From: Internet-Drafts@ietf.org
• Re: diff between -02 and -03 of forgery-resilience
  • From: Paul Vixie <paul@vix.com>
• Re: OPT RR placement
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: diff between -02 and -03 of forgery-resilience
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: OPT RR placement
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: OPT RR placement
  • From: Brandon Black <blblack@gmail.com>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: OPT RR placement
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Paul Vixie <paul@vix.com>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Robert Elz <kre@munnari.OZ.AU>
• OPT RR placement
  • From: Brandon Black <blblack@gmail.com>
• RE: diff between -02 and -03 of forgery-resilience
  • From: Yue Luo <yueluo@windows.microsoft.com>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Paul Vixie <paul@vix.com>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: diff between -02 and -03 of forgery-resilience
  • From: Paul Vixie <paul@vix.com>
• diff between -02 and -03 of forgery-resilience
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D Action:draft-ietf-dnsext-forgery-resilience-03.txt
  • From: Internet-Drafts@ietf.org
• Re: Is there already an implementation of RSA-SHA2 for DNSSEC?
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Is there already an implementation of RSA-SHA2 for DNSSEC?
  • From: Yue Luo <yueluo@windows.microsoft.com>
• Re: the birth of DNSSEC
  • From: Alex Bligh <alex@alex.org.uk>
• the birth of DNSSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: thinking about authority and additional sections in recursive answers
  • From: Paul Vixie <paul@vix.com>
• review of draft-gudmundsson-life-of-dnskey-00.txt
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: thinking about authority and additional sections in recursive answers
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: Patrik Fältström <paf@cisco.com>
• Re: thinking about authority and additional sections in recursive answers
  • From: Mark Andrews <Mark_Andrews@isc.org>
• thinking about authority and additional sections in recursive answers
  • From: Paul Vixie <paul@vix.com>
• TCP "Road Map"
  • From: Mark Townsley <townsley@cisco.com>
• I-D Action:draft-ietf-dnsext-rfc2671bis-edns0-01.txt
  • From: Internet-Drafts@ietf.org
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: DNS is mandatory text
  • From: Paul Vixie <paul@vix.com>
• draft-vixie-dnsext-dns0x20-00
  • From: Paul Vixie <paul@vix.com>
• RE: Comments on dns-cookies draft vs. amplification attacks
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: Paul Vixie <paul@vix.com>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Forgery Resilience consensus call: Qname case sensitivity
  • From: Yue Luo <yueluo@windows.microsoft.com>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: Paul Vixie <paul@vix.com>
• Re: Forgery Resilience consensus call: Qname case sensitivity
  • From: Brian Dickson <briand@ca.afilias.info>
• Forgery Resilience consensus call: Qname case sensitivity
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• dns-0x20 fished out of the ashes
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: dnsext-forgery-resilience-02
  • From: bmanning@vacation.karoshi.com
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Danny Mayer <mayer@gis.net>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Thomas Narten <narten@us.ibm.com>
• Re: dear wg: 0x20 safe to mandate or not? Time limit?
  • From: Paul Vixie <paul@vix.com>
• Re: dear wg: 0x20 safe to mandate or not? Time limit?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dear wg: 0x20 safe to mandate or not? Time limit?
  • From: Paul Vixie <paul@vix.com>
• dear wg: 0x20 safe to mandate or not? Time limit?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dnsext-forgery-resilience-02
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dnsext-forgery-resilience-02
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: dnsext-forgery-resilience-02
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dnsext-forgery-resilience-02
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: dnsext-forgery-resilience-02
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20 mismatches
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dnsext-forgery-resilience-02
  • From: Ben Laurie <ben@links.org>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: DNS is mandatory text
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• RE: DNS is mandatory text
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: dns-0x20 mismatches
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Michael Graff <michael_graff@isc.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Florian Weimer <fweimer@bfk.de>
• Re: DNS is mandatory text
  • From: Måns Nilsson <mansaxel@kthnoc.net>
• Re: dns-0x20 mismatches
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: dns-0x20 mismatches
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: dns-0x20 mismatches
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Michael Graff <explorer@flame.org>
• Re: dns-0x20 mismatches
  • From: Michael Graff <michael_graff@isc.org>
• Re: dns-0x20 mismatches
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Josh Littlefield <joshl@cisco.com>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Michael Graff <michael_graff@isc.org>
• Re: dns-0x20 mismatches
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: dns-0x20 mismatches
  • From: Michael Graff <explorer@flame.org>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: DNS is mandatory text
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20 mismatches
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: dns-0x20 mismatches
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: DNS is mandatory text
  • From: Olafur Gudmundsson <ogud@ogud.com>
• dns-0x20 mismatches
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20 mismatches
  • From: Michael Graff <explorer@flame.org>
• Re: DNS is mandatory text
  • From: Florian Weimer <fweimer@bfk.de>
• Re: dnsext-forgery-resilience-02
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: DNS is mandatory text
  • From: Måns Nilsson <mansaxel@kthnoc.net>
• Re: dnsext-forgery-resilience-02
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNS is mandatory text
  • From: Pekka Savola <pekkas@netcore.fi>
• dnsext-forgery-resilience-02
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: dns-0x20.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Florian Weimer <fweimer@bfk.de>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Florian Weimer <fweimer@bfk.de>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNS is mandatory text
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: David Conrad <drc@virtualized.org>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: top-level domains (was Re: dns-0x20.txt)
  • From: Paul Vixie <paul@vix.com>
• top-level domains (was Re: dns-0x20.txt)
  • From: David Conrad <drc@virtualized.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: dns-0x20.txt
  • From: David Conrad <drc@virtualized.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20.txt
  • From: bmanning@vacation.karoshi.com
• Re: dns-0x20.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: dns-0x20.txt
  • From: David Conrad <drc@virtualized.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNS is mandatory text
  • From: Måns Nilsson <mansaxel@kthnoc.net>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: David Conrad <drc@virtualized.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: DNS is mandatory text
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: dns-0x20.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: DNS is mandatory text
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Florian Weimer <fweimer@bfk.de>
• Re: dns-0x20.txt
  • From: David Dagon <dagon@cc.gatech.edu>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: dns-0x20.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: DNS is mandatory text
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: DNS is mandatory text
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: dns-0x20.txt
  • From: "Blacka, David" <davidb@verisign.com>
• Re: dns-0x20.txt
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Pekka Savola <pekkas@netcore.fi>
• DNS is mandatory text
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: dns-0x20.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: bert hubert <bert.hubert@netherlabs.nl>
• dnssec-bis item, include SOA
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• CD bit setting from intermediate resolvers...
  • From: Michael StJohns <mstjohns@comcast.net>
• conjoining dns-forgery-resilience with dns-0x20; also, rtt banding
  • From: Paul Vixie <paul@vix.com>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Alex Bligh <alex@alex.org.uk>
• birthday attacks
  • From: Steve Crocker <steve@shinkuro.com>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Comments on dns-cookies draft vs. amplification attacks
  • From: Michael Graff <michael_graff@isc.org>
• Fwd: Impending publication: draft-iab-dns-choices-05
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: dns-0x20.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RFC 5155 on DNS Security (DNSSEC) Hashed Authenticated Denial of Existence
  • From: rfc-editor@rfc-editor.org
• Re: edns0-bis submitted
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: George Michaelson <ggm@apnic.net>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: edns-0
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: implications of RFC 2181 on cname chains
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: implications of RFC 2181 on cname chains
  • From: bmanning@vacation.karoshi.com
• Re: implications of RFC 2181 on cname chains
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: implications of RFC 2181 on cname chains
  • From: bmanning@vacation.karoshi.com
• Re: implications of RFC 2181 on cname chains
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: implications of RFC 2181 on cname chains
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: implications of RFC 2181 on cname chains
  • From: Phil Pennock <namedroppers+phil@spodhuis.org>
• Re: implications of RFC 2181 on cname chains
  • From: Paul Vixie <paul@vix.com>
• Re: implications of RFC 2181 on cname chains
  • From: David Blacka <davidb@verisign.com>
• Re: implications of RFC 2181 on cname chains
  • From: Mark Andrews <Mark_Andrews@isc.org>
• implications of RFC 2181 on cname chains
  • From: Paul Vixie <paul@vix.com>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• dns-0x20 section 5.4
  • From: Paul Vixie <paul@vix.com>
• RE: dns-0x20.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• RE: dns-0x20.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: dns-0x20.txt
  • From: bmanning@vacation.karoshi.com
• Re: dns-0x20.txt
  • From: JINMEI Tatuya / 神明達哉 <jinmei@wide.ad.jp>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: JINMEI Tatuya / 神明達哉 <jinmei@wide.ad.jp>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Michael Graff <michael_graff@isc.org>
• Re: edns-0
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: edns-0
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns-0
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dns-0x20.txt
  • From: Jim Reid <jim@rfc1035.com>
• Re: dns-0x20.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: edns-0
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Evan Hunt <Evan_Hunt@isc.org>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: edns0-bis submitted
  • From: Paul Vixie <paul@vix.com>
• Re: DNSEXT@IETF-71 Tue 13:00-15:00
  • From: Paul Vixie <paul@vix.com>
• RE: dns-0x20.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• RE: dns-0x20.txt
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: edns0-bis submitted
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: edns0-bis submitted
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: edns0-bis submitted
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: edns0-bis submitted
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• DNSEXT@IETF-71 Tue 13:00-15:00
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Michael Graff <michael_graff@isc.org>
• Re: edns0-bis submitted
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: edns0-bis submitted
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: dns-0x20.txt
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Phil Pennock <namedroppers+phil@spodhuis.org>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Paul Vixie <paul@vix.com>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Patrik Fältström <paf@cisco.com>
• Re: i'm thinking that EDNS0-bis is just not very sexy
  • From: Brian Dickson <briand@ca.afilias.info>
• i'm thinking that EDNS0-bis is just not very sexy
  • From: Paul Vixie <paul@vix.com>
• Re: dns-0x20.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: dns-0x20.txt
  • From: Roy.Arends@nominet.org.uk
• Re: dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• dns-0x20.txt
  • From: Paul Vixie <paul@vix.com>
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP
  • From: Sam Weiler <weiler@tislabs.com>
• edns0-bis submitted
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2671bis-edns0-00 (fwd)
  • From: Paul Vixie <paul@vix.com>
• Re: EDNS0 (RFC-2671) questions
  • From: Paul Vixie <paul@vix.com>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-10.txt
  • From: Internet-Drafts@ietf.org
• Re: DNSEXT @ IETF-71 action plan and agenda items
  • From: roy@nominet.org.uk
• Re: Last Call: draft-ietf-dnsext-2929bis (Domain Name System (DNS) IANA Considerations) to BCP
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: DNSEXT @ IETF-71 action plan and agenda items
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• RE: notes accompanying -02 of forgery-resilience draft
  • From: Yue Luo <yueluo@windows.microsoft.com>
• Re: DNSEXT @ IETF-71 action plan and agenda items
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• DNSEXT @ IETF-71 action plan and agenda items
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: Florian Weimer <fweimer@bfk.de>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• RE: notes accompanying -02 of forgery-resilience draft
  • From: Yue Luo <yueluo@windows.microsoft.com>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: bert hubert <bert.hubert@netherlabs.nl>
• heads up for NSEC3 software implementers
  • From: roy@nominet.org.uk
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: notes accompanying -02 of forgery-resilience draft
  • From: Alex Bligh <alex@alex.org.uk>
• notes accompanying -02 of forgery-resilience draft
  • From: bert hubert <bert.hubert@netherlabs.nl>
• I-D Action:draft-ietf-dnsext-forgery-resilience-02.txt
  • From: Internet-Drafts@ietf.org
• I-D Action:draft-ietf-dnsext-dnssec-rsasha256-03.txt
  • From: Internet-Drafts@ietf.org
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Paul Vixie <paul@vix.com>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: Resolution of the DNAME via dynamic update issue
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: Resolution of the DNAME via dynamic update issue
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Meeting at IETF-71 ?
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Resolution of the DNAME via dynamic update issue
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: Resolution of the DNAME via dynamic update issue
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Paul Vixie <paul@vix.com>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: Resolution of the DNAME via dynamic update issue
  • From: Paul Vixie <paul@vix.com>
• Resolution of the DNAME via dynamic update issue
  • From: "Scott Rose" <scottr@nist.gov>
• Fwd: I-D ACTION:draft-lewis-axfr-over-udp-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: Paul Vixie <paul@vix.com>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: "Blacka, David" <davidb@verisign.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: Paul Vixie <vixie@isc.org>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: Mark Andrews <Mark_Andrews@isc.org>
• ANY queries in ns resolution: ADDR pseudo-rrtype for IPv4 and IPv6 operation
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR over UDP is available
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: AXFR over UDP is available
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR over UDP is available
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: draft-ietf-dnsext-axfr-clarify-07.txt: 2.1.1 Header Values
  • From: Mark Andrews <Mark_Andrews@isc.org>
• draft-ietf-dnsext-axfr-clarify-07.txt: 2.2 AXFR response
  • From: Mark Andrews <Mark_Andrews@isc.org>
• draft-ietf-dnsext-axfr-clarify-07.txt: 2.1.1 Header Values
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR over UDP is available
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR over UDP is available
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR over UDP is available
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Scott Rose <scottr@nist.gov>
• AXFR over UDP is available
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• I-D ACTION:draft-ietf-dnsext-axfr-clarify-07.txt
  • From: Internet-Drafts@ietf.org
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Paul Vixie <paul@vix.com>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Florian Weimer <fweimer@bfk.de>
• Re: AXFR and TCP
  • From: Florian Weimer <fweimer@bfk.de>
• Re: AXFR and TCP
  • From: Florian Weimer <fweimer@bfk.de>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• call for contributors to the dns-profile document edit process
  • From: George Michaelson <ggm@apnic.net>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt: CNAME synthesis
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-09.txt
  • From: Internet-Drafts@ietf.org
• Re: axfr-clarify-07 and axfr-udp-00 submitted
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Meeting at IETF-71 ?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Meeting at IETF-71 ?
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• axfr-clarify-07 and axfr-udp-00 submitted
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-axfr-clarify-06
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-axfr-clarify-06
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-axfr-clarify-06
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR and TCP
  • From: Ian Jackson <ian@davenant.greenend.org.uk>
• Re: AXFR and TCP
  • From: Ian Jackson <ian@davenant.greenend.org.uk>
• Re: AXFR and TCP
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: AXFR and TCP
  • From: Tony Finch <dot@dotat.at>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR and TCP
  • From: Paul Vixie <paul@vix.com>
• AXFR and TCP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Clarification Request (Truncation)
  • From: Danny Mayer <mayer@gis.net>
• Re: Clarification Request (Truncation)
  • From: Pekka Savola <pekkas@netcore.fi>
• Re: Clarification Request (Truncation)
  • From: Danny Mayer <mayer@gis.net>
• Re: Clarification Request (Truncation)
  • From: Danny Mayer <mayer@ntp.isc.org>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Clarification Request (Truncation)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: updated dname draft-08
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: Clarification Request (Truncation)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: Clarification Request (Truncation)
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Danny Mayer <mayer@gis.net>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Seeking nominations and volunteers for DNSEXT WG Co-Chair
  • From: Mark Townsley <townsley@cisco.com>
• Re: Clarification Request (Truncation)
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: Clarification Request (Truncation)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Clarification Request (Truncation)
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: Clarification Request (Truncation)
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: Clarification Request (Truncation)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: Clarification Request (Truncation)
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Clarification Request (Truncation)
  • From: Kevin Darcy <kcd@chrysler.com>
• Re: AXFR over UDP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR over UDP
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: AXFR over UDP
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: AXFR over UDP
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: AXFR over UDP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Josh Littlefield <joshl@cisco.com>
• Re: AXFR over UDP
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: AXFR over UDP
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: AXFR over UDP
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Status of Dynamic DNS Update Leases
  • From: dan@dcrdev.demon.co.uk
• Re: AXFR over UDP
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: AXFR over UDP
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: AXFR over UDP
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: AXFR over UDP
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR over UDP
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: AXFR over UDP
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: AXFR over UDP
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: AXFR over UDP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: AXFR over UDP
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR over UDP
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: AXFR over UDP
  • From: David Conrad <david.conrad@icann.org>
• Re: AXFR over UDP
  • From: Paul Vixie <paul@vix.com>
• AXFR over UDP
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: DNSEXT list policy (updated)
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• DNS profile document going forward
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Florian Weimer <fweimer@bfk.de>
• DNSEXT list policy (updated)
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Dean Anderson posting privileges revoked.
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Ralf Weber <denic@eng.colt.net>
• Re: IANA "stuff" (was Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt)
  • From: Dean Anderson <dean@av8.com>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: IANA change tracking (Was: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: David Conrad <david.conrad@icann.org>
• Re: IANA change tracking (Was: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: David Conrad <david.conrad@icann.org>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: AXFR "clarify"
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• MUST for the implementation of for the operator? (Was: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Stay on topic we have real work to do
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Thanks to the other commenters on axfr-06
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: IANA change tracking (Was: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• draft-ietf-dnsext-axfr-clarify-06
  • From: Alfred Hönes <ah@tr-sys.de>
• IANA change tracking (Was: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: IANA "stuff" (was Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt)
  • From: Paul Vixie <paul@vix.com>
• Re: IANA "stuff" (was Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt)
  • From: Dean Anderson <dean@av8.com>
• Re: IANA "stuff" (was Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt)
  • From: David Conrad <david.conrad@icann.org>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Dean Anderson <dean@av8.com>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Josh Littlefield <joshl@cisco.com>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: David Conrad <david.conrad@icann.org>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Dean Anderson <dean@av8.com>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Paul Vixie <paul@vix.com>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: David Conrad <david.conrad@icann.org>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: David Conrad <david.conrad@icann.org>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• dropping connections was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Paul Vixie <paul@vix.com>
• Note 2.1.1.b was Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• TSIG was Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR draft on the way
  • From: Brian Dickson <briand@ca.afilias.info>
• In the wake of posting -06
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• I-D ACTION:draft-ietf-dnsext-axfr-clarify-06.txt
  • From: Internet-Drafts@ietf.org
• AXFR draft on the way
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: AXFR "clarify"
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: AXFR "clarify"
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR "clarify"
  • From: Dean Anderson <dean@av8.com>
• Re: AXFR "clarify"
  • From: bmanning@vacation.karoshi.com
• Re: AXFR "clarify"
  • From: Danny Mayer <mayer@gis.net>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR "clarify"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: AXFR "clarify"
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR "clarify"
  • From: bmanning@vacation.karoshi.com
• AXFR message id's
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• draft-ietf-dnsext-dns-protocol-profile-00
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: AXFR "clarify"
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: capitalization was Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR "clarify"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: capitalization was Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• I-D Action:draft-ietf-dnsext-dns-protocol-profile-01.txt
  • From: Internet-Drafts@ietf.org
• version -01 of draft-ietf-dnsext-dns-protocol-profile sent
  • From: George Michaelson <ggm@apnic.net>
• Re: AXFR "clarify"
  • From: Brian Dickson <briand@ca.afilias.info>
• Re: capitalization was Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• capitalization was Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Florian Weimer <fweimer@bfk.de>
• Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: AXFR "clarify"
  • From: Paul Vixie <paul@vix.com>
• Re: AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: AXFR "clarify"
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: DNS protocol profile document effort.
  • From: Sam Weiler <weiler@tislabs.com>
• AXFR "clarify"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Joao Damas <Joao@c-l-i.net>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Federico Lucifredi <flucifredi@ximian.com>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Paul Vixie <vixie@isc.org>
• RE: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: "Scott Rose" <scottr@nist.gov>
• Re: Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Joe Abley <jabley@ca.afilias.info>
• Continue work on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• draft-ietf-dnsext-dns-protocol-profile-00
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: updated dname draft-08
  • From: Paul Vixie <paul@vix.com>
• Re: updated dname draft-08
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: updated dname draft-08
  • From: Wouter Wijngaards <wouter@nlnetlabs.nl>
• Re: updated dname draft-08
  • From: Paul Vixie <paul@vix.com>
• Re: updated dname draft-08
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: updated dname draft-08
  • From: Paul Vixie <paul@vix.com>
• Re: updated dname draft-08
  • From: Scott Rose <scottr@nist.gov>
• Re: updated dname draft-08
  • From: Paul Vixie <paul@vix.com>
• Re: updated dname draft-08
  • From: Scott Rose <scottr@nist.gov>
• Re: updated dname draft-08
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: updated dname draft-08
  • From: Paul Vixie <paul@vix.com>
• updated dname draft-08
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• I-D Action:draft-ietf-dnsext-rfc2672bis-dname-08.txt
  • From: Internet-Drafts@ietf.org
• TCP mandatory? (Was: initial thoughts on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: In the spirit of Festivus
  • From: Danny Mayer <mayer@gis.net>
• Re: In the spirit of Festivus
  • From: Danny Mayer <mayer@ntp.isc.org>
• initial thoughts on draft-ietf-dnsext-dns-protocol-profile-00
  • From: Joe Abley <jabley@ca.afilias.info>
• Re: I-D Action:draft-ietf-dnsext-dns-protocol-profile-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: I-D Action:draft-ietf-dnsext-dns-protocol-profile-00.txt
  • From: Chris Thompson <cet1@cus.cam.ac.uk>
• Re: I-D Action:draft-ietf-dnsext-dns-protocol-profile-00.txt
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: In the spirit of Festivus
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: I-D Action:draft-ietf-dnsext-dns-protocol-profile-00.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• I-D Action:draft-ietf-dnsext-dns-protocol-profile-00.txt
  • From: Internet-Drafts@ietf.org
• DNS protocol profile document effort.
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: {Blocked Content} I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-07.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: In the spirit of Festivus
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: In the spirit of Festivus
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: {Blocked Content} I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-07.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: {Blocked Content} I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-07.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: {Blocked Content} I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-07.txt
  • From: Wouter Wijngaards <wouter@NLnetLabs.nl>
• Re: ECC future direction for DNSSEC
  • From: Mark Andrews <Mark_Andrews@isc.org>
• ECC future direction for DNSSEC
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: In the spirit of Festivus
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: In the spirit of Festivus
  • From: Paul Vixie <paul@vix.com>
• Re: In the spirit of Festivus
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: In the spirit of Festivus
  • From: Andras Salamon <andras@dns.net>
• Re: I-D Action:draft-ietf-dnsext-rfc2671bis-edns0-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: draft-ietf-dnsext-ecc-key-10
  • From: "Eastlake III Donald-LDE008" <Donald.Eastlake@motorola.com>
• Re: EDNS0 revisions
  • From: Paul Vixie <paul@vix.com>
• Re: EDNS0 revisions
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: EDNS0 revisions
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• draft-ietf-dnsext-ecc-key-10
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: In the spirit of Festivus
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: In the spirit of Festivus
  • From: Shane Kerr <Shane_Kerr@isc.org>
• Re: EDNS0 revisions
  • From: Kenji Rikitake <kenji.rikitake@acm.org>
• Re: EDNS0 revisions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: {Blocked Content} I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-07.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: EDNS0 revisions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: EDNS0 revisions
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: EDNS0 revisions
  • From: Paul Vixie <paul@vix.com>
• Re: EDNS0 revisions
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: EDNS0 revisions
  • From: Mark Andrews <Mark_Andrews@isc.org>
• draft-ietf-dnsext-rfc2671bis-edns0-00 (fwd)
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: EDNS0 revisions
  • From: Paul Vixie <paul@vix.com>