IETF Logo Mail Archive

Re: [Iasa20] Benjamin Kaduk's No Objection on draft-ietf-iasa2-rfc4071bis-09: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Thu, 11 April 2019 17:28 UTC

Return-Path: <kaduk@mit.edu>
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 A8DD9120663; Thu, 11 Apr 2019 10:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 noacZxijL3hh; Thu, 11 Apr 2019 10:28:07 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6C68120312; Thu, 11 Apr 2019 10:28:07 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x3BHS18b013299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Apr 2019 13:28:04 -0400
Date: Thu, 11 Apr 2019 12:28:01 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Joseph Lorenzo Hall <joe@cdt.org>, IASA 2 WG <iasa20@ietf.org>, The IESG <iesg@ietf.org>
Message-ID: <20190411172801.GJ18549@kduck.mit.edu>
References: <155498907076.25231.13801022071773065752.idtracker@ietfa.amsl.com> <CABtrr-XbQkVvGykEMDnb9jyFxZaei39R=4KgbnBXsB5nsoermQ@mail.gmail.com> <CABtrr-W6qevLCOZPUgrMsARq+fVJr7zK2Z5X=j6xBZbZ9Tybag@mail.gmail.com> <CA+9kkMC+=3s8nuSp-KGooWL0DbgobUtFejwJNS4_nLN_EEPbsA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+9kkMC+=3s8nuSp-KGooWL0DbgobUtFejwJNS4_nLN_EEPbsA@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/s9pY4tHDs47UWyG3QpZsBSsnZIk>
Subject: Re: [Iasa20] Benjamin Kaduk's No Objection on draft-ietf-iasa2-rfc4071bis-09: (with COMMENT)
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: Thu, 11 Apr 2019 17:28:10 -0000

On Thu, Apr 11, 2019 at 10:25:00AM -0700, Ted Hardie wrote:
> Howdy,
> 
> On Thu, Apr 11, 2019 at 8:48 AM Joseph Lorenzo Hall <joe@cdt.org> wrote:
> 
> >
> >
> > On Thu, Apr 11, 2019 at 11:05 AM Joseph Lorenzo Hall <joe@cdt.org> wrote:
> >
> >>
> >> Section 7.7
> >>>
> >>>    The IETF LLC exists to support the IETF, IAB, and IRTF.  Therefore,
> >>>    the IETF LLC's funding and all revenues, in-kind contributions, and
> >>>    other income that comprise that funding shall be used solely to
> >>>    support activities related to the IETF, IAB, IRTF, and RFC Editor,
> >>>    and for no other purposes.
> >>>
> >>> Why are the lists in the first and second sentences different?
> >>>
> >>
> >> Because the RFC Editor is contracted through the IAB, but that somewhere
> >> in the WG discussion it felt important to call out in the second list. I
> >> don't think we can just add the RFC Editor to the first list... but we
> >> could do something like this: "The IETF LLC exists to support the IETF,
> >> IRTF, and IAB (through which the RFC Editor receives support)."
> >>
> >
> > Mirja pointed out correctly that the RFC Editor is contracted by the LLC,
> > so I am wrong here. best, Joe
> >
> 
> It's a bit more complicated than that, but since we are creating a 6635bis,
> maybe leave this topic to the that?

To be clear, I'm not insisting on a change here, and just wondered if the
lists were supposed to be synchronized (or not).

-Ben

v2.8.7 | Report a Bug | By Email