Re: [Add] Proposed charter and BoF request for IETF 106

S Moonesamy <sm+ietf@elandsys.com> Thu, 10 October 2019 05:30 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5416B120043 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 22:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
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 d9kBnjRFQ2DK for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 22:30:35 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id D93DB120044 for <add@ietf.org>; Wed, 9 Oct 2019 22:30:35 -0700 (PDT)
Received: from sm-THINK.elandsys.com ([102.115.166.197]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x9A5TrOj004879 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Oct 2019 22:30:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1570685430; x=1570771830; i=@elandsys.com; bh=kOIobD6K2HNnZYcbZKF7IYKcXI0TxHShSZRokP69+kw=; h=Date:To:From:Subject:In-Reply-To:References; b=cFPsRCxzifeGwXDcU4InNu3E6XA8eOYniDDHgmMukb3lnzA0RNezSvmVdGlj78gaO dQkG8l11B4vYYWNUrIYpHQAifhDdRNyJEOYjxC6noddImQ4Hcl+hO2SpXGKTK3z4Ed 7Yzd7cDzeW9JftgJ7jAcpslx5ihBCqTqj4X/aKhY=
Message-Id: <6.2.5.6.2.20191009195808.08165628@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 Oct 2019 20:46:25 -0700
To: Barry Leiba <barryleiba@computer.org>, add@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.g mail.com>
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/y2JUAxBVPC5vaM1Yk4b2xm0aCO4>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2019 05:30:37 -0000

Hi Barry,
At 12:38 AM 10/9/2019, Barry Leiba wrote:
>The IESG has worked up a proposal for a possible working group, which
>we're tentatively calling "ABCD", for "Application Behavior
>Considering DNS".  We can discuss the charter proposal here, and
>expect to approve a working-group-forming BoF for Singapore.

The topic looks like it is about (re)defining how DNS works.  The 
draft charter is quite broad.  I could not figure out what would be 
in scope and what would be out of scope.  That could be clarified as 
part of WG chartering.

My reading of the DPRIVE WG charter is that the WG was chartered to 
address concerns surrounding RFC 7258.  That is also a specific area 
of focus of this BOF proposal.  I suggest clarifying that (please see 
my previous comment about scope).

The area of focus mentions DNS transport including recommendations on 
detail protocol usage.  Does that mean the the group will make 
recommendations about when to use DNS over TLS and when to use DNS over TLS?

Regards,
S. Moonesamy