Re: [DNSOP] Changes to Charter

Daniel Migault <mglt.ietf@gmail.com> Fri, 21 March 2014 13:46 UTC

Return-Path: <mglt.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 0585D1A08C2 for <dnsop@ietfa.amsl.com>; Fri, 21 Mar 2014 06:46:24 -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 wPdLqBKQsEqy for <dnsop@ietfa.amsl.com>; Fri, 21 Mar 2014 06:46:22 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4623A1A0755 for <dnsop@ietf.org>; Fri, 21 Mar 2014 06:46:22 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id i8so2720767qcq.37 for <dnsop@ietf.org>; Fri, 21 Mar 2014 06:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PFoZl/viEbT//LV7bPGLJZlNjUx6mGQlkCynlGGcki8=; b=qPsxTQvgdbOC/WlMycJ/y2W3e+4zWpRGRy792LpjqIhrA76MZvMjHoYSv+NPH5p9w2 QIsVaRQ26V6Zn/Qq/d0C8ZVcOR+o05uxi6yAwu5yB8XmJkao9moarMvI4NfhZbiBRQqu vvQqcNzAFLbyJC24LIu29VmOJQqvRxj73IQZiRCcj8P22xOAmR8Ad0ADQKi0Kvt5mSY2 srJhlhxRcJnBB33ULyB0u7yfH0cUAQ+UqIJcPSBM9onRZg++ncOLYeIp+X2rKhNjxdjx JjK5ctXOG4G+4ANIhOlCA5Dc153Pr9SDCDkbBW5OVRQFIC/MYzBwTw/nbh+GnReAaCcE 9zWw==
MIME-Version: 1.0
X-Received: by 10.140.28.100 with SMTP id 91mr29329962qgy.36.1395409572848; Fri, 21 Mar 2014 06:46:12 -0700 (PDT)
Received: by 10.140.48.208 with HTTP; Fri, 21 Mar 2014 06:46:12 -0700 (PDT)
In-Reply-To: <532C3BAC.1050108@gmail.com>
References: <5329F31B.20107@gmail.com> <CAHw9_i+fK=QProY4iJ0YfxiXUfUVooG_cH+zS90gTQoSAWJcxQ@mail.gmail.com> <532C3BAC.1050108@gmail.com>
Date: Fri, 21 Mar 2014 14:46:12 +0100
Message-ID: <CADZyTknWKw8O53HphWfrojCwjFsOwsdqkS7PKK=zNQ+stC85yA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: Tim Wicinski <tjw.ietf@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/l393QZf-WVHy_i7ikxqiwhRexBM
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:46:24 -0000

I am fine with these 2 items if DNS includes DNSSEC. Maybe replacing
DNS by "DNS or DNSSEC" clarify this.

On Fri, Mar 21, 2014 at 2:16 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
>
>
> 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
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58