wiki:InformalAgenda

Informal Telechat - May 23, 2019

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

PLEASE NOTE: The current calendar subscription URL is at (updated 2019-03-07): https://calendar.google.com/calendar/ical/ietf.org_vad13t4tfg35fc27nispen5pnc%40group.calendar.google.com/public/basic.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.1 draft-ietf-nfsv4-mv1-msns-update (Magnus)

So https://datatracker.ietf.org/doc/draft-ietf-nfsv4-mv1-msns-update/ was abstained back to the WG due to its 100+ pages of OLD / NEW / REPLACES text.

However, I now seek the guidance of the IESG about what form of the update the IESG likes to see from the WG.

Option 1.

Is what is documented in https://datatracker.ietf.org/doc/draft-ietf-nfsv4-rfc5661-msns-update/ This is form cuts out main sections that are changed by the updated and publish the updated sections in complete form. This results in a document that actually are possible to run an RFC diff on the affected sections, please se: https://tools.ietf.org/rfcdiff?url1=https://www.rfc-editor.org/rfc/rfc5661.txt&url2=https://www.ietf.org/id/draft-ietf-nfsv4-rfc5661-msns-update-00.txt. This style results in an document that are 135 pages so quite reasonable compared to its precessor.

Option 2.

Run an trial version of Adam's proposal for how to handle bis documents where one can note that this doesn't fix certain aspects. At least the editors has expressed that they don't like this idea if they forces them to wait until the process are published. So, if we are going this route, I think we need to be in agreement that this is done as an experiment with Adam's proposal. My understanding is that there is nothing in Adam's proposal that violates any existing IETF process or? Thus as long as IESG are in agreement we could try this out. However, there are a significant downside of this document, and that is that the RFC-editor may be less then happy as the result of an RFC 5661bis with these changes will run close to 700 pages.

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

3. Management Issues

3.1 "WG meeting structure" thread on wgchairs@… (Alissa)

For discussion.

3.2 Huawei (Barry)

For discussion.

3.3 CoI statement (Barry)

See my email with draft text.

3.4 PR Action for Pradeep Xplorer (Adam)

See email thread "Final decision on PR-Action against Pradeep"

3.5 Writeups related to intended status (Magnus)

3.6 NomCom? : number of ART open positions (Éric)

Currently told NomCom? about 2 open positions, do we have an update ?

Can we already get an idea of who is running again for his current position?

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

4. WG News (all)

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

4.x Issue (... who ...)

5. Documents to swap (all)

Any documents that should be swapped between ADs or areas?

6. Executive Sessions

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

7. Parking place

7.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.

Last modified 3 days ago Last modified on May 23, 2019, 6:50:19 AM