Re: [Iasa20] Magnus Westerlund's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS)

Ted Hardie <ted.ietf@gmail.com> Tue, 09 April 2019 15:57 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B921512089C; Tue, 9 Apr 2019 08:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 2IFdet1VY7Ph; Tue, 9 Apr 2019 08:57:16 -0700 (PDT)
Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 D515512044E; Tue, 9 Apr 2019 08:57:15 -0700 (PDT)
Received: by mail-io1-xd43.google.com with SMTP id b6so14777183iog.0; Tue, 09 Apr 2019 08:57:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j7MSI7C1ug0yRnhBarLa3SrJF5tJmcsLIi+YhEom/cc=; b=e7FkHOAxM8Gei0XUvWo6+rrRXI2PO7nV+Hq1oEXiUDaQps+sjOaxgaDleEOnS092c5 0QTydzoXErV1JX4Xvhy1gGFXJAZrJaNJSjAGGPML16tOolIna4qXUi33wpM/+8QYVWV5 LrhewtiB717j/68KabZTWdCOCKqkmcP73KGW2F3m9eAsAYeD1ScR0jWH6SvTVwiv1Vyj 0ka6o8jo9rzigJCq65mLNot26C+bc0saEgkO8A9MeomgvQt6canTq0lz7HfcsfSw4tmw 2uOyJuwEgvcHoFbTGGXLP1gbQCsHhht7/+Myt9LefJMU7i0vWbpBijkMTYuaGKSCiMNp u53g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j7MSI7C1ug0yRnhBarLa3SrJF5tJmcsLIi+YhEom/cc=; b=ZxlzOIzL379YoA/imIqmKfDXGKeyKzwZSQNzzk36duWxcs1Nu4BD2MGLspsAl8f+I6 /lgJjZ4KV+4GHs7GOYT1OQO0lZ1+Zh5OqNqc/lDZ45NsENydFHip5hV8eTBlXZeK94vg 2EEHy1fB/pysPvnj2Zy0XFJdD0bVSYWwN88v7DuSAfmD5Z5Ubl2ybYFqNEcC+ZSJEbH9 I4U1hn5vGhuASDr6zLbaLpmXrJtPlZiLamujza78l1BLNSarxwriFqizaRTSJ+HyhMfN lxcW1AD60Xum7r3V6FyhFCxrRIKVuLgY/OnrsvHGSL+O6Qr6SHiiuD9JeAJ+EwdfYTrr mhcg==
X-Gm-Message-State: APjAAAXx+lzN+gW25pzljGpjsQvhuS6Hw1uEgJ4eu1hYNz8hSvyoKu5a CP0zu7F+OfegPXh0OVfmuZ6HpuOqhneAmojmW8c=
X-Google-Smtp-Source: APXvYqyv2cceTnVocnK4vFKiKedoGzNYTUz4wsljFs+LJiNhrDlGZ9fT23BwF6MIEIwV3PTw5TbvShEdZ515puQUvGE=
X-Received: by 2002:a6b:6f09:: with SMTP id k9mr16754771ioc.163.1554825435063; Tue, 09 Apr 2019 08:57:15 -0700 (PDT)
MIME-Version: 1.0
References: <155480545379.14224.7509050660875750169.idtracker@ietfa.amsl.com>
In-Reply-To: <155480545379.14224.7509050660875750169.idtracker@ietfa.amsl.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 9 Apr 2019 08:56:48 -0700
Message-ID: <CA+9kkMDaV26KQve27iLYWhuXaV3VQORN=57qwaUck5yYL8aJ2Q@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: The IESG <iesg@ietf.org>, IASA 2 WG <iasa20@ietf.org>, draft-ietf-iasa2-rfc4071bis@ietf.org, iasa2-chairs@ietf.org, Jon Peterson <jon.peterson@neustar.biz>
Content-Type: multipart/alternative; boundary="000000000000bea89605861b018f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/p7ZoBcRvLe15NThY-LgQpedLeoA>
Subject: Re: [Iasa20] Magnus Westerlund's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2019 15:57:19 -0000

Hi Magnus,

On Tue, Apr 9, 2019 at 3:24 AM Magnus Westerlund via Datatracker <
noreply@ietf.org> wrote:

> Magnus Westerlund has entered the following ballot position for
> draft-ietf-iasa2-rfc4071bis-08: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4071bis/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Having not followed this at all I do see some question marks in regards to
> the
> IRTF that I would like to have clarification on thus the Discuss position.
>
> Why isn't IRTF disucssed in this section, or having its own section of
> similar
> nature?
>
> 4.6.  Relationship of the IETF LLC Board to the IETF Leadership
>
>    The IETF LLC Board is directly accountable to the IETF community for
>    the performance of the IASA 2.0.  However, the nature of the Board's
>    work involves treating the IESG and IAB as major internal customers
>    of the administrative support services.  The Board and the IETF
>    Executive Director should not consider their work successful unless
>    the IESG and IAB are also satisfied with the administrative support
>    that the IETF is receiving.
>
>
The administrative support for the IRTF has historically been bundled into
either the support of the IAB or to the meeting support (when the RGs are
meeting at the IETF meeting).   The IRTF chair, as a member of the IAB,
would be able to express concerns she or he had with the administrative
support services.

This doesn't mean that the LLC Board couldn't seek out the input of the
IRTF chair for direct discussion of concerns; this section describes what
the board must do, but doesn't limit them to only that.


> Can someone please explain why the IETF LLC role for IRTF are almost not
> at all
> described? For example is IRTF not a significant internal customer?
>
> Also, what is the relation between the IRTF and IETF community? As the IETF
> community does not appear to have a definition, it is not possible to
> determine
> if IRTF is counted as part of the IETF community or not. In my thinking the
> IETF and IRTF communities are not the same set, and it is not obvious that
> IETF
> community is the super set.
>
>
I think we use IETF in two ways.  This first encompasses the set of working
groups and structures that support the standards process,  and the second
is used more broadly, to include the IAB, IRTF, Hackathon, RFC series and
other parts of the Internet technical community which are gathered here.  I
think when we say "IETF community", we generally mean the second, because
we have no better term.  We could change the title to say something like
"Relationship of the IETF LLC Board to the other Leadership groups", but I
am not personally sure that is an improvement.


> I think some clarification on the IRTFs relation are needed in this
> document.
>
>
I don't really want to open RFC 4440 or BCP 8 for this, so I would be
interested to know what you think the minimum clarification here would be.
Would adding the IRTF as an additional internal customer be sufficient?

Ted


>
>
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>