From owner-namedroppers@ops.ietf.org Sun Apr 01 02:42:44 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HXtm0-00048R-BR; Sun, 01 Apr 2007 02:42:44 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HXtlw-0001a3-0S; Sun, 01 Apr 2007 02:42:44 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HXteg-0002aa-Dk
	for namedroppers-data@psg.com; Sun, 01 Apr 2007 06:35:10 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [213.154.224.1] (helo=open.nlnetlabs.nl)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <olaf@open.nlnetlabs.nl>)
	id 1HXted-0002a6-P2
	for namedroppers@ops.ietf.org; Sun, 01 Apr 2007 06:35:09 +0000
Received: from open.nlnetlabs.nl (localhost [127.0.0.1])
	by open.nlnetlabs.nl (8.13.8/8.13.8) with ESMTP id l316Z3QI050449
	for <namedroppers@ops.ietf.org>; Sun, 1 Apr 2007 08:35:03 +0200 (CEST)
	(envelope-from olaf@open.nlnetlabs.nl)
Received: (from olaf@localhost)
	by open.nlnetlabs.nl (8.13.8/8.13.8/Submit) id l316Z3HD050448
	for namedroppers@ops.ietf.org; Sun, 1 Apr 2007 08:35:03 +0200 (CEST)
	(envelope-from olaf)
Date: Sun, 1 Apr 2007 08:35:03 +0200 (CEST)
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Message-Id: <200704010635.l316Z3HD050448@open.nlnetlabs.nl>
To: namedroppers@ops.ietf.org
Subject: DNSEXT list policy
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8


- List Purpose

  namedroppers@ops.ietf.org is the mailing list for the IETF DNSEXT
  working group.  

  See <http://www.ietf.org/html.charters/dnsext-charter.html> for the
  wg charter.  Messages should be on topics appropriate to the dnsext
  wg, which are various discussion of the DNS protocols or
  administrivia of the WG itself.

- Specific items that are not not appropriate for posting

  Calls for papers, announcements of events not directly relevant to
  the DNS protocols, etc. are not appropriate.  

  Discussion of problems with particular implementations,
  announcements of releases, sites' misconfigurations, pleas for help
  with specific implementations, etc.  should be done on mailing lists
  for the particular implementations.

  There is a working group for dns operational practice, DNSOP, whose
  charter can be found at
  <http://www.ietf.org/html.charters/dnsop-charter.html>. Items
  relevant to the DNSOP charter are to be discussed on the DNSOP
  mailinglist.

  Discussion about the quality of implementations is outside the scope
  of this list.

- Moderation

  Moderation is based on "subscriber-only with spam filter". To
  counter a certain class of spam mails messages over 20000
  characters, originating from list subscribers, will be held for
  moderations.

  Questions or concerns related to the acceptance or rejection of
  specific messages to the namedroppers mailing list should first be
  discussed with the wg chairs, with followup appeals using the normal
  appeals process of rfc 2026 (i.e. follup with area directors, then
  iesg, etc.).

  There is a mailing list for the discussion of ietf processes, which
  includes any general discussion of the moderation of ietf mailing
  lists.  it is poised@lists.tislabs.com

  
---

NOTE WELL:

All statements related to the activities of the IETF and addressed to the 
IETF are subject to all provisions of Section 10 of RFC 2026, which grants 
to the IETF and its participants certain licenses and rights in such 
statements.

Such statements include verbal statements in IETF meetings, as well as 
written and electronic communications made at any time or place, which are 
addressed to

    - the IETF plenary session,
    - any IETF working group or portion thereof,
    - the IESG, or any member thereof on behalf of the IESG,
    - the IAB or any member thereof on behalf of the IAB,
    - any IETF mailing list, including the IETF list itself,
      any working group or design team list, or any other list
      functioning under IETF auspices,
    - the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other function, 
that are clearly not intended to be input to an IETF activity, group or 
function, are not subject to these provisions.


----------------------------------------------------------------------
$Id: dnsext-list-policy.txt,v 1.8 2005/01/12 15:54:51 olaf Exp $

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 05:11:50 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYIZq-0003Fu-Gj; Mon, 02 Apr 2007 05:11:50 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYIZl-0003Yl-5O; Mon, 02 Apr 2007 05:11:50 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYISn-000ExK-99
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 09:04:33 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [192.134.4.11] (helo=mx2.nic.fr)
	by psg.com with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <mohsen.souissi@nic.fr>)
	id 1HYISk-000EwS-Mw
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 09:04:32 +0000
Received: from mx2.nic.fr (localhost [127.0.0.1])
	by mx2.nic.fr (Postfix) with SMTP id 798BD1C011B;
	Mon,  2 Apr 2007 11:04:29 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163])
	by mx2.nic.fr (Postfix) with ESMTP id 74A0E1C0119;
	Mon,  2 Apr 2007 11:04:28 +0200 (CEST)
Received: from kerkenna.nic.fr (kerkenna.nic.fr [192.134.4.98])
	by relay2.nic.fr (Postfix) with ESMTP id 708BC58ED21;
	Mon,  2 Apr 2007 11:04:28 +0200 (CEST)
Received: from kerkenna.nic.fr (localhost [127.0.0.1])
	by kerkenna.nic.fr (8.13.8/8.13.8) with ESMTP id l3294P9j011957;
	Mon, 2 Apr 2007 09:04:26 GMT
	(envelope-from souissi@kerkenna.nic.fr)
Received: (from souissi@localhost)
	by kerkenna.nic.fr (8.13.8/8.13.8/Submit) id l3294NZG011956;
	Mon, 2 Apr 2007 11:04:23 +0200 (CEST)
	(envelope-from souissi)
Date: Mon, 2 Apr 2007 11:04:23 +0200
From: Mohsen Souissi <mohsen.souissi@nic.fr>
To: =?iso-8859-1?Q?=D3lafur_Gu=F0mundsson?= /DNSEXT co-chair <ogud@ogud.com>
Cc: namedroppers@ops.ietf.org
Subject: Re: DNSEXT future
Message-ID: <20070402090423.GX56958@kerkenna.nic.fr>
References: <200703270035.l2R0ZNKK072363@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200703270035.l2R0ZNKK072363@ogud.com>
User-Agent: Mutt/1.4.2.2i
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9

My 2 eurocents below:

 On 26 Mar, Ólafur Guðmundsson /DNSEXT co-chair wrote:
 | 
 | Dear Colleagues:

[...]
 
 | For this reason we asked the meeting and our AD for guidance on what to do
 | with the working group. The three options are
 | 	A. keep the working group open
 | 	B. Put the group to sleep/hibernate
 | 	C. Close the working group

==> I'm in favour of option "B" if "sleep/hibernate" means that the wg:

- remains the reference forum for discussions and decision process
  wrt future new DNS extensions requests, either on the mailing-list
  (which should remain open in all cases), or at face2face IETF
  meetings when there is enough material to justify holding a session

- remains the reference wg for reporting any issues (specification bugs,
  clarification requests, ...) wrt to the running DNS protocol as a
  whole (ie the core DNS + the recent extensions including DNSSEC)

- is supposed to be the place (a sort of thinktank) where potential
  DNS2 design/specicications will/would take place


Otherwise, I would prefer option A. 


I believe that DNS protocol is so important for the whole Internet service
infrastructure that it would be wise to keep at least a background
activity on the three above-mentioned technical aspects...


Mohsen.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 10:00:21 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYN53-0003gA-B4; Mon, 02 Apr 2007 10:00:21 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYN4z-0002zb-U2; Mon, 02 Apr 2007 10:00:21 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYMyB-0008kh-H4
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 13:53:15 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [199.212.90.4] (helo=monster.hopcount.ca)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <jabley@ca.afilias.info>)
	id 1HYMy6-0008k1-2w
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 13:53:14 +0000
Received: from yxu1a17.hopcount.ca ([199.212.90.17])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD))
	(envelope-from <jabley@ca.afilias.info>)
	id 1HYN0m-000Eqs-S3; Mon, 02 Apr 2007 13:55:57 +0000
In-Reply-To: <200703270035.l2R0ZNKK072363@ogud.com>
References: <200703270035.l2R0ZNKK072363@ogud.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <001A8F70-F25B-47A9-AAE1-299BF7543696@ca.afilias.info>
Cc: namedroppers@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
From: Joe Abley <jabley@ca.afilias.info>
Subject: Re: DNSEXT future 
Date: Mon, 2 Apr 2007 09:52:49 -0400
To: =?ISO-8859-1?Q?=D3lafur_Gu=F0mundsson_/DNSEXT_co-chair?= <ogud@ogud.com>
X-Mailer: Apple Mail (2.752.3)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69


On 26-Mar-2007, at 20:36, =D3lafur Gu=F0mundsson /DNSEXT co-chair wrote:

> [...]
>
> For this reason we asked the meeting and our AD for guidance on =20
> what to do
> with the working group. The three options are
> 	A. keep the working group open
> 	B. Put the group to sleep/hibernate
> 	C. Close the working group
>
> [...]
>
> The purpose of this message is to gauge the mailing list as to =20
> which option
> they think is the most appropriate.

I am quite ignorant of the procedural practicality of doing B, but I =20
seem to think I heard from several well-informed people in the over-=20
filled room in Prague that there is both precedent and accommodation =20
to choose B.

That being the case, it seems sensible to me to choose B along with a =20=

time at which the decision could be reviewed based on experience =20
gained during the intervening interval. If during the review it seems =20=

that we might as well have chosen C, then perhaps the group could be =20
closed by consensus at that time. On the other hand, if there are =20
indications to the contrary, perhaps we could continue with B, or =20
perhaps rise from the ashes ("A") with new objectives.

So, for example, "hibernation for 18 months followed by review" =20
sounds like a plausible option.


Joe



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 11:09:54 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYOAM-0003JT-CW; Mon, 02 Apr 2007 11:09:54 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYOAI-00064T-QD; Mon, 02 Apr 2007 11:09:54 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYO60-000FSq-CP
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 15:05:24 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <Ed.Lewis@neustar.biz>)
	id 1HYO5r-000FSH-Hu
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 15:05:18 +0000
Received: from [192.168.1.102] (hlid.ogud.com [66.92.146.160])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l32F2vXp027469;
	Mon, 2 Apr 2007 11:02:59 -0400 (EDT)
	(envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a0623090ec236c1be9df4@[192.168.1.102]>
Date: Mon, 2 Apr 2007 11:04:06 -0400
To: namedroppers@ops.ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: DNSEXT (premature?) obituary notice
Cc: ed.lewis@neustar.biz
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de

Nothin' like an obituary to bring out all the=20
love...see the "action items" I clipped from this=20
thread attached below.

It seems like there is a long laundry list of=20
work items that fit under the WG's charter, plus=20
some more that don't (e.g., expansion of record=20
synthesis).  What I read from this is that there=20
is a demand/need for furthering DNS work.

What I also read from this lingering list of=20
wants and needs is that there isn't a lot of real=20
desire to finish off the work.  It's not that=20
folks are lazy, the desire to finish off work=20
comes from the work being meaningful and=20
rewarding.  I don't see DNS'ers sitting under=20
palm trees drinking mai-tais while this list=20
lingers, we are busy doing other work.

Or perhaps we do have time we could spend on this=20
work, but there's been no "bolt of lightening" to=20
stir the pot and cause reactions to happen.

There have been stalled WG's in the past, and I=20
think DNSEXT is about there too.  Other cases=20
have been caused by two competing approaches head=20
butting each other, or maybe IPR claims, or maybe=20
social/political/etc. issues which are not=20
technical.  I don't think we suffer that here, it=20
just seems like there's been no push to really=20
finish off the work.

If the group is to stay open, what is going to=20
make this work get done?  A chair saying "read=20
and comment on ASAP" is not making us jump,=20
that's apparently not an effective motivational=20
tool in an all-volunteer environment.  What would=20
be more interesting that a list of "I'd like to=20
see..." is a list of "Here's what's going to make=20
this happen if we have review..."  I'm not=20
accusing any of the below folks of issuing=20
"unfunded mandates" because it is good just to=20
have a list of work items - but the list isn't=20
going to shrink through success unless someone=20
(else) does or leads the work.

Even if a need exists but there is no will to do=20
it, the list of needs will shrink if we "give up=20
the dream."

I'm in no hurry to see the WG close, but I wonder=20
- who cares if the work list is completed?  Does=20
anyone (outside of the WG) care?  *If no one=20
cares*, I think it is time we all moved on even=20
with unfinished business.  If anyone cares, how=20
can they help the WG along to finishing off the=20
list?

The main burst of DNSSEC energy is situated in=20
Sweden, there was an ICANN panel last week of 6=20
presentations, 5 from Sweden and another from=20
Bulgaria.  In the presentation from an ISP (Mats=20
Dufberg, TeliaSonera,=20
(http://icann.org/meetings/lisbon/presentation-dnssec-28mar07-dufberg.pdf)=
=20
he mentions the need for a signed root.  He's one=20
of many.  Is anyone listening to these requests?

On one hand I want to encourage the WG to clean=20
up the milestones to match what's below and=20
organize the work around it.  On the other hand,=20
I don't see that the work will be pay off.  Maybe=20
we all would be more useful to society under a=20
palm trees and drinking mai-tais.

Should we itemize this list into milestones?=20
Should we just forget about it?  Where's the=20
energy for all this?  Those are my thoughts.

At 20:36 -0400 3/26/07, =D3lafur Gu=F0mundsson /DNSEXT co-chair wrote:
>All the remaining work in the group are close to completion,
>with the exception of
>	ECC DNSKEY specification.
>	advancing RFC's up the standards track.
>Both of these items have not had great interest or activity.
>A potential new item for the working group is the provide input on the
>processing of RFC2929bis templates while that process is stabilizing.

At 1:13 +0000 3/27/07, Paul Vixie wrote:
>i'd like to see roy's version of DLV standardized before we quit, that's al=
l.

At 21:55 -0400 3/26/07, Edward Lewis wrote:
>What about DNAME?  That's the only topic that caused any stir of engineerin=
g
>at the meeting last week.

At 22:14 -0400 3/26/07, Michael StJohns wrote:
>Would it be fair to characterize (B) as "We'll continue to be open to
>standardize new RR Types that don't require changes to the base DNS protoco=
l,

At 12:27 +1000 3/27/07, Mark Andrews wrote:
>	We really do need to see interop from new vendors that
>	wern't around when a RFC is developed to be able to move
>	forward RFCs on the standards track.  We had a perfect
>	example of this in the weeks leading up to IETF 68.
>
>	I still want to see the RFCs advanced.  I would however be
>	happy with waiting a year or so before looking at them as
>	I feel that most of the wg feel slightly burnout at this
>	stage.  Recessing for a year or so would be a good idea.

At 8:20 +0200 3/27/07, Roy Arends wrote:
>As for DNSEXT, I don't think we're done at all. There is indeed DLV, and
>there is the last mile. There is also the transparency and the end-to-end
>paradigm I'd like to see written up, explicitly for the DNS. There is
>key-management, rollover, and once 2929-bis is done, I hope to see more
>record types hit the iana registry. Some of this can be wrapped up in
>DNSOP, but not all of it.

At 11:28 +0100 3/27/07, David Conrad wrote:
>Key rollover?

At 9:51 -0400 3/27/07, =D3lafur Gu=F0mundsson /DNSEXT co-chair wrote:
>[A] Read and comment on ASAP:
>http://ietf.org/internet-drafts/draft-ietf-dnsext-rfc2672bis-dname-01.txt
>http://ietf.org/internet-drafts/draft-ietf-dnsext-forgery-resilience-00.txt

At 11:14 -0400 3/27/07, Dean Anderson wrote:
>I think the working group needs to properly resolve AXFR-clarify.
>I will submit a draft to do this.
>
>IXFR also needs work.

At 11:48 -0400 3/27/07, Suresh Krishnaswamy wrote:
>The last time I asked informally, the answer that I got was that API work w=
as
>not within the scope of this working group, and extruding detailed validati=
on
>policy and authentication chain information on-the-wire, even though within
>scope, was a bad idea. Is this still the working groups sentiment? If
>draft-hayatnagarkar-dnsext-validator-api is not within scope for DNSEXT,
>which working group is better suited to=20
>standardize last-mile issues/solutions?

-- 
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis                                                +1-571-434-5468
NeuStar

Sarcasm doesn't scale.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 11:27:04 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYOQy-0000nk-KN; Mon, 02 Apr 2007 11:27:04 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYOQs-00083A-A3; Mon, 02 Apr 2007 11:27:04 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYONt-000GoG-51
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 15:23:53 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [213.248.199.23] (helo=mx3.nominet.org.uk)
	by psg.com with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <jay@nominet.org.uk>)
	id 1HYONi-000GnR-9f
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 15:23:48 +0000
Received: from unknown (HELO notes1.nominet.org.uk) ([213.248.197.128])
  by mx3.nominet.org.uk with ESMTP; 02 Apr 2007 16:23:18 +0100
X-IronPort-AV: i="4.14,362,1170633600"; 
   d="scan'208"; a="7876489:sNHT38251024"
In-Reply-To: <198A730C2044DE4A96749D13E167AD37011E1271@MOU1WNEXMB04.vcorp.ad.vrsn.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: namedroppers@ops.ietf.org
Subject: Re: Protocol Policy Publication Was: DNSEXT future
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V702MAC_11052006 November 05, 2006
Message-ID: <OF546B39B8.8B0DA2CD-ON802572B1.00542F7E-802572B1.005487C4@nominet.org.uk>
From: Jay Daley <jay@nominet.org.uk>
Date: Mon, 2 Apr 2007 16:23:17 +0100
X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at
 02/04/2007 04:23:18 PM,
	Serialize complete at 02/04/2007 04:23:18 PM
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

Phillip

> One issue that keeps coming up is the desire to publish some form of
> policy indication through the DNS.

I agree entirely.  This is important now and will only grow in importance.

> The question then is should this be a proposal made to DNSEXT or a 
> personal submission or what? 

A proposal.  I would like to think that DNS experts here can work this 
through, especially if you are proposing new record types, more use of 
prefixes and considering changes to the way wildcards work (or even just 
discussing them). 

Jay Daley
Nominet UK

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 13:01:24 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYPuG-00073P-1h; Mon, 02 Apr 2007 13:01:24 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYPuE-00085e-J6; Mon, 02 Apr 2007 13:01:24 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYPoX-000Odc-Gy
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 16:55:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS 
	autolearn=ham version=3.1.7
Received: from [204.152.187.1] (helo=sa.vix.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <vixie@vix.com>)
	id 1HYPoR-000Obv-0L
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 16:55:26 +0000
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 17E9411429
	for <namedroppers@ops.ietf.org>; Mon,  2 Apr 2007 16:55:22 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: namedroppers@ops.ietf.org
Subject: Re: DNSEXT (premature?) obituary notice 
In-Reply-To: Your message of "Mon, 02 Apr 2007 11:04:06 -0400."
             <a0623090ec236c1be9df4@[192.168.1.102]> 
References: <a0623090ec236c1be9df4@[192.168.1.102]> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Apr 2007 16:55:22 +0000
Message-ID: <60855.1175532922@sa.vix.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

note, this isn't a rant on ed, it's just that his note crystalized some ideas.

> What I also read from this lingering list of wants and needs is that there
> isn't a lot of real desire to finish off the work.  It's not that folks are
> lazy, the desire to finish off work comes from the work being meaningful
> and rewarding.  I don't see DNS'ers sitting under palm trees drinking
> mai-tais while this list lingers, we are busy doing other work.

there's more to this malaise than being too busy.  there's exhaustion, and
there's what you said, lack of "meaningful and rewarding."  this working group
is a perfect demonstration of "tyranny of the majority".  thirteen (13) years
into the experiment, we're once again at the 11th hour of dnssec as we've been
five times before, and we're now being told that the "auth-follows-delegation"
model (DS vs DLV) are undeployable due to root domain politics and economics.
we are also still working our way through "zonewalking-isn't-acceptable"
(NSEC3 and whitelies), and are apparently about to readdress the previous
answer to "security-can't-be-optional" (opt-in).  most of the stuff we thought
was done, wasn't.  most of what we thought was deployable, isn't.  most of
the people who were willing to "do it over" five times are pondering this 6th.

now, most investors (and most gamblers, and most engineers, and most lovers)
are willing to double down if they think they've still got "a shot at it," but
most want to know "why will this time be any different?"  which requires being
able to determine "why have we failed every time up through now?"  which means
taking a look at the key decisions and processes and cultures that led to five
straight undeployable results (which is to say, "failures").  let's party like
it's still 1994:

2065 failed because eastlake didn't understand DNS and noone else understood
security, so it was effectively ships-passing-in-the-night, unreviewed work,
doomed to burst into flame when the rubber finally met the road.  the IESG
thought they fixed this by merging DNSSEC with DNSIND and calling it DNSEXT,
to make sure subsequent work wasn't done in a double-blind environment.  this
fix seems to have worked-- subsequent failures were all different from this.

who wants to do 2535?  my favorite of all time is still the folks who rained
on opt-in not because they didn't want to use it, but because they didn't want
verisign to be able to use it.  a close second is the folks who thought that
what US-DoC/VeriSign/ICANN needed in order to mend their fences and learn to
live together in peace and harmony was shared responsibility for all of the
world's electronic commerce security.  an honourable mention goes out to the
folks who figured that the TLD operators who tightly restricted AXFR would all
be eager to drop their pants the moment NSEC came out.  and the thing that
makes these most interesting, from an anthropological standpoint, is that the
decisions were all made by what heinlein called "aunt millie" -- well meaning
decent people who considered it their sacred duty to save others from folly.

> I'm in no hurry to see the WG close, but I wonder - who cares if the work
> list is completed?  Does anyone (outside of the WG) care?  *If no one
> cares*, I think it is time we all moved on even with unfinished business.
> If anyone cares, how can they help the WG along to finishing off the list?

i think folks are (rightly) afraid to care, since they've seen what happens
to others who cared.  the majority is still standing by, ready to tyrannize.
IETF is an open-door society, and unless one counts the DNS Directorate,
there is no way to get anything done that anybody objects to.  (noting that
we might now have nearly perfect IP mobility if A6/DNAME had not been killed,
and i mean killed by a non-open non-IETF-like process.)  (and also noting
that the problems now being faced by IPv6 include all of the ones warned
about by the promoters of TUBA.)

> Should we itemize this list into milestones? Should we just forget about
> it?  Where's the energy for all this?  Those are my thoughts.

i believe that the strong desire shown for killing this working group comes
from the irrational belief that if we start over with a new charter and a
new name, the current tryannizing majority will lose interest and/or not be
able to find the next working group, and that only the smart constructive
creative baggage-free non-hating types will join the next mailing list or
attend the next set of meetings.  that's never been seen to work, but hope
springs eternal.  (we should have put more effort into MODA, i guess.)

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 14:05:17 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYQu5-000156-PD; Mon, 02 Apr 2007 14:05:17 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYQu4-0006P1-Fl; Mon, 02 Apr 2007 14:05:17 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYQp4-0004yN-Vf
	for namedroppers-data@psg.com; Mon, 02 Apr 2007 18:00:06 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO,INFO_TLD autolearn=no version=3.1.7
Received: from [207.219.45.62] (helo=mail.libertyrms.com)
	by psg.com with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <andrew@ca.afilias.info>)
	id 1HYQp2-0004xG-9U
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 18:00:05 +0000
Received: from andrew-vpn.int.libertyrms.com ([10.1.7.6] helo=trilby.local)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1HYQp1-0001WH-B5
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 14:00:03 -0400
Received: by trilby.local (Postfix, from userid 1019)
	id D431D2E4588; Mon,  2 Apr 2007 14:00:18 -0400 (EDT)
Date: Mon, 2 Apr 2007 14:00:18 -0400
From: Andrew Sullivan <andrew@ca.afilias.info>
To: namedroppers@ops.ietf.org
Subject: Re: DNSEXT (premature?) obituary notice
Message-ID: <20070402180017.GA19183@afilias.info>
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
References: <a0623090ec236c1be9df4@[192.168.1.102]> <60855.1175532922@sa.vix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <60855.1175532922@sa.vix.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-SA-Exim-Mail-From: andrew@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

On Mon, Apr 02, 2007 at 04:55:22PM +0000, Paul Vixie wrote:

> i believe that the strong desire shown for killing this working group comes
> from the irrational belief that if we start over with a new charter and a
> new name, the current tryannizing majority will lose interest and/or not be
> able to find the next working group,

I understand, but cannot agree with, this remark.  The desire seems to
be, from my point of view, the urge to end a "working group" that has
stopped working, and become mostly a group.  I suspect that if a
significant number of actual drafts and contributors to those drafts
showed up, the group might have a different reaction.  But I see
precious few actual drafts lining up with these ideas people have.  (I
am hereby explicitly promising review if I am pointed at some, FWIW.)

A
-- 
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<andrew@ca.afilias.info>                              M2P 2A8
jabber: ajsaf@jabber.org                 +1 416 646 3304 x4110

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 02 21:57:37 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYYHB-0000oY-0M; Mon, 02 Apr 2007 21:57:37 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYYH9-0000EK-Lq; Mon, 02 Apr 2007 21:57:36 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYYBb-000B9f-5P
	for namedroppers-data@psg.com; Tue, 03 Apr 2007 01:51:51 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO,SPF_PASS autolearn=ham version=3.1.7
Received: from [65.205.251.74] (helo=colibri.verisign.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <pbaker@verisign.com>)
	id 1HYYBZ-000B9O-AJ
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 01:51:50 +0000
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34])
	by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l331pmlV005348;
	Mon, 2 Apr 2007 18:51:48 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 2 Apr 2007 18:51:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: DNSEXT (premature?) obituary notice 
Date: Mon, 2 Apr 2007 18:51:28 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37011E1655@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <60855.1175532922@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DNSEXT (premature?) obituary notice 
Thread-Index: Acd1SMWxXJGd9AfaQY+C/jpWBj7DagAQRwuQ
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Paul Vixie" <paul@vix.com>, <namedroppers@ops.ietf.org>
X-OriginalArrivalTime: 03 Apr 2007 01:51:47.0682 (UTC) FILETIME=[A3C80C20:01C77592]
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5


> [mailto:owner-namedroppers@ops.ietf.org] On Behalf Of Paul Vixie

> note, this isn't a rant on ed, it's just that his note=20
> crystalized some ideas.

Ditto

> now, most investors (and most gamblers, and most engineers,=20
> and most lovers) are willing to double down if they think=20
> they've still got "a shot at it," but most want to know "why=20
> will this time be any different?"  which requires being able=20
> to determine "why have we failed every time up through now?" =20
> which means taking a look at the key decisions and processes=20
> and cultures that led to five straight undeployable results=20
> (which is to say, "failures").  let's party like it's still 1994:

I think that it's a continuation of the same impulse, namely considering =
the problem of DNS security as an exclusively technical exercise =
ignoring the fact that security is inescapably a social issue. Computers =
do not perform crime, people perform crime and they do so for social =
reasons (e.g. money).

I have spent quite a bit of time thinking (and modelling) the deployment =
problem. We have a double ended problem: there is no value for signers =
without verifiers and vice versa. How do we establish critical mass?

One possible answer I see is to use the DNS to distribute security =
sensitive information that provides a unilateral deployment benefit. =
Free Swan, SSH keys, DKIM and the like.=20


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Tue Apr 03 06:15:26 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYg2w-0005Rq-L6; Tue, 03 Apr 2007 06:15:26 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYg2s-0003zh-B9; Tue, 03 Apr 2007 06:15:26 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYfwQ-000M7a-LL
	for namedroppers-data@psg.com; Tue, 03 Apr 2007 10:08:42 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [195.54.233.68] (helo=shaun.rfc1035.com)
	by psg.com with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <jim@rfc1035.com>)
	id 1HYfwN-000M70-QN
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 10:08:41 +0000
Received: from [86.53.62.81] (account jim HELO [192.168.72.124])
  by shaun.rfc1035.com (CommuniGate Pro SMTP 5.1.4)
  with ESMTPSA id 161791; Tue, 03 Apr 2007 11:08:37 +0100
In-Reply-To: <a0623090ec236c1be9df4@[192.168.1.102]>
References: <a0623090ec236c1be9df4@[192.168.1.102]>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <46052853-565A-4D19-BAD1-207902C1FAD9@rfc1035.com>
Cc: namedroppers@ops.ietf.org
Content-Transfer-Encoding: 7bit
From: Jim Reid <jim@rfc1035.com>
Subject: Re: DNSEXT (premature?) obituary notice
Date: Tue, 3 Apr 2007 11:07:35 +0100
To: Edward Lewis <Ed.Lewis@neustar.biz>
X-Mailer: Apple Mail (2.752.2)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

On Apr 2, 2007, at 16:04, Edward Lewis wrote:

> What I read from this is that there is a demand/need for furthering  
> DNS work.

I'm not so sure. There is recognition that there are other things  
this WG could do. Though it's not yet clear what, if anything, these  
other things are.

> What I also read from this lingering list of wants and needs is  
> that there isn't a lot of real desire to finish off the work.

To be fair, I think this WG has scared away anyone who had ideas that  
were not DNSSEC related. It might be necessary to do outreach beyond  
the WG to re-engage with these guys.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Tue Apr 03 10:23:13 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYjuj-0006Pz-68; Tue, 03 Apr 2007 10:23:13 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYjuQ-0006sK-OT; Tue, 03 Apr 2007 10:23:13 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYjo3-000H6p-W0
	for namedroppers-data@psg.com; Tue, 03 Apr 2007 14:16:20 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS 
	autolearn=ham version=3.1.7
Received: from [32.97.110.149] (helo=e31.co.us.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <narten@us.ibm.com>)
	id 1HYjnv-000H6I-3Q
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 14:16:15 +0000
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227])
	by e31.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l33EGAML004404
	for <namedroppers@ops.ietf.org>; Tue, 3 Apr 2007 10:16:10 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l33EGA6j049554
	for <namedroppers@ops.ietf.org>; Tue, 3 Apr 2007 08:16:10 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l33EG9I3031849
	for <namedroppers@ops.ietf.org>; Tue, 3 Apr 2007 08:16:09 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-209-175.wecm.ibm.com [9.67.209.175])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l33EG7AK031698
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 3 Apr 2007 08:16:09 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l33EEgOF013012;
	Tue, 3 Apr 2007 10:14:50 -0400
Message-Id: <200704031414.l33EEgOF013012@cichlid.raleigh.ibm.com>
To: =?iso-8859-1?Q?=D3lafur?= =?iso-8859-1?Q?_Gu=F0mundsson?= /DNSEXT co-chair <ogud@ogud.com>
cc: namedroppers@ops.ietf.org
Subject: Re: DNSEXT future 
In-reply-to: <200703270035.l2R0ZNKK072363@ogud.com> 
References: <200703270035.l2R0ZNKK072363@ogud.com>
Comments: In-reply-to =?iso-8859-1?Q?=D3lafur?= =?iso-8859-1?Q?_Gu=F0mundsson?= /DNSEXT co-chair <ogud@ogud.com>
   message dated "Mon, 26 Mar 2007 20:36:10 -0400."
Date: Tue, 03 Apr 2007 10:14:42 -0400
From: Thomas Narten <narten@us.ibm.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab

> For this reason we asked the meeting and our AD for guidance on what to do
> with the working group. The three options are
> 	A. keep the working group open
> 	B. Put the group to sleep/hibernate

IMO, saying the WG  is "hibernating/sleeping/dormant" is a
misnomer. The implication is that it will become active again in the
future. I'm not sure that is true, or we want it to be. :-)

While I do like closing WGs (generally), it seems that DNS-related
issues will continue to pop up (some of them in the Bad Idea
category), and having an official WG for dealing with such issues is a
more open and transparent way of doing so than via a directorate or
other means. Speaking as a former  AD, one generally welcomes having a
WG say "we don't need this" to the AD having to say so themselves and
then be accused of having an agenda, etc.

Note that the another WG that has been mentioned as an example is
pppext. Clearly PPP work is finished and has been for a long
time. Yet, that area has had the problem where ideas-killed-long-ago
magically appear as individual submissions. Having a WG around to
review such documents has proven useful.

The  PPPEXT charter says:

> The Point-to-Point Protocol (PPP, RFC 1661) is a mature protocol with a
> large number of subprotocols, encapsulations and other extensions. The 
> group will actively advance PPP's most useful extensions to full 
> standard, while defending against further enhancements of questionable 
> value.

A revised DNSEXT charter could easily summarize the state of DNS work
(done, or whatever) and outline what it thinks the role of the WG is.

So, I'd favor a recharter, with a new scope that says things like:

  - DNS work is largely finished, WG is not soliciting
    extensions/enhancements (that could be done via a BOF if
    appropriate)

  - Will work on revising unclear documents and advancing them as
    appropriate.

  - does not expect to  have face-to-face meetings

  - will only take on new work items if there is strong support that
    the work is needed, and then in consultation with the AD.

  - explicitely list the remaining work items that are almost done but
    need to be completed

Or some such.

Thomas    

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Tue Apr 03 11:15:25 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HYkjF-00069T-Go; Tue, 03 Apr 2007 11:15:25 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HYken-0002LT-J2; Tue, 03 Apr 2007 11:11:14 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HYkbj-000Mgs-1R
	for namedroppers-data@psg.com; Tue, 03 Apr 2007 15:07:39 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [130.105.36.66] (helo=cirrus.av8.net)
	by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.63 (FreeBSD))
	(envelope-from <dean@av8.com>)
	id 1HYkbX-000Mfn-Ck
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 15:07:36 +0000
Received: from sr22.av8.net (sr22.av8.net [198.3.136.5])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id l33F7Ppp005148
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 3 Apr 2007 11:07:25 -0400
Date: Tue, 3 Apr 2007 11:07:25 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@sr22.av8.net
To: Paul Vixie <paul@vix.com>
cc: namedroppers@ops.ietf.org
Subject: Re: DNSEXT (premature?) obituary notice 
In-Reply-To: <60855.1175532922@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0704031047240.31291-100000@sr22.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

On Mon, 2 Apr 2007, Paul Vixie wrote:

> 
> i think folks are (rightly) afraid to care, since they've seen what happens
> to others who cared.  

Yes, as one of the several victims, I can agree.  When was the last time
that Dan Bernstein posted?  I know: April 6th, 2006. Almost one year
ago.  Do you suppose Dan doesn't care anymore?  Or might it be because
of abuse?  

> the majority is still standing by, ready to tyrannize. 

That may be.  I suspect that a certain majority has been discredited or
at least lost the cult status and deference they once enjoyed.  Further
bad news awaits a certain group.

> IETF is an open-door society, and unless one counts the DNS
> Directorate, there is no way to get anything done that anybody objects
> to.

Obviously, not so. The 'tyrannizing majority' just recently passed the
'not-open' secrecy-enabling NSID option, which benefits no one but root
server operators who don't want to be held accountable for misbehaving
anycast servers. [recall that NSID secrecy prevents non-root operators
from determining if they are talking to the same anycast instance over
several queries--this makes it difficult to test root anycast operations
over UDP. Fortunately, one can still do TCP testing directly.  
Unfortunately, one then cannot use open recursors to test from different
parts of the internet this way, so it may be hard to get to all the
Anycast clones.]

The blunt exercises of power tryannical majority are pretty recent.

		--Dean





--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Wed Apr 04 15:56:36 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZBar-0003TO-Ol; Wed, 04 Apr 2007 15:56:34 -0400
Received: from psg.com ([147.28.0.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HZBaF-0002dg-Kp; Wed, 04 Apr 2007 15:56:32 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HZBUd-00013Q-3L
	for namedroppers-data@psg.com; Wed, 04 Apr 2007 19:50:07 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO,MIME_BOUND_NEXTPART,NO_REAL_NAME autolearn=no 
	version=3.1.7
Received: from [156.154.16.158] (helo=ns0.neustar.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ietf@ietf.org>)
	id 1HZBUZ-00011s-5i
	for namedroppers@ops.ietf.org; Wed, 04 Apr 2007 19:50:05 +0000
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns0.neustar.com (Postfix) with ESMTP id 6CA0432A21;
	Wed,  4 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HZBUY-0001gZ-9c; Wed, 04 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-trustupdate-timers-06.txt 
Message-Id: <E1HZBUY-0001gZ-9c@stiedprstage1.ietf.org>
Date: Wed, 04 Apr 2007 15:50:02 -0400
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the DNS Extensions Working Group of the IETF.

	Title		: Automated Updates of DNSSEC Trust Anchors
	Author(s)	: M. StJohns
	Filename	: draft-ietf-dnsext-trustupdate-timers-06.txt
	Pages		: 13
	Date		: 2007-4-4
	
This document describes a means for automated, authenticated and
   authorized updating of DNSSEC "trust anchors".  The method provides
   protection against N-1 key compromises of N keys in the trust point
   key set.  Based on the trust established by the presence of a current
   anchor, other anchors may be added at the same place in the
   hierarchy, and, ultimately, supplant the existing anchor(s).

   This mechanism will require changes to resolver management behavior
   (but not resolver resolution behavior), and the addition of a single
   flag bit to the DNSKEY record.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-trustupdate-timers-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-dnsext-trustupdate-timers-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dnsext-trustupdate-timers-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-4-4133733.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-trustupdate-timers-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-trustupdate-timers-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-4-4133733.I-D@ietf.org>

--OtherAccess--

--NextPart--


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Sat Apr 07 20:32:55 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaLKx-0000Vn-8E; Sat, 07 Apr 2007 20:32:55 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HaLKv-0001wK-Tl; Sat, 07 Apr 2007 20:32:55 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HaLFk-000NWQ-Du
	for namedroppers-data@psg.com; Sun, 08 Apr 2007 00:27:32 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO 
	autolearn=ham version=3.1.7
Received: from [156.154.24.139] (helo=ns4.neustar.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ietf@ietf.org>)
	id 1HaLFi-000NW3-AT
	for namedroppers@ops.ietf.org; Sun, 08 Apr 2007 00:27:31 +0000
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns4.neustar.com (Postfix) with ESMTP id 620472AC97;
	Sun,  8 Apr 2007 00:27:27 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HaLFf-0007Sl-5c; Sat, 07 Apr 2007 20:27:27 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>,
	dnsext mailing list <namedroppers@ops.ietf.org>,
	dnsext chair <dnsext-chairs@tools.ietf.org>
Subject: Document Action: 'DNSSEC Opt-In' to Experimental RFC 
Message-Id: <E1HaLFf-0007Sl-5c@stiedprstage1.ietf.org>
Date: Sat, 07 Apr 2007 20:27:27 -0400
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955

The IESG has approved the following document:

- 'DNSSEC Opt-In '
   <draft-ietf-dnsext-dnssec-opt-in-09.txt> as an Experimental RFC

This document is the product of the DNS Extensions Working Group. 

The IESG contact persons are Mark Townsley and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnssec-opt-in-09.txt

Technical Summary

opt-in is a method to disable the authenticated denial of existence
for a range of domain names in a zone. It has been developed to
generate a sparse set of NSEC RRs in a zone that contains mostly
delegations i.e. to opt-in the secure delegations. The span of
delegations for which authenticated denial is not available is still
indicated using an NSEC resource record.  'NSEC-bit' in the type
bitmap of the NSEC RDATA is used to signal the different semantic of
the opt-in type NSEC RR.

opt-in is a methodology that is backwards incompatible with DNSSEC; in
order to perform a trial the methodology described in
draft-ietf-dnsext-dnssec-experiments is applied.

   Working Group Summary

A couple of years ago this document had thourough technical review
around 2002. This version of the document has been slightly updated
to reflect changes to DNSSEC since 2002 and to turn it into an experiment
of the form described in draft-ietf-dnsext-dnssec-experiments.

During the development of the OPT-IN spec before and in 2002 there has
been in depth review and feedback by several core members of the working
group. At that time the consensus was that the document was
technologically solid but there was no consent the mechanism.

This time around the views of many folk have changed and they do not have
any problems with the OPT-IN technology going forward as an experiment.
The same functionality is introduced work currently in DNSEXT NSEC3.

Document Quality

The document has been reviewed by

Scott Rose 
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00316.html)

Mark Kosters
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00309.html,
he is one of the initial editors)

Rodney Joffe
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00335.html)

and dnsext chair Olaf Kolkman.

There has been some discussion after we advanced the document in which it
became clear that Ed Lewis also reviewed the document and supported
experimental status.

(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00902.html)


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Sat Apr 07 20:33:27 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaLLT-00014k-9A; Sat, 07 Apr 2007 20:33:27 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HaLLR-00022i-UM; Sat, 07 Apr 2007 20:33:27 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HaLET-000NSC-Th
	for namedroppers-data@psg.com; Sun, 08 Apr 2007 00:26:13 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO 
	autolearn=ham version=3.1.7
Received: from [156.154.16.138] (helo=ns1.neustar.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ietf@ietf.org>)
	id 1HaLER-000NRw-Ph
	for namedroppers@ops.ietf.org; Sun, 08 Apr 2007 00:26:12 +0000
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id DF29926F14;
	Sun,  8 Apr 2007 00:26:08 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HaLEO-0007QJ-QN; Sat, 07 Apr 2007 20:26:08 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>,
	dnsext mailing list <namedroppers@ops.ietf.org>,
	dnsext chair <dnsext-chairs@tools.ietf.org>
Subject: Protocol Action: 'DNSSEC Experiments' to Proposed 
         Standard 
Message-Id: <E1HaLEO-0007QJ-QN@stiedprstage1.ietf.org>
Date: Sat, 07 Apr 2007 20:26:08 -0400
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

The IESG has approved the following document:

- 'DNSSEC Experiments '
   <draft-ietf-dnsext-dnssec-experiments-04.txt> as a Proposed Standard

This document is the product of the DNS Extensions Working Group. 

The IESG contact persons are Mark Townsley and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnssec-experiments-04.txt

   Technical Summary

This document describes how algorithm identifiers can be used to
perform experiments within a DNSSECbis environment without that the
published data is marked as "bogus" by validating resolvers that do
not partake in the experiments.

The document explains why this methodology works and describes how
experiments are to be defined.

Besides, it suggests that algorithm identifiers can be used to
introduce non-backward compatible DNSSEC features into the
protocol.

The technology relies on the fact that DNSSECbis validators should
treat RRSets that are signed  (exclusively) with key-algorithms that
are not implemented by the validator, should treat the RRset as
not being signed at al.

The first application of this methodology will be an experiment with
"opt-in" [draft-ietf-dnsext-dnssec-opt-in]. It is possible that the
methodology will be used for the introduction of current DNSSEC
extensions currently under development in DNSEXT, the NSEC3 work.


   Working Group Summary

There is a solid consensus behind this working group document.
It has had a few review cycles and it is seen as relevant

   Document Quality

This document has been reviewed (among others) by these key members,
most of them recognized  DNS and or DNSSEC specialist.

Sam Weiler

(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00576.html)

Ed Lewis
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00440.html)

Andrew Sullivan
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00330.html)

Mark Kosters
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00309.html)

Thierry Moreau
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00305.html)

Scott Rose
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00316.html)

RodneyJoffe
(http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00335.html)

Thomas Nartan (thread starting at:
http://ops.ietf.org/lists/namedroppers/namedroppers.2006/msg00308.html).


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 09 10:29:17 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Haurt-0008PI-3s; Mon, 09 Apr 2007 10:29:17 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Haurr-0000uf-N2; Mon, 09 Apr 2007 10:29:17 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1Haukg-000C8g-Of
	for namedroppers-data@psg.com; Mon, 09 Apr 2007 14:21:50 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <Ed.Lewis@neustar.biz>)
	id 1HaukV-000C86-QL
	for namedroppers@ops.ietf.org; Mon, 09 Apr 2007 14:21:45 +0000
Received: from [192.168.1.102] (hlid.ogud.com [66.92.146.160])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l39EIcwO073451;
	Mon, 9 Apr 2007 10:18:38 -0400 (EDT)
	(envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06230903c23ffb6270b9@[192.168.1.102]>
Date: Mon, 9 Apr 2007 10:19:17 -0400
To: namedroppers@ops.ietf.org
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: how ironic
Cc: ed.lewis@neustar.biz
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370


'DNSSEC Opt-In'      as Experimental
'DNSSEC Experiments' as Proposed Standard

Just the juxtaposition of document names and categories.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Sarcasm doesn't scale.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 13 12:29:53 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcOen-0006NC-Jz; Fri, 13 Apr 2007 12:29:53 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HcOem-0003CF-2u; Fri, 13 Apr 2007 12:29:53 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HcOXR-000Dy7-P0
	for namedroppers-data@psg.com; Fri, 13 Apr 2007 16:22:17 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO,HEADER_SPAM autolearn=no version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <namedroppers@mail.ogud.com>)
	id 1HcOXN-000Dxg-Ly
	for namedroppers@ops.ietf.org; Fri, 13 Apr 2007 16:22:16 +0000
Received: from mail.ogud.com (localhost [127.0.0.1])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l3DGIgU4015819
	for <namedroppers@ops.ietf.org>; Fri, 13 Apr 2007 12:18:42 -0400 (EDT)
	(envelope-from namedroppers@mail.ogud.com)
Received: (from namedroppers@localhost)
	by mail.ogud.com (8.13.1/8.13.1/Submit) id l3DGIgvV015818
	for namedroppers@ops.ietf.org; Fri, 13 Apr 2007 12:18:42 -0400 (EDT)
	(envelope-from namedroppers)
Received: from [217.13.230.178] (helo=yxa.extundo.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <simon@josefsson.org>)
	id 1HYgLt-000Nws-MU
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 10:35:03 +0000
Received: from mocca.josefsson.org (yxa.extundo.com [217.13.230.178])
	(authenticated bits=0)
	by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l33AYYWE007213
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 3 Apr 2007 12:34:35 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Jim Reid <jim@rfc1035.com>
Cc: Edward Lewis <Ed.Lewis@neustar.biz>, namedroppers@ops.ietf.org
Subject: Re: DNSEXT (premature?) obituary notice
References: <a0623090ec236c1be9df4@[192.168.1.102]>
	<46052853-565A-4D19-BAD1-207902C1FAD9@rfc1035.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:070403:jim@rfc1035.com::n+xmNxxqhW1A83Zu:lYP
X-Hashcash: 1:22:070403:namedroppers@ops.ietf.org::O0Xdj3vUJiERs1Uc:8izN
X-Hashcash: 1:22:070403:ed.lewis@neustar.biz::a4VIUgOaBlkjtMyx:MP7W
Date: Tue, 03 Apr 2007 12:34:34 +0200
In-Reply-To: <46052853-565A-4D19-BAD1-207902C1FAD9@rfc1035.com> (Jim Reid's
	message of "Tue\, 3 Apr 2007 11\:07\:35 +0100")
Message-ID: <87tzvxrbk5.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

[ Moderators note: Post was moderated, either because it was posted by
   a non-subscriber, or because it was over 20K.  
   With the massive amount of spam, it is easy to miss and therefore 
   delete relevant posts by non-subscribers. 
   Please fix your subscription addresses. ]

Jim Reid <jim@rfc1035.com> writes:

>> What I also read from this lingering list of wants and needs is that
>> there isn't a lot of real desire to finish off the work.
>
> To be fair, I think this WG has scared away anyone who had ideas that
> were not DNSSEC related. It might be necessary to do outreach beyond
> the WG to re-engage with these guys.

I agree.  I also believe that any further security-related work (e.g.,
DNSSEC) should be done in the Security Area, to get more appropriate
review.  If we'd done that sooner, I believe NO would not have been
killed and we'd avoided the multi-year wait for a NXT-replacement.

I don't believe WGs should live forever, and DNSEXT is one of the
longest living WGs I know.  If it is not clear that we have important
new DNS extensions to adopt, then that is a good indication that the
WG should be closed.

/Simon


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 13 12:31:48 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcOgc-0007HL-2K; Fri, 13 Apr 2007 12:31:48 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HcOgZ-0003kS-Gt; Fri, 13 Apr 2007 12:31:46 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HcOXG-000Dwx-LI
	for namedroppers-data@psg.com; Fri, 13 Apr 2007 16:22:06 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00,HEADER_SPAM 
	autolearn=no version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <namedroppers@mail.ogud.com>)
	id 1HcOXB-000DwU-DH
	for namedroppers@ops.ietf.org; Fri, 13 Apr 2007 16:22:04 +0000
Received: from mail.ogud.com (localhost [127.0.0.1])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l3DGIUQU015813
	for <namedroppers@ops.ietf.org>; Fri, 13 Apr 2007 12:18:30 -0400 (EDT)
	(envelope-from namedroppers@mail.ogud.com)
Received: (from namedroppers@localhost)
	by mail.ogud.com (8.13.1/8.13.1/Submit) id l3DGIUrF015812
	for namedroppers@ops.ietf.org; Fri, 13 Apr 2007 12:18:30 -0400 (EDT)
	(envelope-from namedroppers)
Received: from [80.91.229.2] (helo=ciao.gmane.org)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ietf-namedroppers@m.gmane.org>)
	id 1HYWD4-00032X-CR
	for namedroppers@ops.ietf.org; Mon, 02 Apr 2007 23:45:16 +0000
Received: from root by ciao.gmane.org with local (Exim 4.43)
	id 1HYWCs-0005XB-09
	for namedroppers@ops.ietf.org; Tue, 03 Apr 2007 01:45:02 +0200
Received: from desk.marajade.sandelman.ca ([205.150.200.247])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <namedroppers@ops.ietf.org>; Tue, 03 Apr 2007 01:45:01 +0200
Received: from mcr by desk.marajade.sandelman.ca with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <namedroppers@ops.ietf.org>; Tue, 03 Apr 2007 01:45:01 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: namedroppers@ops.ietf.org
From: Michael Richardson <mcr@sandelman.ca>
Subject:  Re: DNSEXT future
Date:  Mon, 02 Apr 2007 19:22:30 -0400
Lines: 23
Message-ID: <eus37n$bbn$2@sea.gmane.org>
References:  <85057.1174958037@sa.vix.com> <OFE666686F.6E206EF4-ON802572AB.00221085-C12572AB.0022EFA8@nominet.org.uk>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: desk.marajade.sandelman.ca
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.9) Gecko/20061219 Iceape/1.0.7 (Debian-1.0.7-3)
In-Reply-To: <OFE666686F.6E206EF4-ON802572AB.00221085-C12572AB.0022EFA8@nominet.org.uk>
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

[ Moderators note: Post was moderated, either because it was posted by
   a non-subscriber, or because it was over 20K.  
   With the massive amount of spam, it is easy to miss and therefore 
   delete relevant posts by non-subscribers. 
   Please fix your subscription addresses. ]

Roy Arends wrote:
> Paul Vixie wrote on 03/27/2007 03:13:57 AM:
> 
>> i'd like to see roy's version of DLV standardized before we quit, that's 
> all.
> 
> Me too. (well, ofcourse I would, wouldn't I). Jakob and I are writing this 
> up in a draft that will soon hit the list.
> 
> As for DNSEXT, I don't think we're done at all. There is indeed DLV, and 
> there is the last mile. There is also the transparency and the end-to-end

I would rather see dnsext hibernate, and spawn off a new group with
a limited charter (and clear end-of-life) if we still need to meet
for this.

I am also not opposed to seeing dnsext close, but I see the advantage
of hibernation. (cf. sipping vs sip)

> paradigm I'd like to see written up, explicitly for the DNS. There is 
> key-management, rollover, and once 2929-bis is done, I hope to see more 
> record types hit the iana registry. Some of this can be wrapped up in 
> DNSOP, but not all of it.



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 13 14:07:24 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcQBA-0002Ym-R8; Fri, 13 Apr 2007 14:07:24 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HcQB7-0002rH-D2; Fri, 13 Apr 2007 14:07:24 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HcQ6X-000L4Y-GD
	for namedroppers-data@psg.com; Fri, 13 Apr 2007 18:02:37 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <Ed.Lewis@neustar.biz>)
	id 1HcQ6T-000L4F-Vp
	for namedroppers@ops.ietf.org; Fri, 13 Apr 2007 18:02:35 +0000
Received: from [10.31.33.50] (hlid.ogud.com [66.92.146.160])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l3DHwo31016733;
	Fri, 13 Apr 2007 13:58:51 -0400 (EDT)
	(envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06230909c24573f6f685@[10.31.33.50]>
In-Reply-To: <87tzvxrbk5.fsf@mocca.josefsson.org>
References: <a0623090ec236c1be9df4@[192.168.1.102]>
 <46052853-565A-4D19-BAD1-207902C1FAD9@rfc1035.com>
 <87tzvxrbk5.fsf@mocca.josefsson.org>
Date: Fri, 13 Apr 2007 14:01:56 -0400
To: Simon Josefsson <simon@josefsson.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: DNSEXT (premature?) obituary notice
Cc: Jim Reid <jim@rfc1035.com>, Edward Lewis <Ed.Lewis@neustar.biz>,
        namedroppers@ops.ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

At 12:34 +0200 4/3/07, Simon Josefsson wrote:

>I agree.  I also believe that any further security-related work (e.g.,
>DNSSEC) should be done in the Security Area, to get more appropriate
>review.  If we'd done that sooner, I believe NO would not have been
>killed and we'd avoided the multi-year wait for a NXT-replacement.

Just to fill in the history...the DNSSEC WG existed in the Security 
area from about 1994 (before my time) until 1999 when it was merged 
into the current DNSEXT WG.  Prior to the conclusion of DNSSEC WG we 
did talk in hallways about a hashed-based means of authenticated 
denial.

Adding some debatable perspective to my comments - the reason for the 
move of DNSSEC work from the Security Area to the Internet Area was a 
realization that the early versions of DNSSEC lacked a true 
understanding of the DNS protocol and were much more influenced by 
considerations for cryptography and asymmetric keys.  Off-line keys 
were proposed to keep the private key private.  The parent-child 
exchange wasn't operationally feasible.  The whole notion of "key 
strength" was unworkable in practice.

I don't know if this is a coincidence, but in 1998 or 1999, after a 
few years of work on RFC 2065, DNSSEC make its first appearance in 
BIND.  In May of 1999 there was the first field test/workshop in 
Knivsta, SE.  In July 1999 it was pretty much decided to end DNSSEC 
WG and merge it with DNSIND WG to make DNSEXT WG.  By 2002 the DS 
record was born and implemented and tested in November.  (DNSOP BoF 
was in March 1999 and that's where I added a laundry list of DNS 
operations work items.)

I think that the move from the Security Area was a good one.  I've 
since learned that it is better to know the underlying protocol than 
security theory when trying to "slap on" security.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Sarcasm doesn't scale.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Wed Apr 18 13:08:00 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeDdO-0004Tn-H4; Wed, 18 Apr 2007 13:08:00 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeDdN-0005Pf-4I; Wed, 18 Apr 2007 13:07:58 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HeDWS-000LgC-De
	for namedroppers-data@psg.com; Wed, 18 Apr 2007 17:00:48 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS 
	autolearn=ham version=3.1.7
Received: from [204.152.187.1] (helo=sa.vix.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <vixie@vix.com>)
	id 1HeDWO-000Lfq-Gl
	for namedroppers@ops.ietf.org; Wed, 18 Apr 2007 17:00:45 +0000
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id C04A011425
	for <namedroppers@ops.ietf.org>; Wed, 18 Apr 2007 17:00:43 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: namedroppers@ops.ietf.org
Subject: has anybody looked into the verizon/vonage dns patent fight?
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 18 Apr 2007 17:00:43 +0000
Message-ID: <80988.1176915643@sa.vix.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

somebody called my attn to <http://www.google.com/patents?vid=USPAT6104711>.

i think t p brisco and roland schemers and TGV did most of this way long ago
before this patent was filed, except for the phone number parts.  (anybody?)

<rant about patent system corruption cathartically typed in and then wisely
paragraph-wiped, since it's off-topic here.  plz do the same if you must.>

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Wed Apr 18 20:03:39 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeK7f-000203-N8; Wed, 18 Apr 2007 20:03:39 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HeK7b-0001Pt-Dl; Wed, 18 Apr 2007 20:03:39 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HeK27-000PZd-Rm
	for namedroppers-data@psg.com; Wed, 18 Apr 2007 23:57:55 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO autolearn=ham version=3.1.7
Received: from [131.112.32.132] (helo=necom830.hpcl.titech.ac.jp)
	by psg.com with smtp (Exim 4.63 (FreeBSD))
	(envelope-from <mohta@necom830.hpcl.titech.ac.jp>)
	id 1HeK1y-000PZG-TG
	for namedroppers@ops.ietf.org; Wed, 18 Apr 2007 23:57:51 +0000
Received: (qmail 30917 invoked from network); 19 Apr 2007 00:10:49 -0000
Received: from softbank219001188028.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.1.188.28)
  by necom830.hpcl.titech.ac.jp with SMTP; 19 Apr 2007 00:10:49 -0000
Message-ID: <4626B077.8050406@necom830.hpcl.titech.ac.jp>
Date: Thu, 19 Apr 2007 08:57:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
CC:  namedroppers@ops.ietf.org
Subject: Re: has anybody looked into the verizon/vonage dns patent fight?
References: <80988.1176915643@sa.vix.com>
In-Reply-To: <80988.1176915643@sa.vix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 1.1 (+)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

Paul Vixie wrote:

> somebody called my attn to <http://www.google.com/patents?vid=USPAT6104711>.
> 
> i think t p brisco and roland schemers and TGV did most of this way long ago
> before this patent was filed, except for the phone number parts.  (anybody?)

RFC1530, published in 1993, gives mapping between phone numbers
and domain names.

						Masataka Ohta


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 20 09:26:33 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Het8D-0001Eu-1N; Fri, 20 Apr 2007 09:26:33 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Het8B-0000Wb-Jy; Fri, 20 Apr 2007 09:26:33 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1Het18-000Kog-RH
	for namedroppers-data@psg.com; Fri, 20 Apr 2007 13:19:14 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO 
	autolearn=ham version=3.1.7
Received: from [68.142.225.206] (helo=smtp108.rog.mail.re2.yahoo.com)
	by psg.com with smtp (Exim 4.63 (FreeBSD))
	(envelope-from <thierry.moreau@connotech.com>)
	id 1Het15-000KoK-Rk
	for namedroppers@ops.ietf.org; Fri, 20 Apr 2007 13:19:13 +0000
Received: (qmail 53670 invoked from network); 20 Apr 2007 13:19:10 -0000
Received: from unknown (HELO connotech.com) (t2i6@rogers.com@209.148.165.15 with plain)
  by smtp108.rog.mail.re2.yahoo.com with SMTP; 20 Apr 2007 13:19:10 -0000
X-YMail-OSG: 0alz2F0VM1k0jCeyHNUDg9HsqZHqfId8ZO.5S3eriOWGW7unyU2.YdTHFDb5_erqAQ--
Message-ID: <4628BF57.6070309@connotech.com>
Date: Fri, 20 Apr 2007 09:25:43 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Namedroppers <namedroppers@ops.ietf.org>
Subject: Root deployment facilitation for DNSSEC
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

New individual submission draft:

DNSSEC Validation Root Priming Through SLP (DNSSEC-ROOTP)
Category: experimental

Abstract:

By assigning the SLP (Service Location Protocol, [RFC2608]) UA (User 
Agent) role to a DNS resolver, the present document opens the door to 
selective deployment of DNS root nameservice substitution within an 
administrative domain. This SLP scheme directly addresses the DNS 
resolver configuration scaling issue. It is envisioned that various DNS 
root nameservice substitution undertakings target their respective user 
base, and no single one will be exposed alone to the global scaling 
problem. Usage is limited to DNSSEC-enabled root nameservice. Moreover, 
from the SLP security features, the proposed scheme expands the set of 
DNS root trust anchor key rollover options.

The I-D is temporarily at: 
http://www.connotech.com/draft-moreau-srvloc-dnssec-priming-00.txt

Regards,

-- 

- Thierry Moreau

CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Montreal, Qc
Canada   H2M 2A1

Tel.: (514)385-5691
Fax:  (514)385-5900

web site: http://www.connotech.com
e-mail: thierry.moreau@connotech.com



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Sat Apr 21 04:53:38 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfBLe-0003qT-Gg; Sat, 21 Apr 2007 04:53:38 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HfBLd-0001tb-3D; Sat, 21 Apr 2007 04:53:38 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HfBGX-0008fd-O9
	for namedroppers-data@psg.com; Sat, 21 Apr 2007 08:48:21 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [195.241.79.176] (helo=smtp-out1.tiscali.nl)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <wouter@nlnetlabs.nl>)
	id 1HfBGU-0008fN-Hc
	for namedroppers@ops.ietf.org; Sat, 21 Apr 2007 08:48:20 +0000
Received: from [82.170.145.155] (helo=[192.168.254.1])
	by smtp-out1.tiscali.nl with esmtp (Tiscali http://www.tiscali.nl)
	id 1HfBGS-0000uN-Fj
	for <namedroppers@ops.ietf.org>; Sat, 21 Apr 2007 10:48:16 +0200
Message-ID: <4629CFC5.6000207@nlnetlabs.nl>
Date: Sat, 21 Apr 2007 10:48:05 +0200
From: Wouter Wijngaards <wouter@nlnetlabs.nl>
User-Agent: Thunderbird 1.5.0.10 (X11/20070301)
MIME-Version: 1.0
To: Namedroppers <namedroppers@ops.ietf.org>
Subject: Draft Key Rollover History
X-Enigmail-Version: 0.94.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have recently been thinking about key-priming for machines that have
been off-line long enough for their trust-anchors to go stale. I've
documented an idea in draft-wijngaards-dnsext-trust-history-00 (
http://www.ietf.org/internet-drafts/draft-wijngaards-dnsext-trust-history-00.txt
).

The properties of this solution are:
* The priming keys do not go stale, 10 year old software could install
and re-prime successfully.
* priming keys can be rolled themselves, reducing their exposure.
* priming keys can be revoked if compromised.
* withstand N-1 key compromises.

The zone owner is in control of choices
* Can be lots of keys, packets stay small.
* Number and size of keys can be chosen by zone operator.
  Say using 13 keys for the root zone.
* Number and size of keys can be changed by zone operator with a rollover.
* history is stored at a name of operators choice.
* (ancient) history can be served by a subdomain of the zone, so can be
offloaded to another authoritative server.
* all history data can be treated as unknown RR data types by caches.
* operators can move historical data around.
* operators can discard old private key data and still do all of the
above.

I would appreciate your review and comments.

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGKc/FkDLqNwOhpPgRAg6/AKCzm5ShUmoxe/M7yPsJpMD76h6uvgCdETJC
kn17wTtEVbp1yyORYYVZIjo=
=Prvh
-----END PGP SIGNATURE-----

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Mon Apr 23 13:12:40 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg25g-0008GO-OF; Mon, 23 Apr 2007 13:12:40 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hg25f-0004Iu-8A; Mon, 23 Apr 2007 13:12:40 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1Hg1vr-0001GC-6a
	for namedroppers-data@psg.com; Mon, 23 Apr 2007 17:02:31 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,
	SPF_PASS autolearn=ham version=3.1.7
Received: from [157.185.61.2] (helo=M4.sparta.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <Robert.Story@sparta.com>)
	id 1Hg1vn-0001Fe-Js
	for namedroppers@ops.ietf.org; Mon, 23 Apr 2007 17:02:29 +0000
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21])
	by M4.sparta.com (8.13.5/8.13.5) with ESMTP id l3NH2IFL017926;
	Mon, 23 Apr 2007 12:02:18 -0500
Received: from garak.ads.sparta.com (garak.sparta.com [157.185.63.81])
	by Beta5.sparta.com (8.12.11/8.13.1) with ESMTP id l3NH2INC030804;
	Mon, 23 Apr 2007 12:02:18 -0500
Received: from mailbin2.ads.sparta.com ([157.185.85.6]) by garak.ads.sparta.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 23 Apr 2007 12:02:18 -0500
Received: from spx.vb.futz.org ([216.27.162.138]) by mailbin2.ads.sparta.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 23 Apr 2007 13:03:35 -0400
Date: Mon, 23 Apr 2007 13:02:04 -0400
From: Robert Story <rstory@sparta.com>
To: Wouter Wijngaards <wouter@nlnetlabs.nl>
Cc: Namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Draft Key Rollover History
Message-ID: <20070423130204.3ec8c5e5@spx.vb.futz.org>
In-Reply-To: <4629CFC5.6000207@nlnetlabs.nl>
References: <4629CFC5.6000207@nlnetlabs.nl>
Organization: SPARTA
X-Mailer: Claws Mail 2.8.1 (GTK+ 2.8.20; powerpc-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_tcjSdvtO=tWqonXS.uX._S2";
 protocol="application/pgp-signature"; micalg=PGP-SHA1
X-OriginalArrivalTime: 23 Apr 2007 17:03:35.0734 (UTC) FILETIME=[54954D60:01C785C9]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (M4.sparta.com [157.185.61.2]); Mon, 23 Apr 2007 12:02:19 -0500 (CDT)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

--Sig_tcjSdvtO=tWqonXS.uX._S2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sat, 21 Apr 2007 10:48:05 +0200 Wouter wrote:
WW> I have recently been thinking about key-priming for machines that have
WW> been off-line long enough for their trust-anchors to go stale. [...]

WW> * operators can discard old private key data and still do all of the
WW> above.

I've only skimmed the draft, but my first though when I read this was:
what happens when an old key (which was never revoked) becomes
compromised? The scenarios in section 6 of timers is 'informative', so
a zone could roll keys without revoking the the keys as described in
6.3. So, does this present an attack on the stale update mechanism you
describe? If so, then operators might need old private keys to go back
and revoke the compromised key.

Another thought I had was with regards to delegating the historical
data to subzone. Why restrict it to a subzone? If you let it be any
name, operators could outsource maintenance of the historical data.

--=20
Robert Story
SPARTA

--Sig_tcjSdvtO=tWqonXS.uX._S2
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFGLOaM7/fVLLY1mngRAvnFAJ9/W0Whruj1hM/splFHGBKYOvDxogCfZk+Z
NOP1NtxL0ADYM+FFnc/zSAM=
=XBXQ
-----END PGP SIGNATURE-----

--Sig_tcjSdvtO=tWqonXS.uX._S2--

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Tue Apr 24 03:27:59 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgFRP-0006b9-Du; Tue, 24 Apr 2007 03:27:59 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HgFRO-0002iD-2d; Tue, 24 Apr 2007 03:27:59 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HgFL4-000Pf0-Cj
	for namedroppers-data@psg.com; Tue, 24 Apr 2007 07:21:26 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [213.154.224.1] (helo=open.nlnetlabs.nl)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <wouter@nlnetlabs.nl>)
	id 1HgFL0-000PeB-Oh
	for namedroppers@ops.ietf.org; Tue, 24 Apr 2007 07:21:24 +0000
Received: from [IPv6:2001:7b8:206:1:240:f4ff:fe37:8810] (diva.nlnetlabs.nl [IPv6:2001:7b8:206:1:240:f4ff:fe37:8810])
	by open.nlnetlabs.nl (8.13.8/8.13.8) with ESMTP id l3O7LHqG048251;
	Tue, 24 Apr 2007 09:21:18 +0200 (CEST)
	(envelope-from wouter@nlnetlabs.nl)
Message-ID: <462DAFED.1030006@nlnetlabs.nl>
Date: Tue, 24 Apr 2007 09:21:17 +0200
From: Wouter Wijngaards <wouter@NLnetLabs.nl>
User-Agent: Thunderbird 1.5.0.10 (X11/20070301)
MIME-Version: 1.0
To: Robert Story <rstory@sparta.com>
CC: Namedroppers <namedroppers@ops.ietf.org>
Subject: Re: Draft Key Rollover History
References: <4629CFC5.6000207@nlnetlabs.nl> <20070423130204.3ec8c5e5@spx.vb.futz.org>
In-Reply-To: <20070423130204.3ec8c5e5@spx.vb.futz.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Story wrote:
> I've only skimmed the draft, but my first though when I read this was:
> what happens when an old key (which was never revoked) becomes
> compromised? The scenarios in section 6 of timers is 'informative', so
> a zone could roll keys without revoking the the keys as described in
> 6.3. So, does this present an attack on the stale update mechanism you
> describe? If so, then operators might need old private keys to go back
> and revoke the compromised key.

The operator can store a pre-self-signed key revocation (in a safe
place, it can only be used for denial of service really) before
discarding private key data. When the key becomes compromised, the zone
operator can insert the key revocation by rolling over the current keys.
This signs the key revocation with the current keys, and stores the key
revocation at the most recent history moment. Thus, old private keys are
not needed to revoke an old key.

> Another thought I had was with regards to delegating the historical
> data to subzone. Why restrict it to a subzone? If you let it be any
> name, operators could outsource maintenance of the historical data.
> 
Well, the reason I restricted it to a subzone is because I wanted the
current DNSKEY of the zone to sign a DS to it. Although this can be
relaxed, I think, and any name be used, or maybe a DS to the outsourced
name added or something. The DS would give an attacker more trouble
spoofing. This protection is really only a hurdle for the case where the
attacker has compromised N keys.

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGLa/skDLqNwOhpPgRAntHAJ9IrVCiOwWLpCqTw+AHq4oalblyYwCgmVvF
NyPFnl6UtnH9B+6rfocnnmQ=
=kn+8
-----END PGP SIGNATURE-----

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Tue Apr 24 10:09:34 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgLi2-0006SZ-Fm; Tue, 24 Apr 2007 10:09:34 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HgLhw-0001oB-UY; Tue, 24 Apr 2007 10:09:34 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HgLac-0005cd-0r
	for namedroppers-data@psg.com; Tue, 24 Apr 2007 14:01:54 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [129.6.16.226] (helo=smtp.nist.gov)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <scottr@nist.gov>)
	id 1HgLaT-0005c9-Ob
	for namedroppers@ops.ietf.org; Tue, 24 Apr 2007 14:01:48 +0000
Received: from [129.6.140.98] (98-140.antd.nist.gov [129.6.140.98])
	by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id l3OE1KTr031519
	for <namedroppers@ops.ietf.org>; Tue, 24 Apr 2007 10:01:31 -0400
Message-ID: <462E0DB0.5060202@nist.gov>
Date: Tue, 24 Apr 2007 10:01:20 -0400
From: Scott Rose <scottr@nist.gov>
Organization: NIST
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: IETF DNSEXT WG <namedroppers@ops.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scottr@nist.gov
Subject: DNAME-update draft: revised server algorithm
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0

The new version (-02) of the DNAME-update draft will be posted shortly. 
  In the latest version, a revised version of the server algorithm in
RFC 2672 is found to reflect that the DNSSEC-OK bit also signals 
understanding of DNAME.

Below is the new algorithm

3.4.  Server algorithm

    Below the server algorithm, which appeared in RFC 2672 Section 4.1,
    is expanded to handle the DO bit.

    1.  Set or clear the value of recursion available in the response
        depending on whether the name server is willing to provide
        recursive service.  If recursive service is available and
        requested via the RD bit in the query, go to step 5, otherwise
        step 2.
    2.  Search the available zones for the zone which is the nearest
        ancestor to QNAME.  If such a zone is found, go to step 3,
        otherwise step 4.
    3.  Start matching down, label by label, in the zone.  The matching
        process can terminate several ways:
        A.  If the whole of QNAME is matched, we have found the node.

            If the data at the node is a CNAME, and QTYPE doesn't match
            CNAME, copy the CNAME RR into the answer section of the
            response, change QNAME to the canonical name in the CNAME RR,
            and go back to step 1.

            Otherwise, copy all RRs which match QTYPE into the answer
            section and go to step 6.




Rose & Wijngaards       Expires October 26, 2007                [Page 7]

Internet-Draft              DNAME Redirection                 April 2007


        B.  If a match would take us out of the authoritative data, we
            have a referral.  This happens when we encounter a node with
            NS RRs marking cuts along the bottom of a zone.

            Copy the NS RRs for the subzone into the authority section of
            the reply.  Put whatever addresses are available into the
            additional section, using glue RRs if the addresses are not
            available from authoritative data or the cache.  Go to step
            4.
        C.  If at some label, a match is impossible (i.e., the
            corresponding label does not exist), look to see whether the
            last label matched has a DNAME record.

            If a DNAME record exists at that point, copy that record into
            the answer section.  If substitution of its <target> for its
            <owner> in QNAME would overflow the legal size for a <domain-
            name>, set RCODE to YXDOMAIN [RFC2136] and exit; otherwise
            perform the substitution and continue.  The server SHOULD
            synthesize a CNAME record as described above and include it
            in the answer section.  The server MAY omit this CNAME
            synthesis if the query has the EDNS DNSSEC-OK bit set.  Go
            back to step 1.

            If there was no DNAME record, look to see if the "*" label
            exists.

            If the "*" label does not exist, check whether the name we
            are looking for is the original QNAME in the query or a name
            we have followed due to a CNAME or DNAME.  If the name is
            original, set an authoritative name error in the response and
            exit.  Otherwise just exit.

            If the "*" label does exist, match RRs at that node against
            QTYPE.  If any match, copy them into the answer section, but
            set the owner of the RR to be QNAME, and not the node with
            the "*" label.  Go to step 6.
    4.  Start matching down in the cache.  If QNAME is found in the
        cache, copy all RRs attached to it that match QTYPE into the
        answer section.  If QNAME is not found in the cache but a DNAME
        record is present at an ancestor of QNAME, copy that DNAME record
        into the answer section.  If there was no delegation from
        authoritative data, look for the best one from the cache, and put
        it in the authority section.  Go to step 6.
    5.  Use the local resolver or a copy of its algorithm to answer the
        query.  Store the results, including any intermediate CNAMEs and
        DNAMEs, in the answer section of the response.
    6.  Using local data only, attempt to add other RRs which may be
        useful to the additional section of the query.  Exit.

    Note that there will be at most one ancestor with a DNAME as
    described in step 4 unless some zone's data is in violation of the
    no-descendants limitation in section 3.  An implementation might take
    advantage of this limitation by stopping the search of step 3c or
    step 4 when a DNAME record is encountered.


<End section>

Please send technical comments to the list, wording comments can be sent 
directly to the authors (Wouter and myself).

Scott


-- 
----------------------------------------
Scott Rose            Computer Scientist
NIST
ph: +1 301-975-8439
scott.rose@nist.gov

http://www-x.antd.nist.gov/dnssec
http://www.dnssec-deployment.org/
-----------------------------------------

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Thu Apr 26 16:10:40 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhAIa-00052x-Cn; Thu, 26 Apr 2007 16:10:40 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HhAIY-0002Ch-SI; Thu, 26 Apr 2007 16:10:40 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HhACT-00091C-Ci
	for namedroppers-data@psg.com; Thu, 26 Apr 2007 20:04:21 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ogud@ogud.com>)
	id 1HhACP-00090k-MJ
	for namedroppers@ops.ietf.org; Thu, 26 Apr 2007 20:04:19 +0000
Received: from Puki.ogud.com (hlid.ogud.com [66.92.146.160])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l3QJwpfW032534;
	Thu, 26 Apr 2007 15:58:52 -0400 (EDT)
	(envelope-from ogud@ogud.com)
Message-Id: <200704261958.l3QJwpfW032534@ogud.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 26 Apr 2007 16:03:43 -0400
To: Scott Rose <scottr@nist.gov>, IETF DNSEXT WG <namedroppers@ops.ietf.org>
From: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: DNAME-update draft: revised server algorithm
In-Reply-To: <462E0DB0.5060202@nist.gov>
References: <462E0DB0.5060202@nist.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8

<no-hat>

I think this is fine.
For the discussion my preference is to change:
"The server MAY omit this CNAME
  synthesis if the query has the EDNS DNSSEC-OK bit set."

to:
"The server SHOULD omit this CNAME
synthesis if the query has the EDNS DNSSEC-OK bit set."

         Olafur



At 10:01 24/04/2007, Scott Rose wrote:
>The new version (-02) of the DNAME-update draft will be posted 
>shortly.  In the latest version, a revised version of the server algorithm in
>RFC 2672 is found to reflect that the DNSSEC-OK bit also signals 
>understanding of DNAME.
>
>Below is the new algorithm
>
>3.4.  Server algorithm
>
>    Below the server algorithm, which appeared in RFC 2672 Section 4.1,
>    is expanded to handle the DO bit.
>
>    1.  Set or clear the value of recursion available in the response
>        depending on whether the name server is willing to provide
>        recursive service.  If recursive service is available and
>        requested via the RD bit in the query, go to step 5, otherwise
>        step 2.
>    2.  Search the available zones for the zone which is the nearest
>        ancestor to QNAME.  If such a zone is found, go to step 3,
>        otherwise step 4.
>    3.  Start matching down, label by label, in the zone.  The matching
>        process can terminate several ways:
>        A.  If the whole of QNAME is matched, we have found the node.
>
>            If the data at the node is a CNAME, and QTYPE doesn't match
>            CNAME, copy the CNAME RR into the answer section of the
>            response, change QNAME to the canonical name in the CNAME RR,
>            and go back to step 1.
>
>            Otherwise, copy all RRs which match QTYPE into the answer
>            section and go to step 6.
>
>
>
>
>Rose & Wijngaards       Expires October 26, 2007                [Page 7]
>
>Internet-Draft              DNAME Redirection                 April 2007
>
>
>        B.  If a match would take us out of the authoritative data, we
>            have a referral.  This happens when we encounter a node with
>            NS RRs marking cuts along the bottom of a zone.
>
>            Copy the NS RRs for the subzone into the authority section of
>            the reply.  Put whatever addresses are available into the
>            additional section, using glue RRs if the addresses are not
>            available from authoritative data or the cache.  Go to step
>            4.
>        C.  If at some label, a match is impossible (i.e., the
>            corresponding label does not exist), look to see whether the
>            last label matched has a DNAME record.
>
>            If a DNAME record exists at that point, copy that record into
>            the answer section.  If substitution of its <target> for its
>            <owner> in QNAME would overflow the legal size for a <domain-
>            name>, set RCODE to YXDOMAIN [RFC2136] and exit; otherwise
>            perform the substitution and continue.  The server SHOULD
>            synthesize a CNAME record as described above and include it
>            in the answer section.  The server MAY omit this CNAME
>            synthesis if the query has the EDNS DNSSEC-OK bit set.  Go
>            back to step 1.
>
>            If there was no DNAME record, look to see if the "*" label
>            exists.
>
>            If the "*" label does not exist, check whether the name we
>            are looking for is the original QNAME in the query or a name
>            we have followed due to a CNAME or DNAME.  If the name is
>            original, set an authoritative name error in the response and
>            exit.  Otherwise just exit.
>
>            If the "*" label does exist, match RRs at that node against
>            QTYPE.  If any match, copy them into the answer section, but
>            set the owner of the RR to be QNAME, and not the node with
>            the "*" label.  Go to step 6.
>    4.  Start matching down in the cache.  If QNAME is found in the
>        cache, copy all RRs attached to it that match QTYPE into the
>        answer section.  If QNAME is not found in the cache but a DNAME
>        record is present at an ancestor of QNAME, copy that DNAME record
>        into the answer section.  If there was no delegation from
>        authoritative data, look for the best one from the cache, and put
>        it in the authority section.  Go to step 6.
>    5.  Use the local resolver or a copy of its algorithm to answer the
>        query.  Store the results, including any intermediate CNAMEs and
>        DNAMEs, in the answer section of the response.
>    6.  Using local data only, attempt to add other RRs which may be
>        useful to the additional section of the query.  Exit.
>
>    Note that there will be at most one ancestor with a DNAME as
>    described in step 4 unless some zone's data is in violation of the
>    no-descendants limitation in section 3.  An implementation might take
>    advantage of this limitation by stopping the search of step 3c or
>    step 4 when a DNAME record is encountered.
>
>
><End section>
>
>Please send technical comments to the list, wording comments can be 
>sent directly to the authors (Wouter and myself).
>
>Scott
>
>
>--
>----------------------------------------
>Scott Rose            Computer Scientist
>NIST
>ph: +1 301-975-8439
>scott.rose@nist.gov
>
>http://www-x.antd.nist.gov/dnssec
>http://www.dnssec-deployment.org/
>-----------------------------------------
>
>--
>to unsubscribe send a message to namedroppers-request@ops.ietf.org with
>the word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/namedroppers/>


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 27 15:55:32 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhWXU-0003HE-6A; Fri, 27 Apr 2007 15:55:32 -0400
Received: from psg.com ([147.28.0.62])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HhWXH-0003OE-Ds; Fri, 27 Apr 2007 15:55:32 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HhWSM-0001eA-SY
	for namedroppers-data@psg.com; Fri, 27 Apr 2007 19:50:14 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,
	FORGED_RCVD_HELO,MIME_BOUND_NEXTPART,NO_REAL_NAME autolearn=no 
	version=3.1.7
Received: from [156.154.16.158] (helo=ns0.neustar.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <ietf@ietf.org>)
	id 1HhWSB-0001c8-4g
	for namedroppers@ops.ietf.org; Fri, 27 Apr 2007 19:50:05 +0000
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns0.neustar.com (Postfix) with ESMTP id 5E703329DA;
	Fri, 27 Apr 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HhWSA-0002QK-7w; Fri, 27 Apr 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: namedroppers@ops.ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dnsext-rfc2672bis-dname-02.txt 
Message-Id: <E1HhWSA-0002QK-7w@stiedprstage1.ietf.org>
Date: Fri, 27 Apr 2007 15:50:02 -0400
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the DNS Extensions Working Group of the IETF.

	Title		: Update to DNAME Redirection in the DNS
	Author(s)	: S. Rose, W. Wijngaards
	Filename	: draft-ietf-dnsext-rfc2672bis-dname-02.txt
	Pages		: 15
	Date		: 2007-4-27
	
The DNAME record provides redirection for a sub-tree of the domain
   name tree in the DNS system.  That is, all names that end with a
   particular suffix are redirected to another part of the DNS.  This is
   an update to the original specification in RFC 2672.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-rfc2672bis-dname-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-dnsext-rfc2672bis-dname-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dnsext-rfc2672bis-dname-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-4-27111912.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dnsext-rfc2672bis-dname-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dnsext-rfc2672bis-dname-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-4-27111912.I-D@ietf.org>

--OtherAccess--

--NextPart--


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



From owner-namedroppers@ops.ietf.org Fri Apr 27 17:03:37 2007
Return-path: <owner-namedroppers@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhXbN-00020A-Lq; Fri, 27 Apr 2007 17:03:37 -0400
Received: from psg.com ([147.28.0.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HhXbM-00033t-BF; Fri, 27 Apr 2007 17:03:37 -0400
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD))
	(envelope-from <owner-namedroppers@ops.ietf.org>)
	id 1HhXWP-0006PC-IJ
	for namedroppers-data@psg.com; Fri, 27 Apr 2007 20:58:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.7
Received: from [66.92.146.160] (helo=ogud.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.63 (FreeBSD))
	(envelope-from <Ed.Lewis@neustar.biz>)
	id 1HhXWM-0006Om-CU
	for namedroppers@ops.ietf.org; Fri, 27 Apr 2007 20:58:28 +0000
Received: from [10.31.32.239] (hlid.ogud.com [66.92.146.160])
	by ogud.com (8.13.1/8.13.1) with ESMTP id l3RKquRW045895;
	Fri, 27 Apr 2007 16:52:58 -0400 (EDT)
	(envelope-from Ed.Lewis@neustar.biz)
Mime-Version: 1.0
Message-Id: <a06230904c25813a361e9@[10.31.32.239]>
In-Reply-To: <462E0DB0.5060202@nist.gov>
References: <462E0DB0.5060202@nist.gov>
Date: Fri, 27 Apr 2007 16:58:23 -0400
To: Scott Rose <scottr@nist.gov>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: DNAME-update draft: revised server algorithm
Cc: IETF DNSEXT WG <namedroppers@ops.ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.61 on 66.92.146.160
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-id: DNSEXT discussion <namedroppers.ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

At 10:01 -0400 4/24/07, Scott Rose wrote:

>        C.  If at some label, a match is impossible (i.e., the
>            corresponding label does not exist), look to see whether the
>            last label matched has a DNAME record.
>
>            If a DNAME record exists at that point, copy that record into
>            the answer section.  If substitution of its <target> for its
>            <owner> in QNAME would overflow the legal size for a <domain-
>            name>, set RCODE to YXDOMAIN [RFC2136] and exit; otherwise
>            perform the substitution and continue.  The server SHOULD
>            synthesize a CNAME record as described above and include it
>            in the answer section.  The server MAY omit this CNAME
>            synthesis if the query has the EDNS DNSSEC-OK bit set.  Go
>            back to step 1.
>
>            If there was no DNAME record, look to see if the "*" label
>            exists.
>
>            If the "*" label does not exist, check whether the name we
>            are looking for is the original QNAME in the query or a name
>            we have followed due to a CNAME or DNAME.  If the name is
>            original, set an authoritative name error in the response and
>            exit.  Otherwise just exit.
>
>            If the "*" label does exist, match RRs at that node against
>            QTYPE.  If any match, copy them into the answer section, but
>            set the owner of the RR to be QNAME, and not the node with
>            the "*" label.  Go to step 6.

 From RFC 4592:

#   The change is to add the following text to part 'c' prior to the
#   instructions to "go to step 6":
#
#      If the data at the source of synthesis is a CNAME, and QTYPE
#      doesn't match CNAME, copy the CNAME RR into the answer section of
#      the response changing the owner name to the QNAME, change QNAME to
#      the canonical name in the CNAME RR, and go back to step 1.

When preparing RFC 4592, we knew that the DNAME specification was a problem.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

Sarcasm doesn't scale.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>



