Re: [DNSOP] Changes to Charter

joel jaeggli <joelja@bogus.com> Tue, 25 March 2014 16:14 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38ADD1A01C6 for <dnsop@ietfa.amsl.com>; Tue, 25 Mar 2014 09:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxFtV05reSSb for <dnsop@ietfa.amsl.com>; Tue, 25 Mar 2014 09:14:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 55E1E1A01B6 for <dnsop@ietf.org>; Tue, 25 Mar 2014 09:14:04 -0700 (PDT)
Received: from mb-aye.local ([173.247.205.34]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s2PGE1UO087364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Mar 2014 16:14:02 GMT (envelope-from joelja@bogus.com)
Message-ID: <5331AB49.5000500@bogus.com>
Date: Tue, 25 Mar 2014 09:14:01 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Thunderbird/28.0
MIME-Version: 1.0
To: Tim Wicinski <tjw.ietf@gmail.com>, dnsop@ietf.org
References: <5329F31B.20107@gmail.com> <53306FDD.20100@bogus.com> <5331A34E.7010702@gmail.com>
In-Reply-To: <5331A34E.7010702@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="I4M71HxKtxe18DU5hcPgGDHRvtfkvV0L3"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Tue, 25 Mar 2014 16:14:02 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/EtcMELSDRSs9qW4aT11-Uv0_dxo
Subject: Re: [DNSOP] Changes to Charter
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Mar 2014 16:14:11 -0000

On 3/25/14, 8:39 AM, Tim Wicinski wrote:
> 
> 
> On 3/24/14, 1:48 PM, joel jaeggli wrote:
>> On 3/19/14, 12:42 PM, Tim Wicinski wrote:
>>>
>>> 5. Address possible minor changes or extensions to the DNS Protocol,
>>> initially with a focus on the operational impacts of these changes. Act
>>> as clearinghouse or providing advice to ADs and other WGs on EDNS0
>>> options, new RRTYPEs, record synthesis, or other mechanics of  extending
>>> DNS to support other applications.
>>
>> I fell like this is intended to allow work on issues related to the
>> root/tld registration but without being explicit. I'm a little on the
>> fence with respect to how explicit we want to but I think we should
>> actually call it out.
>>
> 
> We were trying to be explicitly vague, or vaguely explicit.  I was
> thinking we could say something like "such as root/tld conflicts or
> namespace or application space conflicts".
> 

if I had to channel my other colleagues on the IESG it's probably
important enough to warrant it's own bullet. I will ultimately get my
own chance to whittle at the text so it's just a suggestion.