Mail Index

• Thread Index

• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-04.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] Fwd: Last Call: draft-cheshire-dnsext-multicastdns (Multicast DNS) to Informational RFC
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Jakob Schlyter <jakob@kirei.se>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Bob Halley <Bob.Halley@nominum.com>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: [dnsext] DNSKEY signatures - dnssec-bis updates
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• [dnsext] I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-18.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] Re: Building structured extensibility into EDNS0(bis)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] DNSKEY signatures - dnssec-bis updates
  • From: "Roy Arends" <roy@nominet.org.uk>
• [dnsext] Building structured extensibility into EDNS0(bis)
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-03.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-registry-fixes-01.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] DNSKEY signatures - dnssec-bis updates
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] NSEC and algo 7 - dnssec-bis updates
  • From: Mark Andrews <marka@isc.org>
• [dnsext] DNSKEY signatures - dnssec-bis updates
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] NSEC and algo 7 - dnssec-bis updates
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Duane Wessels <wessels@dns-oarc.net>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: George Michaelson <ggm+ietf@apnic.net>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: George Michaelson <ggm@apnic.net>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Duane Wessels <wessels@dns-oarc.net>
• [dnsext] Re: IETF 76: Root DNSSEC Presentation with Q&A (room changed again)
  • From: Jakob Schlyter <jakob@kirei.se>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: David Conrad <drc@virtualized.org>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: John Levine <johnl@iecc.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Geoff Huston <gih@apnic.net>
• [dnsext] Re: I-D Action:draft-ietf-dnsext-dnssec-gost-02.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-02.txt
  • From: Internet-Drafts@ietf.org
• Source material for RFCs (was: Re: [dnsext] a possible errata to RFC2136)
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] a possible errata to RFC2136
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] Re: IETF 76: Root DNSSEC Presentation with Q&A (room changed)
  • From: Jakob Schlyter <jakob@kirei.se>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Ted Lemon <mellon@fugue.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Geoff Huston <gih@apnic.net>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: John Schnizlein <schnizlein@isoc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] a possible errata to RFC2136
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] a possible errata to RFC2136
  • From: Bob Halley <Bob.Halley@nominum.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] a possible errata to RFC2136
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] a possible errata to RFC2136
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Re: a possible errata to RFC2136
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] a possible errata to RFC2136
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] a possible errata to RFC2136
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] a possible errata to RFC2136
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• Re: [dnsext] a possible errata to RFC2136
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] RE: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: <mohamed.boucadair@orange-ftgroup.com>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] a possible errata to RFC2136
  • From: Bob Halley <Bob.Halley@nominum.com>
• [dnsext] Re: IETF 76: Root DNSSEC Presentation with Q&A
  • From: Jakob Schlyter <jakob@kirei.se>
• [dnsext] a possible errata to RFC2136
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Alfred Hönes <ah@TR-Sys.de>
• RE: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: <mohamed.boucadair@orange-ftgroup.com>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Andras Salamon <andras@dns.net>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Andras Salamon <andras@dns.net>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] draft-li-dnsext-ipv4-ipv6 -- a more versatile proposal
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] Re:conclusions drawn in draft-wang-dns-inconsis-ncache-00
  • From: "Zheng Wang" <wangzheng@cnnic.cn>
• [dnsext] DNSEXT Working Group status report from Chairs
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [DNSOP] [dnsext] Computerworld apparently has changed DNS protocol
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Mark Andrews <marka@isc.org>
• Re: [DNSOP] [dnsext] Re: Computerworld apparently has changed DNS protocol
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Computerworld apparently has changed DNS protocol
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Computerworld apparently has changed DNS protocol
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Computerworld apparently has changed DNS protocol
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Computerworld apparently has changed DNS protocol
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: [DNSOP] Computerworld apparently has changed DNS protocol
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Computerworld apparently has changed DNS protocol
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] New unofficial versions of drafts
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] conclusions drawn in draft-wang-dns-inconsis-ncache-00
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] IETF 76: Root DNSSEC Presentation with Q&A
  • From: Jakob Schlyter <jakob@kirei.se>
• Re: [dnsext] conclusions drawn in draft-wang-dns-inconsis-ncache-00
  • From: Mark Andrews <marka@isc.org>
• [dnsext] conclusions drawn in draft-wang-dns-inconsis-ncache-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-ietf-dnsext-dnskey-registry-fixes-01 editorials
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] A few notes on the IXFR-ONLY draft
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] A few notes on the IXFR-ONLY draft
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-01
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-01
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-ietf-dnsext-dnskey-registry-fixes-01 editorials
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] draft-ietf-dnsext-dns-tcp-requirements-01
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] draft-ietf-dnsext-dnskey-registry-fixes-01 editorials
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] A few notes on the IXFR-ONLY draft
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Douglas Otis <dotis@mail-abuse.org>
• [dnsext] WGLC: Gost algorithms for DNSSEC
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Draft agenda posted
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] RFC 5702 on Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RFC 5702 on Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC
  • From: rfc-editor@rfc-editor.org
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Ray.Bellis@nominet.org.uk
• Re: Protocol numbers for RSA/SHA{256|512} (Was: Re: [dnsext] GOST DNSSEC, implementations?)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: registrar transfers (was Re: [dnsext] Trust Anchors)
  • From: Joe Abley <jabley@hopcount.ca>
• Re: registrar transfers (was Re: [dnsext] Trust Anchors)
  • From: João Damas <joao@bondis.org>
• [dnsext] Re: registrar transfers
  • From: Jim Reid <jim@rfc1035.com>
• registrar transfers (was Re: [dnsext] Trust Anchors)
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] Trust Anchors
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] new version of draft-ietf-dnsext-dnskey-registry-fixes available
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] Trust Anchors
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Trust Anchors
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Trust Anchors
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Trust Anchors
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Trust Anchors
  • From: João Damas <joao@bondis.org>
• Re: [dnsext] Trust Anchors
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Trust Anchors
  • From: Bob Halley <Bob.Halley@nominum.com>
• Re: [dnsext] Trust Anchors
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Trust Anchors
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Trust Anchors
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-01.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] Trust Anchors
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Trust Anchors
  • From: Bob Halley <Bob.Halley@nominum.com>
• Re: [dnsext] Trust Anchors
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Trust Anchors
  • From: Bob Halley <Bob.Halley@nominum.com>
• [dnsext] Re: Is rfc3110 correct?
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Is rfc3110 correct?
  • From: Mark Andrews <marka@isc.org>
• [dnsext] A64-DNS Resource Record for IPv4-mapped IPv6 Address
  • From: <mohamed.boucadair@orange-ftgroup.com>
• [dnsext] Separating DNAME-bis from whether to use DNAME at a given level
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: Protocol numbers for RSA/SHA{256|512} (Was: Re: [dnsext] GOST DNSSEC, implementations?)
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: joao damas <joao@bondis.org>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: "Health" <healthyao@gmail.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Paul Vixie <vixie@isc.org>
• Re: Protocol numbers for RSA/SHA{256|512} (Was: Re: [dnsext] GOST DNSSEC, implementations?)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Protocol numbers for RSA/SHA{256|512} (Was: Re: [dnsext] GOST DNSSEC, implementations?)
  • From: Doug Barton <dougb@dougbarton.us>
• [dnsext] Re: DNAME-bis issues (was: [DNSOP] new draft about idn tld variant implementation)
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Doug Otis <doug.mtview@gmail.com>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-01.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] Re: [DNSOP] new draft about idn tld variants implementation
  • From: joao damas <joao@bondis.org>
• [dnsext] Re: [DNSOP] new draft about idn tld variants implementation
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] planning draft-ietf-dnsext-rfc2672bis-dname-17 to IESG
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Donald Eastlake <d3e3e3@gmail.com>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Fw: New Version Notification for draft-bellis-dns-recursive-discovery-00
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] What is the 'canonical' spelling: RRset of RRSet ?
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] draft-crocker-dnssec-algo-signal-04 editorials
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Significant typo (I hope) in draft-ietf-dnsext-dnssec-registry-fixes-00
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] What does "status" mean in draft-ietf-dnsext-dnssec-registry-fixes-00?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Significant typo (I hope) in draft-ietf-dnsext-dnssec-registry-fixes-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] FW: New Version Notification for draft-crocker-dnssec-algo-signal-04
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00 / a way forward
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-registry-fixes-00.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: Shane Kerr <shane@isc.org>
• [dnsext] Re: [DNSOP] draft-iab-idn-encoding-00
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Re: draft-iab-idn-encoding-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Why ZSK rollover is a Bad Idea
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] draft-ietf-dnsext-dns-tcp-requirements-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Why ZSK rollover is a Bad Idea (tm)
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] Why ZSK rollover is a Bad Idea (tm)
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Why ZSK rollover is a Bad Idea (tm)
  • From: Eric Rescorla <ekr@rtfm.com>
• Re: [dnsext] Why ZSK rollover is a Bad Idea (tm)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Why ZSK rollover is a Bad Idea (tm)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] I-D Action:draft-ietf-dnsext-dns-tcp-requirements-00.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] DNSEXT session at IETF 76
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] RSA/SHA256 assignments
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Protocol Action: 'Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC' to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• [dnsext] IETF-75 Hiroshima agenda requests and deadlines
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] comment about the IANA registry discussion in draft-ietf-dnsext-dnssec-algo-allocation
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• [dnsext] draft-gudmundsson-dns-srv-iana-registry-03
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Shane Kerr <shane@isc.org>
• [dnsext] draft-ietf-dnsext-rfc2671bis-edns0
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Collection of recursive resolvers?
  • From: Paul Wouters <paul@xelerance.com>
• [dnsext] Collection of recursive resolvers?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] draft-barwood-dnsext-dns-transport-signal-00 to WG work item
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] draft-barwood-dnsext-dns-transport-signal-00.txt - WG item
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: David Blacka <davidb@verisign.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] algorithm identifier code point hijacking
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] algorithm identifier code point hijacking
  • From: bmanning@vacation.karoshi.com
• [dnsext] algorithm identifier code point hijacking
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: John Schnizlein <schnizlein@isoc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] draft-dolmatov-dnsext-dnssec-gost-01 technical & editorial issues
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] Re: Two more details in draft-ietf-dnsext-rfc3597-bis-00
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Andreas Gustafsson <gson@araneus.fi>
• [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-17.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] Two more details in draft-ietf-dnsext-rfc3597-bis-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Protocol standards and implementations vs. configurations
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Protocol standards and implementations vs. configurations
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] draft-ietf-dnsext-rfc3597-bis-00
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] Protocol standards and implementations vs. configurations
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed (adopted alternative transport)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Diffs in draft-ietf-dnsext-rfc3597-bis-00?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Diffs in draft-ietf-dnsext-rfc3597-bis-00?
  • From: Andreas Gustafsson <gson@araneus.fi>
• [dnsext] Diffs in draft-ietf-dnsext-rfc3597-bis-00?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Editor needed
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• [dnsext] I-D Action:draft-ietf-dnsext-rfc3597-bis-00.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Editor needed
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Editor needed
  • From: Tony Finch <dot@dotat.at>
• [dnsext] Another reason for TCP MUST
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-gost-00.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] draft-dolmatov-dnsext-dnssec-gost-01 technical & editorial issues
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Editor needed
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] irrelevant Subject: header
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Re: irrelevant Subject: header
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] irrelevant Subject: header
  • From: Shane Kerr <shane@isc.org>
• [dnsext] irrelevant Subject: header
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• RE: [dnsext] Editor needed
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• [dnsext] re: Nominum doing something DNSCurve-y?
  • From: =JeffH <Jeff.Hodges@KingsMountain.com>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-alg-allocation-00.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] draft-ietf-dnsext-dnssec-alg-allocation-00
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Editor needed
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re-ordering of responses over TCP
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re-ordering of responses over TCP
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Re-ordering of responses over TCP
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] draft-hoffman-dnssec-* (DNSSEC algorithm drafts)
  • From: Alfred Hönes <ah@TR-Sys.de>
• [dnsext] draft-ietf-dnsext-rfc2672bis-dname-16 follow-up
  • From: Alfred Hönes <ah@TR-Sys.de>
• Re: [dnsext] Updated: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Re-ordering of responses over TCP
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Updated: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] new DNS transports
  • From: Mark Andrews <marka@isc.org>
• [dnsext] draft-barwood-dnsext-dns-transport-04 technical comments
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Re-ordering of responses over TCP
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: Editor needed
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] Re-ordering of responses over TCP
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] prioritising TCP and UDP queries
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] new DNS transports
  • From: bmanning@vacation.karoshi.com
• [dnsext] draft-dolmatov-dnsext-dnssec-gost-01 technical & editorial issues
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] new DNS transports
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] Re: Editor needed
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: making TCP a MUST
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] Re: gethostbyname()
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Re: making TCP a MUST
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re: making TCP a MUST
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] Re: making TCP a MUST
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: making TCP a MUST
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] gethostbyname()
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Re: making TCP a MUST
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• [dnsext] [mary.barnes@nortel.com: Nomcom 2009-10: FINAL Call for Nominations, Local Office hours, Nominee Questionnaires]
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] making TCP a MUST
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: making TCP a MUST
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: making TCP a MUST
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] WG Action: RECHARTER: DNS Extensions Working group (dnsext)
  • From: IESG Secretary <iesg-secretary@ietf.org>
• Re: [dnsext] Re: making TCP a MUST
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: making TCP a MUST
  • From: Jim Reid <jim@rfc1035.com>
• Re: Historical insanity (ignorable) Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: making TCP a MUST
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Editor needed
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Editor needed
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] making TCP a MUST
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Editor needed
  • From: Donald Eastlake <d3e3e3@gmail.com>
• Re: [dnsext] Editor needed
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] TCP and 512+ byte responses
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Editor needed
  • From: Mans Nilsson <mansaxel@besserwisser.org>
• Re: [dnsext] Editor needed
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Editor needed
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] TCP and 512+ byte responses
  • From: Jim Reid <jim@rfc1035.com>
• Re: Where TCP might be required (Was: [dnsext] Editor needed)
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Wes Hardaker <wjhns1@hardakers.net>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Where TCP might be required (Was: [dnsext] Editor needed)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• Historical insanity (ignorable) Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] DNS transport
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Editor needed
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] DNS transport
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Jelte Jansen <jelte@isc.org>
• Re: [dnsext] DNS transport
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] DNS transport
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS transport
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS transport
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS transport
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] DNS transport
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Jelte Jansen <jelte@isc.org>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] DNS transport
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] DNS transport
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] GOST DNSSEC implementations?
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] DNS transport
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] DNS transport
  • From: Douglas Otis <dotis@mail-abuse.org>
• [dnsext] Nominum doing something DNSCurve-y?
  • From: Matthew Dempsky <matthew@dempsky.org>
• [no subject]
  • From: Unknown
• [no subject]
  • From: Unknown
• [dnsext] Last Call: draft-ietf-dnsext-dnssec-rsasha256 (Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSEC) to Proposed Standard
  • From: The IESG <iesg-secretary@ietf.org>
• [no subject]
  • From: Unknown
• Re: [dnsext] Re: Signing the root with SHA-1 by Sep 1st
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
  • From: Patrik Fältström <paf@cisco.com>
• Re: Fwd: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Wayne Beaver <wbeaver@afilias.info>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Working around proxies
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Afiliation of DNSEXT WG chairs
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Duane Wessels <wessels@dns-oarc.net>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Afiliation of DNSEXT WG chairs
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Re: Signing the root with SHA-1 by Sep 1st
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: Signing the root with SHA-1 by Sep 1st
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Afiliation of DNSEXT WG chairs
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Working around proxies
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Amplification attacks, RFC3704 etc.
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Amplification attacks, RFC3704 etc.
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Chris Thompson <cet1@cam.ac.uk>
• RE: [dnsext] EDNS0 fallback "revisited"
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Working around proxies
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Douglas Otis <dotis@mail-abuse.org>
• [dnsext] Sorry for the redundant emails
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Working around proxies
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Working around proxies
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Working around proxies
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Working around proxies
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Editor needed
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Editor needed
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Editor needed
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Alan Clegg <aclegg@isc.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Editor needed
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: João Damas <joao@bondis.org>
• Re: [dnsext] Editor needed
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Alan Clegg <aclegg@isc.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Alan Clegg <aclegg@isc.org>
• Re: [dnsext] Re: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] Presentation on DNSSEC that Google brought to my attention
  • From: Alan Clegg <aclegg@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Updated: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Updated: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Editor needed
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] draft-hoffman-dnssec-alg-allocation
  • From: Jim Reid <jim@rfc1035.com>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• [dnsext] Updated: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Re: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• S weak in the upper story ju
  • From: Carriere <triple@danuta.nl>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Jelte Jansen <jelte@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] political/legal aspects of DNSSEC deployment
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dmitry Burkov <dburk@burkov.aha.ru>
• Fwd: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] Fwd: New Version Notification for draft-dempsky-dnscurve-00
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Working around proxies
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Working around proxies
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Working around proxies
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Working around proxies
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• RE: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Working around proxies
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Working around proxies
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Editor needed
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Editor needed
  • From: bmanning@vacation.karoshi.com
• [dnsext] Editor needed
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Minutes from IETF-75 uploaded
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Re: measuring TCP query performance
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS0 fallback "revisited"
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] EDNS0 fallback "revisited"
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Douglas Otis <dotis@mail-abuse.org>
• [dnsext] Working around proxies
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] NAPTR vs (S-NAPTR & U-NAPTR)
  • From: sandoche BALAKRICHENAN <sandoche.balakrichenan@afnic.fr>
• [dnsext] measuring TCP query performance
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Suggested fallbacks...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Suggested fallbacks...
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• [dnsext] BCP 152, RFC 5625 on DNS Proxy Implementation Guidelines
  • From: rfc-editor@rfc-editor.org
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Suggested fallbacks...
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Suggested fallbacks...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] Suggested fallbacks...
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Paul Vixie <vixie@isc.org>
• RE: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• [dnsext] TCP DNS benchmarking, or Who's afraid of TCP?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] TCP traffic and DNSSEC
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Cryptographic Algorithm Identifier Allocation for DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Donald Eastlake <d3e3e3@gmail.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] TCP traffic and DNSSEC
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] TCP traffic and DNSSEC
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] TCP traffic and DNSSEC
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] root DNSKEY response is 1749 bytes
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Doug Barton <dougb@dougbarton.us>
• [dnsext] root DNSKEY response is 1749 bytes
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] Suggested fallbacks...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft updated
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: David Conrad <drc@virtualized.org>
• [dnsext] DNS over SCTP and correcting security concerns
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Doug Otis <doug.mtview@gmail.com>
• DNS-OARC (was Re: [dnsext] all .gov do=1 nxdomain answers already appear to befragmented.. and it works somehow)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft updated
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft updated
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: bert hubert <bert.hubert@gmail.com>
• RE: [dnsext] Re: What ELSE relies on UDP fragmentation?
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Cutting to the chase (was Re: [dnsext] EDNS Page Option draft)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] Re: What ELSE relies on UDP fragmentation?
  • From: Stefan Winter <stefan.winter@restena.lu>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Paul Vixie <vixie@isc.org>
• Re: Cutting to the chase (was Re: [dnsext] EDNS Page Option draft)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Paul Wouters <paul@xelerance.com>
• [dnsext] all .gov do=1 nxdomain answers already appear to be fragmented.. and it works somehow
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] EDNS Page Option draft updated
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: bert hubert <bert.hubert@gmail.com>
• Cutting to the chase (was Re: [dnsext] EDNS Page Option draft)
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Duane Wessels <wessels@dns-oarc.net>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] What ELSE relies on UDP fragmentation?
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] What ELSE relies on UDP fragmentation?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Size of DNSsec NXDOMAIN response
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Size of DNSsec NXDOMAIN response
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] EDNS Page Option draft
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option draft
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] EDNS Page Option draft
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option draft
  • From: Robert Elz <kre@munnari.OZ.AU>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option draft
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option draft
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] EDNS Page Option draft
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Fragmentation undesirable
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Doug Barton <dougb@dougbarton.us>
• Re: [dnsext] Soft Packet Size Limit
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Soft Packet Size Limit (was: DNS over SCTP problems, part 1, theory)
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Soft Packet Size Limit (was: DNS over SCTP problems, part 1, theory)
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Michael Richardson <mcr@sandelman.ca>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] middleboxes and an alternate port number
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] middleboxes and an alternate port number
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] middleboxes and an alternate port number
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] experimental/testing DNSSEC algorithm identifiers
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• [dnsext] extending the EDNS Algorithm Understood (AU) option
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Doug Otis <doug.mtview@gmail.com>
• [dnsext] Re: Rethinking the security too large for UDP problem
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Rethinking the security too large for UDP problem
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 2, practice
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: bert hubert <bert.hubert@netherlabs.nl>
• [dnsext] DNS over SCTP problems, part 2, practice
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] NSEC3 confusion (in .org)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] NSEC3 confusion (in .org)
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] DNS over SCTP problems, part 1, theory
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] DNS over SCTP problems, part 1, theory
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] SCTP trials on NANOG, 3 of 3 (Re: DNS hardening)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] SCTP trials on NANOG, 3 of 3 (Re: DNS hardening)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] SCTP trials on NANOG, 3 of 3 (Re: DNS hardening)
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Signing the root with SHA-1 by Sep 1st
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Signing the root with SHA-1 by Sep 1st
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• [dnsext] SCTP trials on NANOG, 3 of 3 (Re: DNS hardening)
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] SCTP trials over on NANOG, 2 of 3 (Re: DNS hardening)
  • From: Paul Vixie <vixie@isc.org>
• Re: edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Re: DNS hardening, was Re: Dan Kaminsky
  • From: Paul Vixie <vixie@isc.org>
• Re: edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Paul Vixie <vixie@isc.org>
• Re: edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Douglas Otis <dotis@mail-abuse.org>
• edns fallback (was Re: [dnsext] comments on draft-crocker-...)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• [dnsext] [Fwd: I-D Action:draft-dolmatov-cryptocom-gost2814789-01.txt]
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] [Fwd: I-D Action:draft-dolmatov-dnsext-dnssec-gost-01.txt]
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Bob Halley <Bob.Halley@nominum.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
• [dnsext] Re: comments on draft-crocker-dnssec-algo-signal-03
  • From: Anand Buddhdev <anandb@ripe.net>
• Re: [dnsext] Trying to reading RFC 4035 as a requirements document
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Douglas Otis <dotis@mail-abuse.org>
• [dnsext] Trying to reading RFC 4035 as a requirements document
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• [dnsext] dnssec-bis updates: key use
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Danny Mayer <mayer@ntp.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] operational impact of signed responses/referrals
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Re: operational impact of signed responses/referrals
  • From: Joe Abley <jabley@hopcount.ca>
• [dnsext] operational impact of signed responses/referrals
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Joe Abley <jabley@hopcount.ca>
• [dnsext] Publication request for draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Issue with RFC 4034, section 3 and section 4
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Michael Richardson <mcr@sandelman.ca>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Michael Richardson <mcr@sandelman.ca>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] Re: draft-kerr-ixfr-only-00.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@CS.UCLA.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: John Schnizlein <schnizlein@isoc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Eric Osterweil <eoster@cs.ucla.edu>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: John Schnizlein <schnizlein@isoc.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mark Andrews <marka@isc.org>
• [dnsext] dnssec-algo-signal & Roy
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Joe Abley <jabley@hopcount.ca>
• [dnsext] draft-crocker-dnssec-algo-signal-03 -- more time please!
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• [dnsext] Additions to the draft charter
  • From: Olafur Gudmundsson/DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 comments
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] draft-li-dnsext-ipv4-ipv6 comments
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] DNS64 and lying cache servers
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Paul Wouters <paul@xelerance.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Basil Dolmatov <dol@reedcat.net>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS64 and lying cache servers
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mans Nilsson <mansaxel@besserwisser.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Mans Nilsson <mansaxel@besserwisser.org>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNS64 and lying cache servers
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Frederico A C Neves <fneves@registro.br>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] DNS64 and lying cache servers
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Patrik Fältström <paf@cisco.com>
• [dnsext] Signing the root with SHA-1 or SHA-2
  • From: Rob Austein <sra@isc.org>
• [dnsext] DNS64 and lying cache servers
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] draft-li-dnsext-ipv4-ipv6 comments
  • From: Michael Graff <mgraff@isc.org>
• [dnsext] comments on draft-crocker-dnssec-algo-signal-03
  • From: Michael Graff <mgraff@isc.org>
• [dnsext] Report from the Chairs
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] I-D Action:draft-ietf-dnsext-rfc2671bis-edns0-02.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] -03 version of algo-signal posted
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• [dnsext] agenda updated
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Basil Dolmatov <dol@reedcat.net>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Samuel Weiler <weiler@watson.org>
• [dnsext] Materials for any talking
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: some NSEC confusion on cname wildcards
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: some NSEC confusion on cname wildcards
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] some NSEC confusion on cname wildcards
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: some NSEC confusion on cname wildcards
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Re: some NSEC confusion on cname wildcards
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] some NSEC confusion on cname wildcards
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Meeting agenda updated; please send materials
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] -03 version of algo-signal posted
  • From: ALAIN AINA <aalain@trstech.net>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: Fwd: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: Fwd: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: bert hubert <bert.hubert@gmail.com>
• Re: Fwd: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: Fwd: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Alex Bligh <alex@alex.org.uk>
• Fwd: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Mark Andrews <marka@isc.org>
• [dnsext] WikiNameDroppers?
  • From: William Allen Simpson <william.allen.simpson@gmail.com>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] TALINK RRTYPE review. Start of three week comment period
  • From: roy@nominet.org.uk
• [dnsext] DNSEXT agenda updated
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Re: Notes on the DNS standard
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Re: Notes on the DNS standard
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Notes on the DNS standard
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: João Damas <joao@bondis.org>
• Re: [dnsext] draft-dolmatov-dnsext-dnssec-gost-01.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] draft-dolmatov-dnsext-dnssec-gost-01.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] draft-dolmatov-dnsext-dnssec-gost-01.txt
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] draft-livingood-dns-redirect-00
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] draft-livingood-dns-redirect-00
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] Request for clarification on Truncation
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Request for clarification on Truncation
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: David Blacka <davidb@verisign.com>
• Re: [dnsext] 1st version of agenda for IETF75
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] 1st version of agenda for IETF75
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: "Blacka, David" <davidb@verisign.com>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] dnssec-bis-updates question #1
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Mark Andrews <marka@isc.org>
• [dnsext] dnssec-bis-updates question #1
  • From: David Blacka <davidb@verisign.com>
• [dnsext] Re: I-D ACTION:draft-huang-dnsext-reputation-00.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Re: draft-li-dnsext-ipv4-ipv6 and compatibility with the installed base
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] fragmentation considered harmful
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] -03 version of algo-signal posted
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] -03 version of algo-signal posted
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] -03 version of algo-signal posted
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] draft-li-dnsext-ipv4-ipv6 and compatibility with the installed base
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Shane Kerr <shane@isc.org>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Shane Kerr <shane@isc.org>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] Re: a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] a new EDNS feature for draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] fragmentation considered harmful
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] fragmentation considered harmful
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] fragmentation considered harmful
  • From: Diane Bruce <db@db.net>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] fragmentation considered harmful
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] fragmentation considered harmful
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] fragmentation considered harmful
  • From: Michael Graff <mgraff@isc.org>
• [dnsext] WG Review: Recharter of DNS Extensions (dnsext)
  • From: IESG Secretary <iesg-secretary@ietf.org>
• [dnsext] fragmentation considered harmful
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] -03 version of algo-signal posted
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] -03 version of algo-signal posted
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] DNSEXT to meet at IETF-75/Stockholm
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] -03 version of algo-signal posted
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] -03 version of algo-signal posted
  • From: "Rose, Scott W." <scott.rose@nist.gov>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• [dnsext] I-D: IXFR-ONLY proposal (Was: New Version Notification for draft-kerr-ixfr-only-00)
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Re: Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• [dnsext] EDNS0 OWNER Option
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Chris Hills <chaz@chaz6.com>
• [dnsext] Protocol Action: 'DNS Proxy Implementation Guidelines' to BCP
  • From: The IESG <iesg-secretary@ietf.org>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Shane Kerr <shane@isc.org>
• [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Shane Kerr <shane@isc.org>
• RE: [dnsext] Name server agility with DNSSEC
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• [dnsext] Re: Name server agility with DNSSEC
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: I-D Action:draft-li-dnsext-ipv4-ipv6-00.txt
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] Name server agility with DNSSEC
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Name server agility with DNSSEC
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Name server agility with DNSSEC
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Clarification on RFC 2181
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] [Fwd: I-D Action:draft-ietf-behave-dns64-00.txt]
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [dnsext] Clarification on RFC 2181
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Wes Hardaker <wjhns1@hardakers.net>
• Re: [dnsext] Clarification on RFC 2181
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] algo-signal -03 -- Internet Draft to facilitate algorithm transition
  • From: Steve Crocker <steve@shinkuro.com>
• [dnsext] RFC5011 interoperabilty testing
  • From: Steve Crocker <steve@shinkuro.com>
• Re: [dnsext] Clarification on RFC 2181
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] Clarification on RFC 2181
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Clarification on RFC 2181
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: Clarification on RFC 2181
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Clarification on RFC 2181
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Clarification on RFC 2181
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Clarification on RFC 2181
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Clarification on RFC 2181
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Clarification on RFC 2181
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: [dnsext] Clarification on RFC 2181
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Clarification on RFC 2181
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Clarification on RFC 2181
  • From: gson@araneus.fi (Andreas Gustafsson)
• [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-06.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] Clarification on RFC 2181
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Clarification on RFC 2181
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Clarification on RFC 2181
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Clarification on RFC 2181
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Clarification on RFC 2181
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Clarification on RFC 2181
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Clarification on RFC 2181
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Clarification on RFC 2181
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Clarification on RFC 2181
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Re: ops.ietf.org Blacklisting Complications
  • From: "David W. Hankins" <David_Hankins@isc.org>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: JINMEI Tatuya / 神明達哉 <jinmei@isc.org>
• [dnsext] Response to request for real data...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] updated dname update draft (-16)
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-16.txt
  • From: Internet-Drafts@ietf.org
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Nested trust anchors (again)
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] Nested trust anchors (again)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Paul Vixie <vixie@isc.org>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Mark Andrews <marka@isc.org>
• [dnsext] ops.ietf.org Blacklisting Complications
  • From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] Nested trust anchors (again)
  • From: Mark Andrews <marka@isc.org>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: bmanning@vacation.karoshi.com
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Mark Andrews <marka@isc.org>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Paul Vixie <vixie@isc.org>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Nested trust anchors (again)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RE: Nested trust anchors (again)
  • From: Mark Andrews <marka@isc.org>
• RE: [dnsext] RE: Nested trust anchors (again)
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] RE: Nested trust anchors (again)
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Re: Nested trust anchors (again)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] RE: Nested trust anchors (again)
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Ray.Bellis@nominet.org.uk
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] Re: Nested trust anchors (again)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Florian Weimer <fweimer@bfk.de>
• RE: [dnsext] Re: Nested trust anchors (again)
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• Re: [dnsext] Danger of coming unstuck
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Alex Bligh <alex@alex.org.uk>
• [dnsext] Re: Nested trust anchors (again)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Nested trust anchors (again)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Nested trust anchors (again)
  • From: bmanning@vacation.karoshi.com
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Nested trust anchors (again)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: bert hubert <bert.hubert@gmail.com>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Alex Bligh <alex@alex.org.uk>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Nested trust anchors (again)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Nested trust anchors (again)
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Nested trust anchors (again)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] Nested trust anchors (again)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Nested trust anchors (again)
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Nested trust anchors (again)
  • From: Paul Vixie <vixie@isc.org>
• Real data (was Re: [dnsext] Danger of coming unstuck)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Nested trust anchors (again)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Re: Danger of coming unstuck
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Nested trust anchors (again)
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Re: Danger of coming unstuck
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Re: Danger of coming unstuck
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Nested trust anchors (again)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Glue Caching Misbehaviours
  • From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
• [dnsext] Re: Danger of coming unstuck
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Nested trust anchors (again)
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Nested trust anchors (again)
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] Glue Caching Misbehaviours
  • From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Danger of coming unstuck
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Danger of coming unstuck
  • From: sthaug@nethelp.no
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: sthaug@nethelp.no
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Nested trust anchors (again)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Danger of coming unstuck
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] Nested trust anchors (again)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Danger of coming unstuck
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Danger of coming unstuck
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Danger of coming unstuck
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] DNS Extensions Working Group meeting at IETF 75
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] TCP pushback
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Danger of coming unstuck
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Danger of coming unstuck
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] Danger of coming unstuck
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP pushback
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] TCP pushback
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] TCP pushback
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Why the cause of drops matter...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] TCP pushback
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Why the cause of drops matter...
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] TCP pushback
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] Why the cause of drops matter...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] TCP pushback
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP pushback
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• [dnsext] EDNS Page Option to handle large responses
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] New rules for DO bit
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] On RFC maintenance and reference implementations
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] On RFC maintenance and reference implementations (was: Does RFC 3226. . .)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] Does RFC 3226 require DO=1 ==> bufsize over 1219? was Re: [dnsext] New rules for DO bit
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] New rules for DO bit
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] TCP pushback
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] TCP pushback
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] New rules for DO bit
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] TCP pushback
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] TCP pushback
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] TCP pushback
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] TCP pushback
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] New rules for DO bit
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] TCP pushback
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] TCP pushback
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] TCP pushback
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] TCP pushback
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] EDNS Page Option to handle large responses
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] New rules for DO bit
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] New rules for DO bit
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: bmanning@vacation.karoshi.com
• [dnsext] EDNS Page Option to handle large responses
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] New rules for DO bit
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] New rules for DO bit
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Danny Mayer <mayer@gis.net>
• Re: [dnsext] New rules for DO bit
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] New rules for DO bit
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Michael Sinatra <michael@rancid.berkeley.edu>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Danny Mayer <mayer@gis.net>
• Re: [dnsext] New rules for DO bit
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] New rules for DO bit
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] New rules for DO bit
  • From: Michael Graff <mgraff@isc.org>
• Re: [dnsext] New rules for DO bit
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] New rules for DO bit
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] New rules for DO bit
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] New rules for DO bit
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] New rules for DO bit
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Danny Mayer <mayer@gis.net>
• Re: Draft Charter v2. Re: [dnsext] Draft DNSEXT charter
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: Draft Charter v2. Re: [dnsext] Draft DNSEXT charter
  • From: "Bart Smit" <bit@pipe.nl>
• Re: SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Hardening DNS using existing protocol elements
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: Shane Kerr <shane@isc.org>
• Re: SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] Hardening DNS using existing protocol elements
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Comparing SCTP to TCP or UDP
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Comparing SCTP to TCP or UDP
  • From: niels=ietfops@bakker.net (Niels Bakker)
• Re: SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: Doug Otis <doug.mtview@gmail.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: bert hubert <bert.hubert@gmail.com>
• Re: SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: Draft Charter v2. Re: [dnsext] Draft DNSEXT charter
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Ask Bjørn Hansen <ask@develooper.com>
• Re: Draft Charter v2. Re: [dnsext] Draft DNSEXT charter
  • From: "Bart Smit" <bit@pipe.nl>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Andreas Gustafsson <gson@araneus.fi>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Comparing SCTP to TCP or UDP
  • From: Douglas Otis <dotis@mail-abuse.org>
• SCTP (Re: [dnsext] Re: TCP queries to the root servers )
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• [dnsext] Preferring IPv4 glue over IPv6 glue for IPv4 clients
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: RFC 3226 violations (was Re: [dnsext] Re: TCP queries to the root servers)
  • From: bmanning@vacation.karoshi.com
• Re: RFC 3226 violations (was Re: [dnsext] Re: TCP queries to the root servers)
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: RFC 3226 violations
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Andrew Sullivan <ajs@shinkuro.com>
• RFC 3226 violations (was Re: [dnsext] Re: TCP queries to the root servers)
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Samuel Weiler <weiler@watson.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Samuel Weiler <weiler@watson.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Draft Charter v2. Re: [dnsext] Draft DNSEXT charter
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] The ICSI Netalyzr
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Ask Bjørn Hansen <ask@develooper.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Paul Vixie <vixie@isc.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Ask Bjørn Hansen <ask@develooper.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Niall O'Reilly <Niall.oReilly@ucd.ie>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: bmanning@vacation.karoshi.com
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Florian Weimer <fweimer@bfk.de>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bert hubert <bert.hubert@gmail.com>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• TCP performance, was Re: [dnsext] Re: TCP queries to the root servers
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Re: TCP queries to the root servers
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <flucifredi@acm.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <flucifredi@acm.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Re: TCP queries to the root servers
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Donald Eastlake <d3e3e3@gmail.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <flucifredi@acm.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Distributing the root zone out of band
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] TCP queries to the root servers
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Distributing the root zone out of band
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Distributing the root zone out of band
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Distributing the root zone out of band
  • From: bmanning@vacation.karoshi.com
• [dnsext] Proposal to make DNSSEC Algorithm Types be "RFC required"
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Distributing the root zone out of band
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Distributing the root zone out of band
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Distributing the root zone out of band
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] Distributing the root zone out of band
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] WGLC: draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] WGLC: draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Signing a zone and record
  • From: Rafael Dantas Justo <rafael@registro.br>
• Re: [dnsext] Increasing hash collision resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Increasing hash collision resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Florian Weimer <fweimer@bfk.de>
• [dnsext] Signing a zone and record
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Federico Lucifredi <flucifredi@acm.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Matt Larson <mlarson@verisign.com>
• [dnsext] Status of TLSFP RRTYPE Request
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Andras Salamon <andras@dns.net>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Olaf Kolkman <olaf@NLnetLabs.nl>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Shane Kerr <shane@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Patrik Fältström <paf@cisco.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-14.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] DNSEXT to meet at IETF-75/Stockholm
  • From: Danny Mayer <mayer@gis.net>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Mark Andrews <marka@isc.org>
• [dnsext] Enforcing correct behavior: EDNS0 OK bit set, buffer < 1024
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] IP fragmentation security
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] IP fragmentation security
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] IP fragmentation security
  • From: Douglas Otis <dotis@mail-abuse.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] IP fragmentation security
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] IP fragmentation security
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] IP fragmentation security
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] IP fragmentation security
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] IP fragmentation security
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS Ping fallbacks
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Support for EDSN0 PING
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Mark Andrews <marka@isc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] EDNS Ping fallbacks
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] EDNS clarification
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS clarification
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS Ping fallbacks
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] EDNS clarification
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] EDNS Ping fallbacks
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] EDNS clarification
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] DNSCURVE
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Re: DNSCURVE
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Draft DNSEXT charter
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Draft DNSEXT charter
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Draft DNSEXT charter
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Draft DNSEXT charter
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Draft DNSEXT charter
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Draft DNSEXT charter
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Draft DNSEXT charter
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Draft DNSEXT charter
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Draft DNSEXT charter
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Draft DNSEXT charter
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] Draft DNSEXT charter
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] [dotis@mail-abuse.org: Re: DNS over SCTP]
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] [dotis@mail-abuse.org: Re: DNS over SCTP]
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] [dotis@mail-abuse.org: Re: DNS over SCTP]
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] [dotis@mail-abuse.org: Re: DNS over SCTP]
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] [dotis@mail-abuse.org: Re: DNS over SCTP]
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] DNSEXT to meet at IETF-75/Stockholm
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Selecting which name server IP address to query
  • From: JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya@isc.org>
• Re: [dnsext] Selecting which name server IP address to query
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Selecting which name server IP address to query
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Selecting which name server IP address to query
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Selecting which name server IP address to query
  • From: Florian Weimer <fw@deneb.enyo.de>
• [dnsext] Selecting which name server IP address to query
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Emilio Perea <eperea@walkereng.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Increasing hash collision resilience
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: sthaug@nethelp.no
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: sthaug@nethelp.no
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: was Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• was Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: "Federico Lucifredi" <FLucifredi@novell.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Otmar Lendl <lendl@nic.at>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bmanning@vacation.karoshi.com
• [dnsext] Re: Configuration of domains, secondaries in the domain or not? (Was: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] Re: Question on RFC 3225 - DO Bit and ANY
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: SM <sm@resistor.net>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Emilio Perea <eperea@walkereng.com>
• Re: [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: sthaug@nethelp.no
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: SM <sm@resistor.net>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Stuart Cheshire <cheshire@apple.com>
• [dnsext] Re: Configuration of domains, secondaries in the domain or not? (Was: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Question on RFC 3225 - DO Bit and ANY
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Kim Davies <kim.davies@icann.org>
• Re: [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: David Ulevitch <davidu@everydns.net>
• Re: [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Configuration of domains, secondaries in the domain or not? (Was: DNSCurve
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Increasing hash collision resilience
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Increasing hash collision resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: David Ulevitch <davidu@everydns.net>
• [dnsext] Re: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Increasing hash collision resilience
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Re: DNSCurve
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Re: DNSCurve
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Increasing hash collision resilience
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [Namedroppers-honest] [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Re: DNSCURVE
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: DNSCURVE
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Re: DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: DNSCURVE
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Re: DNSCURVE
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Increasing hash collision resilience
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Increasing hash collision resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Re: DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Re: DNSCURVE
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Increasing hash collision resilience
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Re: DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Increasing hash collision resilience
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Increasing hash collision resilience
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: Desperate plea for 0x20, was Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• VS: Re: [dnsext] Increasing hash collision resilience
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] DNSCURVE
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] Increasing hash collision resilience
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] DNAME update draft UD bit
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] DNAME update draft UD bit
  • From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
• RE: [dnsext] Increasing hash collision resilience
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: Basil Dolmatov <dol@cryptocom.ru>
• RE: [dnsext] Increasing hash collision resilience
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: Adoption criteria, was Re: [dnsext] DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• RE: [dnsext] Increasing hash collision resilience
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Adoption criteria, was Re: [dnsext] DNSCURVE
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] DNAME update draft UD bit
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] DNAME update draft UD bit
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Increasing hash collision resilience
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] Re: Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: bmanning@vacation.karoshi.com
• [dnsext] DNAME update draft UD bit
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Increasing hash collision resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: DNSCURVE
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: bmanning@vacation.karoshi.com
• RE: [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: bert hubert <bert.hubert@netherlabs.nl>
• [dnsext] Re: DNSCURVE
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Security of the DNS, holistic approach (Was: DNSCURVE
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: DNSCURVE
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Allocation of EDNS0 option codes (Was: dropping request for adoption of EDNS-PING
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Increasing hash collision resilience
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNSCURVE
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] DNSCURVE
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] DNSCURVE
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] DNSCURVE
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] DNSCURVE
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] DNSCURVE
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: [dnsext] DNSCURVE
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: [dnsext] DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] DNSCURVE
  • From: Matthew Dempsky <matthew@dempsky.org>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] DNSCURVE
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Federico Lucifredi <lucifred@post.harvard.edu>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: Encouragement of debate (was: [dnsext] Support for EDSN0 PING)
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: bmanning@vacation.karoshi.com
• Re: dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: Bart Smit <bit@pipe.nl>
• dropping request for adoption of EDNS-PING, was Re: [dnsext] Point of order
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Adopting GOST digital signature algorithm document
  • From: bmanning@vacation.karoshi.com
• [dnsext] Adopting GOST digital signature algorithm document
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Support to adopt EDNS PING (was Re: [dnsext] Point of order)
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Support for EDSN0 PING
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] TSIG, TKEY, and IPSEC
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Point of order
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Support for EDSN0 PING
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Support for EDSN0 PING
  • From: "Bart Smit" <bit@pipe.nl>
• Encouragement of debate (was: [dnsext] Support for EDSN0 PING)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Support for EDSN0 PING
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Support for EDSN0 PING
  • From: niels=ietfops@bakker.net
• Re: [dnsext] Support for EDSN0 PING
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• Re: [dnsext] Support for EDSN0 PING
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] Support for EDSN0 PING
  • From: "Bart Smit" <bit@pipe.nl>
• Re: Desperate plea for 0x20, was Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Federico Lucifredi <flucifredi@acm.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: niels=ietfops@bakker.net (Niels Bakker)
• RE: [dnsext] Forgery resilience and meeting in Stockholm
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• RE: Desperate plea for 0x20, was Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@netherlabs.nl>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Desperate plea for 0x20, was Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: Desperate plea for 0x20, was Re: [dnsext] Forgery resilience andmeeting in Stockholm
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Desperate plea for 0x20, was Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Shane Kerr <shane_kerr@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Shane Kerr <shane_kerr@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• [dnsext] RFC 2930 (and 2931) can do what we seem to want/need here
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] signing referral NSs and glue
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Matt Larson <mlarson@verisign.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: "Roy Arends" <roy@nominet.org.uk>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Matthijs Mekking <matthijs@NLnetLabs.nl>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Bert <bert@secret-wg.org>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] WGLC TSIG MD5 Deprecated
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] Forgery resilience and meeting in Stockholm
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Forgery resilience and meeting in Stockholm
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] WGLC TSIG MD5 Deprecated
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• [dnsext] new version of tsig-md5-deprecated I-D available
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-03.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Scott Rose <scottr@nist.gov>
• Re: [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Jeroen Massar <jeroen@unfix.org>
• Re: [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Joe Abley <jabley@hopcount.ca>
• Re: [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Mark Andrews <Mark_Andrews@isc.org>
• [dnsext] Domain "Flag" to indicate (non-)availability of automatic DNS updates for reverse DNS
  • From: Jeroen Massar <jeroen@unfix.org>
• [dnsext] Last Call: draft-ietf-dnsext-dnsproxy (DNS Proxy Implementation Guidelines) to BCP
  • From: The IESG <iesg-secretary@ietf.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] SEP bit
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Re: I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] SEP bit
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] SEP bit
  • From: John Dickinson <jad@jadickinson.co.uk>
• [dnsext] DNSEXT WG document status
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ted Lemon <mellon@fugue.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] Request for adoption of draft-hubert-ulevitch-edns-ping.txt as a working group document
  • From: Francis Dupont <Francis.Dupont@fdupont.fr>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] I-D Action:draft-ietf-dnsext-tsig-md5-deprecated-02.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• RE: [dnsext] we need an IAB statement on Secure DNS
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: niels@bakker.net (Niels Bakker)
• RE: [dnsext] we need an IAB statement on Secure DNS
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: niels=ietfops@bakker.net (Niels Bakker)
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ted Lemon <mellon@fugue.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: David Conrad <drc@virtualized.org>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-13.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-13.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Document Advancement: draft-ietf-dnsext-dnsproxy-05.txt
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Thierry Moreau <thierry.moreau@connotech.com>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] Re: Thinking about a DNSSEC api...
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: [dnsext] we need an IAB statement on Secure DNS
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• RE: [dnsext] we need an IAB statement on Secure DNS
  • From: <jmiller@godaddy.com>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Andrew Sullivan <ajs@shinkuro.com>
• RE: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Matthew Dempsky <matthew@dempsky.org>
• RE: [dnsext] we need an IAB statement on Secure DNS
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] we need an IAB statement on Secure DNS
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] we need an IAB statement on Secure DNS
  • From: Paul Vixie <vixie@isc.org>
• RE: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Antoin Verschuren" <Antoin.Verschuren@sidn.nl>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Stefan Schmidt <zaphodb@zaphods.net>
• [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-05.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@gmail.com>
• [dnsext] Thinking about a DNSSEC api...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] "Network bit order" in RFC 3845
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] "Network bit order" in RFC 3845
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] "Network bit order" in RFC 3845
  • From: Tony Finch <dot@dotat.at>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Florian Weimer <fweimer@bfk.de>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ray.Bellis@nominet.org.uk
• RE: Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Publishing NS features in the DNS, was Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• RE: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• [dnsext] Re: Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: Request for adoption of draft-hubert-ulevitch-edns-ping.txt as a working group document
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] "Network bit order" in RFC 3845
  • From: Donald Eastlake <d3e3e3@gmail.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: David Blacka <davidb@verisign.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Matthew Dempsky <matthew@dempsky.org>
• DNSSEC-aware applications (was [dnsext] Re: Request for adoption)
  • From: Danny Mayer <mayer@gis.net>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] "Network bit order" in RFC 3845
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: bert hubert <bert.hubert@gmail.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Otmar Lendl <lendl@nic.at>
• Re: [dnsext] NSEC for preemptive assertion of nonexistence
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: [dnsext] NSEC for preemptive assertion of nonexistence
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] NSEC for preemptive assertion of nonexistence
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Fwd: [Cfrg] DNSSEC considering adopting GOST R 34.10-2001 and GOST R 34.11-94
  • From: Olafur Gudmundsson <ogud@ogud.com>
• [dnsext] Adopt EDNS0 Ping, benefits vs disadvantages ?
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] NSEC for preemptive assertion of nonexistence
  • From: John Dickinson <jad@jadickinson.co.uk>
• Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext]Re: Request for adoption))
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] NSEC for preemptive assertion of nonexistence
  • From: Stuart Cheshire <cheshire@apple.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• Re: [dnsext] Re: Securing hop by hop
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Re: EDNS ping mechanisms
  • From: Florian Weimer <fweimer@bfk.de>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Re: Securing hop by hop
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Tony Finch <dot@dotat.at>
• Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Shane Kerr <shane@ca.afilias.info>
• [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: Securing hop by hop
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Matthew Dempsky <matthew@dempsky.org>
• [dnsext] Re: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• RE: Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: "Aki Tuomi" <Aki.Tuomi@tdc.fi>
• Securing hop by hop (was Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption))
  • From: Shane Kerr <shane@ca.afilias.info>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Samuel Weiler <weiler@tislabs.com>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Samuel Weiler <weiler@watson.org>
• Re: [dnsext] Request for adoption of draft-hubert-ulevitch-edns-ping.txt as a working group document
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Request for adoption of draft-hubert-ulevitch-edns-ping.txt as a working group document
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: bmanning@vacation.karoshi.com
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: gson@araneus.fi (Andreas Gustafsson)
• Re: [dnsext] Re: Request for adoption
  • From: Tony Finch <dot@dotat.at>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Contradictions in NSEC3 wording in draft-ietf-dnsext-dnssec-rsasha256
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: bert hubert <bert.hubert@gmail.com>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: "George Barwood" <george.barwood@blueyonder.co.uk>
• Re: [dnsext] WGLC summary: DNS Proxy Implementation Guidelines
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] Bigger QueryIDs
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Bigger QueryIDs
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: [dnsext] Bigger QueryIDs
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] Bigger QueryIDs
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Bigger QueryIDs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Bigger QueryIDs
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] Bigger QueryIDs
  • From: Alex Bligh <alex@alex.org.uk>
• Re: [dnsext] Bigger QueryIDs
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Bigger QueryIDs
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Cookies, for bigger IDs (Was: Request for adoption
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] WGLC summary: DNS Proxy Implementation Guidelines
  • From: Ray.Bellis@nominet.org.uk
• [dnsext] handshakes and bigger QueryIDs
  • From: Jim Reid <jim@rfc1035.com>
• [dnsext] Bigger QueryIDs
  • From: Jim Reid <jim@rfc1035.com>
• Re: [dnsext] Re: Request for adoption
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• [dnsext] Re: EDNS ping mechanisms
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] Re: Request for adoption
  • From: Ted Lemon <Ted.Lemon@nominum.com>
• Re: [dnsext] Re: Request for adoption
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: Request for adoption
  • From: Michael Graff <michael_graff@isc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] Re: Request for adoption
  • From: Paul Vixie <vixie@isc.org>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: EDNS ping mechanisms (was [dnsext] Re: Request for adoption )
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• [dnsext] Re: Request for adoption
  • From: Michael Graff <michael_graff@isc.org>
• [dnsext] Re: Request for adoption
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• [dnsext] Re: Request for adoption
  • From: Michael Graff <michael_graff@isc.org>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: "Jeffrey A. Williams" <jwkckid1@ix.netcom.com>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-04.txt
  • From: Internet-Drafts@ietf.org
• [dnsext] WGLC summary: DNS Proxy Implementation Guidelines
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Florian Weimer <fw@deneb.enyo.de>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Florian Weimer <fw@deneb.enyo.de>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Peter Koch <pk@DENIC.DE>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Dan Simon <dansimon@microsoft.com>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Dan Simon <dansimon@microsoft.com>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Peter Koch <pk@DENIC.DE>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Florian Weimer <fw@deneb.enyo.de>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Dan Simon <dansimon@microsoft.com>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Donald Eastlake <d3e3e3@gmail.com>
• TLSFP! Not SSLFP! (was: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: Request for adoption (was: [dnsext] New draft has been posted)
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Request for adoption (was: [dnsext] New draft has been posted)
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] New RRTYPE assignment request: SSLFP RRTYPE Request
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] Fwd: I-D ACTION:draft-dolmatov-dnsext-dnssec-gost-00.txt
  • From: "W.C.A. Wijngaards" <wouter@NLnetLabs.nl>
• [dnsext] Re: New draft has been posted
  • From: Basil Dolmatov <dol@cryptocom.ru>
• Re: [dnsext] Fwd: I-D ACTION:draft-dolmatov-dnsext-dnssec-gost-00.txt
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] Fwd: I-D ACTION:draft-dolmatov-dnsext-dnssec-gost-00.txt
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• [dnsext] New draft has been posted
  • From: Basil Dolmatov <dol@cryptocom.ru>
• [dnsext] blast from the past
  • From: Paul Vixie <vixie@isc.org>
• [dnsext] Re: draft-ietf-dnsext-axfr-clarify-11
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• [dnsext] draft-ietf-dnsext-axfr-clarify-11
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] I-D ACTION:draft-ietf-dnsext-axfr-clarify-11.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] HAHAHAHA...
  • From: "Olaf M. Kolkman" <olaf@NLnetLabs.nl>
• Re: [dnsext] HAHAHAHA...
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] draft-ietf-dnsext-dnsproxy-03 nits
  • From: Alfred Hönes <ah@tr-sys.de>
• [dnsext] HAHAHAHA...
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-15.txt
  • From: ap <Andreas.Papst@univie.ac.at>
• Re: [dnsext] draft-wijngaards-dnsext-trust-history-02
  • From: "W.C.A. Wijngaards" <wouter@nlnetlabs.nl>
• [dnsext] Re: WGLC: DNS Proxy Implementation Guidelines
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] draft-wijngaards-dnsext-trust-history-02
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-15.txt
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-12.txt
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-12.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Arifumi Matsumoto <arifumi@nttv6.net>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Paul Selkirk <Paul_Selkirk@isc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael Graff <michael_graff@isc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Paul Hoffman <paul.hoffman@vpnc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] IANA considerations in the RSA-SHA2 draft
  • From: Andrew Sullivan <ajs@shinkuro.com>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Olafur Gudmundsson <ogud@ogud.com>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] IANA considerations in the RSA-SHA2 draft
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Evan Hunt <Evan_Hunt@isc.org>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] IANA considerations in the RSA-SHA2 draft
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Francisco Arias <francisco@arias.com.mx>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Evan Hunt <Evan_Hunt@isc.org>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Alan Barrett <apb@cequrux.com>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] question on RFC 5011, section 2.4.3
  • From: Michael Graff <michael_graff@isc.org>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Alex Bligh <alex@alex.org.uk>
• RE: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: "Griffiths, Chris" <Chris_Griffiths@Cable.Comcast.com>
• [dnsext] question on RFC 5011, section 2.4.3
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Ray.Bellis@nominet.org.uk
• Re: [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Paul Selkirk <Paul_Selkirk@isc.org>
• [dnsext] WGLC: DNS Proxy Implementation Guidelines
  • From: Ólafur Guðmundsson /DNSEXT chair <ogud@ogud.com>
• Re: [dnsext] IANA considerations in the RSA-SHA2 draft
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: David McGrew <mcgrew@cisco.com>
• IANA-clarify? ;) was Re: [dnsext] IANA considerations in ...
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] IANA considerations in the RSA-SHA2 draft that's going around
  • From: Jelte Jansen <jelte@NLnetLabs.nl>
• [dnsext] IANA considerations in the RSA-SHA2 draft that's going around
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: Michael StJohns <mstjohns@comcast.net>
• Re: [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: Michael StJohns <mstjohns@comcast.net>
• [dnsext] New Version Notification for draft-mcgrew-tss-02 (fwd)
  • From: Alfred Hönes <ah@tr-sys.de>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-11.txt
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-15.txt
  • From: ap <Andreas.Papst@univie.ac.at>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Danny Mayer <mayer@gis.net>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnssec-rsasha256-11.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] Nearly there ...
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Ask Bjørn Hansen <ask@develooper.com>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Danny Mayer <mayer@gis.net>
• [dnsext] [Fwd: I-D Action:draft-bagnulo-behave-dns64-02.txt]
  • From: marcelo bagnulo braun <marcelo@it.uc3m.es>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-15.txt
  • From: Andrew Sullivan <ajs@shinkuro.com>
• [dnsext] I-D Action:draft-ietf-dnsext-rfc2672bis-dname-15.txt
  • From: Internet-Drafts@ietf.org
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Jari Arkko <jari.arkko@piuha.net>
• [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Mark Andrews <Mark_Andrews@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Chris Thompson <cet1@cam.ac.uk>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: OndÅej Surà <ondrej.sury@nic.cz>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: bmanning@vacation.karoshi.com
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Florian Weimer <fweimer@bfk.de>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Edward Lewis <Ed.Lewis@neustar.biz>
• RE: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Christian Huitema <huitema@windows.microsoft.com>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] RFC 3484 section 6 rule 9 causing more operational problems
  • From: Paul Vixie <vixie@isc.org>
• Re: [dnsext] Re: RFC 3484 section 6 rule 9 causing more operational problems
  • From: Tony Finch <dot@dotat.at>
• Re: [dnsext] I-D Action:draft-ietf-dnsext-dnsproxy-03.