[Ianaplan] [iab-chair@iab.org: [IAB] IAB comment on question from ICG]

Andrew Sullivan <ajs@anvilwalrusden.com> Thu, 08 October 2015 18:40 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id DED531A8845 for <ianaplan@ietfa.amsl.com>; Thu, 8 Oct 2015 11:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IV8V-HSqTsw7 for <ianaplan@ietfa.amsl.com>; Thu, 8 Oct 2015 11:40:14 -0700 (PDT)
Received: from mx2.yitter.info (mx2.yitter.info []) by ietfa.amsl.com (Postfix) with ESMTP id 73F721A6F9E for <ianaplan@ietf.org>; Thu, 8 Oct 2015 11:40:14 -0700 (PDT)
Received: from localhost (localhost []) by mx2.yitter.info (Postfix) with ESMTP id 39FCC1072E for <ianaplan@ietf.org>; Thu, 8 Oct 2015 18:40:13 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx2.yitter.info ([]) by localhost (mx2.yitter.info []) (amavisd-new, port 10024) with ESMTP id xOO1Z9trzs4I for <ianaplan@ietf.org>; Thu, 8 Oct 2015 18:40:10 +0000 (UTC)
Received: from mx2.yitter.info (c-73-142-68-92.hsd1.nh.comcast.net []) by mx2.yitter.info (Postfix) with ESMTPSA id 9CE331073A for <ianaplan@ietf.org>; Thu, 8 Oct 2015 18:40:10 +0000 (UTC)
Date: Thu, 8 Oct 2015 14:40:08 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20151008184008.GQ17602@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/7dCBmrMxtL-GKoMO8l3wzcom168>
Subject: [Ianaplan] [iab-chair@iab.org: [IAB] IAB comment on question from ICG]
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2015 18:40:16 -0000

Dear colleagues,

The IAB sent the following message to the ICG.

Best regards,


----- Forwarded message from IAB Chair <iab-chair@iab.org>; -----

Date: Thu, 8 Oct 2015 12:58:28 -0400
From: IAB Chair <iab-chair@iab.org>;
To: alissa@cooperw.in
Cc: IAB <iab@iab.org>;
Subject: [IAB] IAB comment on question from ICG
List-Id: "Internet Architecture Board \(IAB\)" <iab.iab.org>

The ICG has posed the following question to the protocol parameters

"The three operational communities have a long history of cooperation
as needed to help ensure the smooth functioning of the DNS and the
Internet. A number of comments were concerned that the three IANA
functions could end up being carried out by different operators and
suggested that there was a need for some information exchange and
coordination between the operational communities to ensure a proper
understanding of the impact a change might have on the operation of
the other functions (perhaps because of interdependencies between the
functions or because of shared resources or key staff). This
information exchange might also help in coordinating action in the
case of remedying operational difficulties. For this to work, the
three operational communities need to commit to coordinating and
cooperating as necessary when changing operator, whether by leveraging
existing coordination mechanisms or new ones.  Can the protocol
parameters operational community provide such a commitment?"

As noted in the IANAPLAN documents, elements of this work are already
in place: "The IETF leadership, ICANN, and the RIRs maintain an
ongoing informal dialog".  The IAB further notes that it has a
chartered responsibility for maintaining technical liaison
relationships "with other organizations concerned with standards and
other technical and organizational issues relevant to the world-wide
Internet."  ‚ÄčThe IAB believes that the information exchange described
by the ICG falls within the IAB's ongoing commitment to serve as the
point of coordination for the IETF, and the IAB remains committed to
continuing such coordination.  Furthermore, the IAB believes that the
dialogue would be extended to other organizations as circumstances

----- End forwarded message -----

Andrew Sullivan