Re: [Mtgvenue] About draft-ietf-mtgvenue-iaoc-venue-selection-process

[Eliot Lear <[e-mail]>]

Thanks, Michael and Lou for your thoughts.  What I am thinking about is
this: what is best for the reader?  I feel pretty strongly that at the
very least, the reference to 4071 has to come out, as it describes an
inapplicable appeals process and a structure that no longer matches how
we are operating; and simply replacing that reference with BCP 101 won't
do either, because that really just refers the reader back to RFC 4071,
as a practical matter, and there's reason to believe that there will be
a replacement appeals process that is applicable here (the big secret
here is that there really wasn't much of an appeals process in this
situation re 4071, but referencing 4071 used less words).

Your suggestion below talks about a change to the introduction to
essentially redefine the IASA.  I think if we're doing that, there are
some other alternatives we should consider, like replacing the word
"IASA" with "meeting organizers".  And then we simply point to who those
are at this moment (e.g, the LLC).  I love using plain English when we can.

To Lou's point about feeling rushed, had I believed that the LLC was
going to move as fast as it did, I would have not wanted to advance this
doc, but here we are, and AUTH48 is just a state and the RFC Editor has
patience, so... let's just figure out what the right thing to do is.

Eliot

On 17.10.18 15:43, Michael Richardson wrote:
> I think that what Eliot would like to do is change "IASA" to "LLC".
>
> Lou has suggested that "IASA" is an abstraction (a layer of indirection)
> which was resolved to IAOC before, and that now resolved to "LLC".
>
> Eliot has then asked, if IASA is a superset of LLC, what is there of
> IASA which is not LLC.  If it's empty, why make it hard for the reader,
> and just dereference the pointer.
>
> I can see both points.
>
> I suggest the text of the abstract be:
>     The IETF Administrative Support Activity (IASA) (implemented by the IETF
>     LLC) is responsible for arranging the selection and operation of the IETF
>     plenary meeting venue.  ...
>
>
> Intro:
>    The IETF Administrative Support Activity (IASA) is
>    responsible for arranging the selection and operation of the IETF
>    plenary meeting venue.  Until he fall of 2018, the IASA was embodied in
>    the form of the IETF Administrative Oversight Committee (IAOC).  From
>    fall 2018 onwards, the IASA was implemented by the IETF LLC.  This
>    document uses the abstract term "IASA" to refer to both embodiments.
>
>    The purpose of this document is to guide the IASA...
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [
>
>
> --
> Michael Richardson <[e-mail]>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
>
> _______________________________________________
> Mtgvenue mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mtgvenue