Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt

Ted Hardie <ted.ietf@gmail.com> Tue, 02 February 2016 21:58 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399471A009E for <ietf@ietfa.amsl.com>; Tue, 2 Feb 2016 13:58:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level:
X-Spam-Status: No, score=0.301 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, HTML_MESSAGE=0.001, MANGLED_SEX=2.3, SPF_PASS=-0.001] autolearn=no
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 jWJXviEZIjgo for <ietf@ietfa.amsl.com>; Tue, 2 Feb 2016 13:57:57 -0800 (PST)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 78ABB1A009D for <ietf@ietf.org>; Tue, 2 Feb 2016 13:57:57 -0800 (PST)
Received: by mail-qg0-x235.google.com with SMTP id u30so1950771qge.1 for <ietf@ietf.org>; Tue, 02 Feb 2016 13:57:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9IDxR8OEVSprFX0Z0g4Fbw1nr77SrQKLh7pDfa/9bCQ=; b=0yJEXpL0UY5g27RItXycp1UEPyb6mhJhw26SShnCGBKSHxheZL8M1rCQG7w3uDSp27 A4x21Ar5aoINg0qArgPy0aOcgRFHbC4Z6dfxX4cWADph0MQv6PkMpFbuFpTxgwhAyEWH wBQrfGyznz1Lim9FKe/muCHOA27lwrELXnoXKSkDYVNTRq/IfzI9G4CCcoevxqJOd5B9 x+vIHX531mZh/7m16j+1goE7EMfBVfdJyS+2gufA/uAMjkPjDNKi/OgnqlhYs9V3tGIR layMXz/cl/fTId6YPh+JU3qwcWf4LOEM62R2bXWBC6v4QBpny4+lmffv3sGK3TduQB2A SG9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9IDxR8OEVSprFX0Z0g4Fbw1nr77SrQKLh7pDfa/9bCQ=; b=l8VNrP9Ty2htXnbD3YbrZdaUbAM8I1dRQiwzlCcIEypGNS6Xablnmqypki9lTnbRNe Vlrss/FEfC39/qD0QptqwCRi8CzvCETqBdQBDdZMyTgbeYPdj0HLi3Ag8wgfO6nE/HsP k+U8PZSKQMMY8ST7K5oG8EPGZncwbNYC/w/M3FdkGzIWZ57cXLzbteTsB9pztolqFqKf OoL+Fet4bqgMXE8EXn6p/24Xd6bh4xOMm0fkoC/KkBbV733p0+Vv5m0sla+jTM6/jyUa he0EWvP+g9UBPkzhwIBE7hknHvjD/wDYpq5agokc2/79RzWG0wXM12sNQuBiavFwQa4r LAUg==
X-Gm-Message-State: AG10YOR9CQ8nCm9KUJpdLm0NAkwV1/aiCK5wpdTD6DaifwUuvTzlD5OZRsnt8cL+AJBZ7Jbd6q0nRl0tRmIE9w==
X-Received: by 10.140.30.102 with SMTP id c93mr37843899qgc.80.1454450276507; Tue, 02 Feb 2016 13:57:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.14.211 with HTTP; Tue, 2 Feb 2016 13:57:36 -0800 (PST)
In-Reply-To: <2DBB9F0D-0965-4562-9D9D-8183A0010071@gmail.com>
References: <20160202182036.26498.27650.idtracker@ietfa.amsl.com> <56B10131.7040603@gmail.com> <2DBB9F0D-0965-4562-9D9D-8183A0010071@gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 02 Feb 2016 13:57:36 -0800
Message-ID: <CA+9kkMAsYTJiYSf4FgeALGOiApo6x-0C80wTKCFMEjJQt+cm3g@mail.gmail.com>
Subject: Re: I-D Action: draft-hardie-iaoc-iab-update-00.txt
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary="001a11394192132896052ad0985c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ysF7F-W_QcPzELvFj3E1D2_37k4>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 21:58:00 -0000

On Tue, Feb 2, 2016 at 1:02 PM, Bob Hinden <bob.hinden@gmail.com> wrote:

> I agree with Brian’s comments about this having to update BCP 101 and
> think it get too much into how the IAB currently organizes itself.
>
> The document reads like the IAB Chair position on the IAOC will be
> replaced by an committee (aka IAB Program).  The person in this role is a
> voting member of the IAOC and IETF Trust, and needs to be able to exercise
> their judgement in real time.  It’s going to be a problem operationally if
> they have to consult the committee before voting.  I think this needs some
> more work in the document.
>
>
​I'm happy to work with the other authors to adjust the language on this,
because that's not the intent.  The intent is to have the program lead be
the voting member and to be able to exercise appropriate judgement in real
time.  The other program members are there to provide advice based on their
commitment to keep up with the *public* information from the IAOC (so not
its internal correspondence, but the public reports, RFPs, minutes, etc.).

If you have specific language you'd like to see in a revision, please let
us know.​



> The description in the draft of what this committee does seem like a
> subset of the IAOC and Trust responsibilities (one example, it doesn’t
> include meeting venue decisions).  It’s a lot more than just reviewing
> “correspondence”, it's also about how the IAOC  works toward decisions.  I
> don’t know if that was intentional or not.  I would think not, but it’s not
> clear.
>
> Also, I suspect in practice that the IAB chair doesn’t spend a lot of time
> reviwing things like RFPs, IAOC and Trust minutes, and other reports, so
> moving this to the IAB committee isn’t that important.  They are there for
> the bigger issues.
>
> While I understand the motivation behind this, I think that the current
> structure for the IAOC and IETF Trust has worked well when we face
> significant issues.  The IANA transition is the latest of these, but it’s
> clear there will be more.  I think it’s been very important that IAB chair
> is directly involved in how the IAOC responds to IETF and Internet
> community issues. Not having the IAB Chair directly involved has downsides
> that are not described in the document.
>
>
​While I agree that it is very important that the IAB ​has to be invested
in how the IAOC responds to the IETF and Internet community issues (like
the IANA transition), it already responds to many similar issues with the
advice and help of a program.  The RSOC, mentioned in the draft, is one.
To take another, there is also a long-standing progam on IANA evolution,
which has provided a great deal of insight on the transition.


> Further, it seems to me that the next phase of the IANA transition where
> the implementation starts is going to see a bigger load on the IAOC and
> IETF Trust.  A lot of decisions will have to be made and having the IAB
> Chair at the table is going to be important.
>
> ​The trade-offs here, in a nutshell, are: we can provide the Chair and
limit the time the chair spends at the table; choose a chair specifically
be​cause they have the support to devote all their time to the job; or
split the work so that the IAB gives its attention to this matter through
someone identified as best suited to the specific job.  It's not clear we
can get everything at once and even if we can in some particular historical
moment, it's not at all clear that we can count on it as a baseline.

Thanks for your review,

Ted




> Bob
>
> > On Feb 2, 2016, at 11:19 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> >
> > Hi,
> >
> > I think this draft mixes up two things.
> >
> > (1) A proposal that the IAB Chair's ex officio seat in the IAOC be
> changed
> > to be a seat for an IAB voting member designated by the IAB. That of
> course
> > can only be achieved by an RFC that formally updates RFC 4071 and so
> becomes
> > part of BCP 101.
> >
> > (2) A description of some IAB internal organisational matters, which the
> IAB
> > is clearly free to arrange how it wants, and publish if it wants. IAB
> > internal arrangements don't need to be BCPs.
> >
> > I've got nothing to say about (2).
> >
> > About (1), I think we should hear the pros and cons, because I doubt if
> > this proposal arose in a vacuum. In particular, how would this help the
> > IAOC be more effective and more responsive to community concerns?
> >
> > Regards
> >   Brian Carpenter
> >
> > On 03/02/2016 07:20, internet-drafts@ietf.org wrote:
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>
> >>
> >>        Title           : Updating the ex-officio member of the IAB in
> the IAOC
> >>        Authors         : Ted Hardie
> >>                          Andrew Sullivan
> >>                          Russ Housley
> >>      Filename        : draft-hardie-iaoc-iab-update-00.txt
> >>      Pages           : 4
> >>      Date            : 2016-02-02
> >>
> >> Abstract:
> >>   At the time the IETF Administrative Oversight Committee was set up
> >>   the Internet Architecture Board had an internal structure
> >>   significantly different from its current structure.  This document
> >>   aims to update the ex officio member from the IAB who serves on the
> >>   IAOC in order to better account for that change and better match the
> >>   skills set out in RFC 4333.
> >>
> >>
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-hardie-iaoc-iab-update/
> >>
> >> There's also a htmlized version available at:
> >> https://tools.ietf.org/html/draft-hardie-iaoc-iab-update-00
> >>
> >>
> >> Please note that it may take a couple of minutes from the time of
> submission
> >> until the htmlized version and diff are available at tools.ietf.org.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> >> I-D-Announce mailing list
> >> I-D-Announce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/i-d-announce
> >> Internet-Draft directories: http://www.ietf.org/shadow.html
> >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >
>
>