Re: [Inip-discuss] Domain Names

Suzanne Woolf <suzworldwide@gmail.com> Fri, 18 December 2015 21:01 UTC

Return-Path: <suzworldwide@gmail.com>
X-Original-To: inip-discuss@ietfa.amsl.com
Delivered-To: inip-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BF71B38EF for <inip-discuss@ietfa.amsl.com>; Fri, 18 Dec 2015 13:01:42 -0800 (PST)
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 ay7noYbgfOTM for <inip-discuss@ietfa.amsl.com>; Fri, 18 Dec 2015 13:01:40 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 137011B3772 for <inip-discuss@iab.org>; Fri, 18 Dec 2015 13:01:40 -0800 (PST)
Received: by mail-qg0-x234.google.com with SMTP id p62so12769926qge.1 for <inip-discuss@iab.org>; Fri, 18 Dec 2015 13:01:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=22ab8lO1M3x9ASOBXvhEK4OwcAJ6u6JQPM5Y2c/q3Lc=; b=bxBt5It1FBrswemH8SVHLVUYwhC95dT07IF4dfwnKm7N001VY7NvZJPNqFPjleBVzL Ca1PXDOEjzFAr377gjLxNAN22GWyS9ffpymRZK2zU1N2c3dH37kyKx5VKl6yDn/7fSj4 cpZBCvQdF96LXTO3zlG7wweutHYs3Cud14r3ytxeAyhyu8+E+UPhv0FuF6XogW4Ttgvy s8NeRmdry/440B7a8o2aW5woG4QnQhUbyKQcbprBN+5dFUs4Gq03Psn/HYRFjvphu+xZ xcal4MYxIyXC6ZjlgCCw4lrcZ4S2Na5cQnx4T2jukFtxSAGUYMCkq0KmMKJMQBu6pdJ7 2e8A==
X-Received: by 10.140.28.116 with SMTP id 107mr7989288qgy.40.1450472499186; Fri, 18 Dec 2015 13:01:39 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by smtp.gmail.com with ESMTPSA id 6sm7544546qgf.34.2015.12.18.13.01.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 18 Dec 2015 13:01:38 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <CAHw9_iLGR_-z6K0GtYTcv+azoCink4rhcAjMiYZX_e1iPRyjPg@mail.gmail.com>
Date: Fri, 18 Dec 2015 16:05:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCC44572-4377-4767-8364-08A7C1355CC5@gmail.com>
References: <D285CCDC.11B63%edward.lewis@icann.org> <CAHw9_i+tKjR87VADPzgm3xEWvQebqr_sigs9oEy3d5LKa4EcCQ@mail.gmail.com> <567429FE.5030503@cse.mrt.ac.lk> <CAHw9_iLGR_-z6K0GtYTcv+azoCink4rhcAjMiYZX_e1iPRyjPg@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/inip-discuss/YbbNCwLApHxdSz7MThW7SehNQZQ>
Cc: inip-discuss@iab.org, Gihan Dias <gihan@cse.mrt.ac.lk>
Subject: Re: [Inip-discuss] Domain Names
X-BeenThere: inip-discuss@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IAB Internet Names and Identifiers Discussion List <inip-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/inip-discuss/>
List-Post: <mailto:inip-discuss@iab.org>
List-Help: <mailto:inip-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/inip-discuss>, <mailto:inip-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2015 21:01:42 -0000

Warren,

Thanks, you saved me the cutting and pasting on what we’ve published about the INIP program, IAB programs generally, and this list. I’ll skip to your more specific question:


> On Dec 18, 2015, at 2:22 PM, Warren Kumari <warren@kumari.net> wrote:
> 
> Which leads to some of my confusions about how this related to the design team vs discussions in dnsop, what the status of all this is, etc.

First— the IAB INIP program, and this list, have no direct relationship with “the design team” (I presume you mean the discussion of special use names in DNSOP), or the DNSOP WG, or any IETF WG. They’re defined by an area of interest for the IAB in the architecture of the internet (see the program description you quoted).

To expand on that a little bit— the IAB’s technical programs are there to provide input and advice to the IAB on issues for the architecture of the internet— things the IAB should (or even should not) be working on. They’re a supplement to the knowledge of individual IAB members, meant to persist beyond any individual IAB member’s term, and a mechanism for doing intensive work when specific areas are identified where the IAB and the larger community might benefit from coherent advice in a timely way. But unless a WG or AD ask, there’s no direct relationship at all between an IAB program and an IETF WG.

The IAB recently decided that all of the technical programs should have public, open-subscription lists, to make sure we’re getting the widest input possible on those topics if architectural interest and to support transparency in “what are the programs doing anyway?”

For this list in particular: When Ed first sent his email  about his draft to the IAB, he got several responses, including some discussion within the INIP program, at least one detailed review I know of, and a suggestion that the draft might be good as an IAB-stream RFC. He also got a suggestion that since the IAB has decided to spin up open lists associated with Program topics, he might want to seek review of his document and his ideas among like-minded folks on this list.

As the IAB lead for the INIP program, I’d be very, very happy to see review of Ed’s document and associated ideas here, especially towards an IAB RFC that might provide guidance to the wider community.

And if you have a related topic you’d rather discuss, please feel free. But if it’s on-charter for an IETF WG, it might be too narrow and specific to bring here.


best,
Suzanne
(also happy to have other IAB members chime in)