Re: COME ON FOLKS!!!! RE: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-08.txt>

Mark Stapp <mjs@cisco.com> Fri, 13 May 2005 18:37 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DWf2B-0006Dt-CW; Fri, 13 May 2005 14:37:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DWf2A-0006Do-CK for dhcwg@megatron.ietf.org; Fri, 13 May 2005 14:37:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12654 for <dhcwg@ietf.org>; Fri, 13 May 2005 14:37:12 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DWfI8-00035L-4d for dhcwg@ietf.org; Fri, 13 May 2005 14:53:45 -0400
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 13 May 2005 11:37:04 -0700
X-IronPort-AV: i="3.93,107,1115017200"; d="scan'208"; a="264952393:sNHT31237608"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j4DIahQ0024853 for <dhcwg@ietf.org>; Fri, 13 May 2005 11:37:01 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 13 May 2005 11:37:00 -0700
Received: from [161.44.65.205] ([161.44.65.205]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 13 May 2005 11:36:39 -0700
Message-ID: <4284F36B.605@cisco.com>
Date: Fri, 13 May 2005 14:35:23 -0400
From: Mark Stapp <mjs@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: COME ON FOLKS!!!! RE: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-08.txt>
References: <8E296595B6471A4689555D5D725EBB2122DC47@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2122DC47@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 May 2005 18:36:39.0479 (UTC) FILETIME=[B376AC70:01C557EA]
X-Spam-Score: 1.3 (+)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

yes, I want this draft to advance to the iesg (and, just maybe, beyond)

thank you for your energy and determination, Bernie!

-- Mark

Bernie Volz (volz) wrote:

>I don't believe there were ANY responses to this WG last call. Either
>positive or negative.
>
>Now, we can all complain about the slow progress within the IETF, but WE
>ARE THE CAUSE OF THOSE PROBLEMS! Not the IESG.
>
>The FQDN related work has been stalled for YEARS! Several different
>people have worked on it and it has never been brought to closure.
>
>Well, I thought we finally had a good chance to bring this work to a
>close, but it just won't happen if YOU ALL don't want it to happen.
>Apparently no one cares about this issue??
>
>And this document, as I understand it, is the last piece of work holding
>up the FQDN drafts (though of course there may be issues raised within
>the IETF last call and/or IESG review).
>
>As the WG Last Call period has officially ended, I don't know if the
>chairs will accept comments, but it certainly can't hurt for people to
>respond one way or another.
>
>Personally, I'm not going to put a lot more effort into this work if the
>WG won't support it. So, it will soon fall to yet another person or
>group to complete this work (if it ever will be).
>
>Sorry for the rant.
>
>- Bernie
> 
>
>  
>
>>-----Original Message-----
>>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
>>On Behalf Of Ralph Droms
>>Sent: Monday, April 11, 2005 3:08 PM
>>To: dhcwg@ietf.org
>>Cc: Stig Venaas
>>Subject: [dhcwg] dhc WG last call on 
>><draft-ietf-dhc-ddns-resolution-08.txt>
>>
>>
>>This message announces a WG last call on "Resolution of DNS
>>Name Conflicts among DHCP Clients"
>><draft-ietf-dhc-ddns-resolution-08.txt>.  The last call will
>>conclude at 1700 EST (USA) on 2005-04-25.
>>
>>Please respond to this WG last call.  If you support
>>acceptance of the document without change, respond with a
>>simple acknowledgment, so that support for the document can
>>be assessed.  Lack of discussion does not represent positive
>>support.  If there is no expression of support for
>>acceptance during the WG last call, the document will not be
>>advanced to the IESG.
>>
>>There are options in DHCP that can be used for transmitting
>>information about updating DNS. However, these do not
>>explicitly control updating the name to address and address
>>to name mappings maintained in the DNS, as performed by
>>hosts acting as DHCP clients and servers.
>>draft-ietf-dhc-ddns-resolution-08.txt describes techniques
>>for the resolution of DNS name conflicts among DHCP clients
>>and servers.  This draft is available as
>>http://www.ietf.org/internet-drafts/draft-ietf-dhc-ddns-
>>resolution-08.txt
>>
>>- Ralph Droms 
>>
>>
>>_______________________________________________
>>dhcwg mailing list
>>dhcwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/dhcwg
>>
>>    
>>
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg
>
>  
>

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg