IETF Logo Mail Archive

Re: [DNSOP] Changes to Charter

Tim Wicinski <tjw.ietf@gmail.com> Fri, 21 March 2014 13:16 UTC

Return-Path: <tjw.ietf@gmail.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 E7EAC1A03E2 for <dnsop@ietfa.amsl.com>; Fri, 21 Mar 2014 06:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 LYrPWc6WJrs5 for <dnsop@ietfa.amsl.com>; Fri, 21 Mar 2014 06:16:40 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 29C361A096A for <dnsop@ietf.org>; Fri, 21 Mar 2014 06:16:39 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id r5so2683840qcx.18 for <dnsop@ietf.org>; Fri, 21 Mar 2014 06:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/WacOWr2SgxcoxyqcpKt9Y5NcEO0mo7Bt6hu+aVdCTU=; b=Lw1gNF9Wci3vNp5L2r7JWbEnO2xkhdxcIoNp31vXo8h7dI3EEERlzklegP9GOWSMFH hU/GqsMw/xcwSdsm07WFZCaIfh4q/n2RRAhddi2rNvMAt1uz/hTypd5/GfovHT1YSERY zXHQlXWfiixN92SkR6ec3SuNBiG4EUcDngr0ZucO44pNzXBS2Y33CFz4KYmU0NccMV5U 8Gbr6XjN+o2ARsehl93mRdJJVhc/S7lYm9TEf5Wh6bWe0yWFyWHXAxmFS2/OGevWIpO8 7A0ur6UKVzduSihGmR48P+yWKNYiH4NcDjMMZcaJ4ZAz8sgKluuqfm1CJhpPZ+cJkIws 3U3A==
X-Received: by 10.229.139.199 with SMTP id f7mr57447831qcu.2.1395407789620; Fri, 21 Mar 2014 06:16:29 -0700 (PDT)
Received: from [10.33.3.173] ([204.14.236.215]) by mx.google.com with ESMTPSA id f48sm2451806qge.5.2014.03.21.06.16.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Mar 2014 06:16:28 -0700 (PDT)
Message-ID: <532C3BAC.1050108@gmail.com>
Date: Fri, 21 Mar 2014 09:16:28 -0400
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <5329F31B.20107@gmail.com> <CAHw9_i+fK=QProY4iJ0YfxiXUfUVooG_cH+zS90gTQoSAWJcxQ@mail.gmail.com>
In-Reply-To: <CAHw9_i+fK=QProY4iJ0YfxiXUfUVooG_cH+zS90gTQoSAWJcxQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/08s3PcV7kBALxFJVpsXTJ88T_28
Cc: joel jaeggli <joelja@bogus.com>, dnsop <dnsop@ietf.org>
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: Fri, 21 Mar 2014 13:16:42 -0000

On 3/21/14, 7:38 AM, Warren Kumari wrote:
> On Wed, Mar 19, 2014 at 3:42 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>>
>> 6.  Publish documents which address DNS-related issues, by identifying and
>> documenting the problem space around the issue. The group will then discuss
>> these issues and decide if which group should address the solution space.
>
> Last sentence does not parse (and I'm not quite sure what you were
> trying to say, so unclear how to fix it).
>
> W
>

Ooof.  I obviously failed to incorporate the correct wording from my 
co-chair.

What this sentence is trying to say is:
	The group will then discuss these issues and decide if which
	group should address the solution space.

Is something like this:
	dnsop will take in drafts that revolve around DNS-related issues, and 
the group will discuss the problem space (via drafts) and decide:
		1. should the solution space be addressed in dnsop?
		2. If not, help decide where the work would be better
		 carried out and work with the appropriate ADs on this.


This still sounds horrible.

tim

v2.23.0 | Report a Bug | By Email