wiki:InformalAgenda

Version 1308 (modified by spencerdawkins.ietf@…, 3 months ago) (diff)

--

Informal Telechat - November 29, 2018

Web Ex URL (updated 2015-09-09):

PLEASE NOTE: The current calendar subscription URL is at (updated 12/14/2016): https://ietf.org/calendars/private/iesg/iesg.ics

Note: If no items have been added to this wiki 24 hours before the telechat, then the telechat is cancelled. ADs should feel free to add items after that time, as long as there is *something* on the agenda 24 hours in advance.

1. Administrivia

1.1 Roll Call

1.2 Bash the Agenda

2. Document Discussions

2.x Issue (... who ...)

3. Management Issues

3.x Issue (... who ...)

3.1 Tao approval (Alissa)

3.2 Exit strategy for HotRFC from "experiment" to "part of IETF week" (Spencer)

We need to figure out (1) whether we agree that HotRFC is useful enough to keep doing it, after three IETF meetings, (2) figure out whether there's anything we need to do differently for IETF 104 (for example, we haven't been providing remote ACCESS, and that's been questioned, although providing remote PARTICIPATION doesn't make much sense to me), and (3) figure out whether there's anything that "we" can do to be helpful between "I did my HotRFC pitch" and "here's the new work proposal/BOF request" (sample questions include "should we have a mailing list for HotRFC to use for ad hoc connections between proponents and interested parties, because the closest we can come right now is sending to NNNattendees mailing list").

It would also be helpful to identify someone who's going to be on the IESG after IETF 104 to be the contact for HotRFC that takes over from Spencer. Volunteers?

3.3 IETF 103 plenary follow-up (Alissa)

Time to discuss toxic working groups, training, and other topics arising from the plenary Q&A.

3.4 IESG Mailing List Membership Visibility (Adam)

Currently, the list recipients of mail sent to "iesg@…" is available only to the list administrators (see https://ietf.org/mailman/listinfo/iesg/), while the membership of most other mailing lists hosted on ietf.org are visible to all subscribers of the list. This unavailability of list membership makes it difficult for IESG members to make informed decisions about whether to send messages to iesg-only@… or iesg@…. Should we consider changing the mailman configuration to allow subscribers to see the current subscriber list?

3.5 Next steps for whatever we're calling "announcements of newly-adopted IETF work" (Spencer)

I THINK the IESG likes doing a mailing list that roughly announces newly-adopted IETF work, based on pattern-matching draft file names against "draft-ietf-*-00".

I THINK the IESG is OK to go ahead with this now, for the IETF stream, and let other stream managers do the right thing for their own streams.

I THINK we talked about giving the WG chairs a heads-up about this, just in case there are any land mines we're not seeing, and in case WG chairs want to think about when they want to announce that they've adopted a draft, and in case any WG chairs that don't rename drafts when they're adopted want to start, so their drafts will be included.

I THINK the next step is to send this as a tools request, properly prioritized. Who does that?

Greg Woods also suggested asking for feedback from the IESG Comms Review Team. I told him that sounded like a fine idea to me.

Are we done here?

4. WG News (all)

Any news that would have a cross-WG or cross-area impact?

5. Executive Sessions

5.x Issue (... who ...)

6. Parking place

6.x Issue (... who ...)

Editing hints

When adding a management issue to Section 3, use the following Wiki markup:

=== 3.1 Talk about the Weather ===

A sunny day, today!

Do not use any other Wiki markup or features on this page (above the line) -- this page will be parsed by the AD Dashboard tool in the future.

Use triple braces { and } on their own lines to ensure the text appears without formatting but in a grey box. Like so:

The quick brown fox says .....

Note that this page is public, and all the old versions are available, too.