Re: [v6ops] v6ops - Update to a Meeting Session Request for IETF 111

[Fred Baker <[e-mail]>]

Following up on the document list. See attached. This data is data tracker data that is reorganized into a format that I find more useful - each document has several statuses (has it been posted? What does the Working Group, IESG, or RFC Editor think of it?), and I try to sort that out into a "most relevant" status". Also, since "has it been updated since the most recent IETF meeting" is a factor in v6ops, you'll find that considered.

At this point, I have four questions for the working group:
   For draft-ietf-v6ops-transition-comparison, any comments on progress/status? (The authors would like to wait until October 30 before making a decision, pending other tests)
   For draft-ietf-v6ops-ipv6-deployment, any comments on progress/status? (On April 7, Guiseppe sent a note to the list asking for more comments)
   For draft-horley-v6ops-expand-doc, What is the working group;'s opinion? The chairs think it is in a state conducive to adoption.
   For draft-vasilenko-v6ops-ipv6-oversized-analysis, where do we go? At this moment, I'm thinking it could be presented at discussed at IETF 111.

Per https://datatracker.ietf.org/meeting/111/important-dates/, we are on the clock for IETF 111. Register...


> On May 20, 2021, at 12:25 AM, IETF Meeting Session Request Tool <[e-mail]> wrote:
> 
> 
> 
> An update to a meeting session request has just been submitted by Fred Baker, a Chair of the v6ops working group.
> 
> 
> ---------------------------------------------------------
> Working Group Name: IPv6 Operations
> Area Name: Operations and Management Area
> Session Requester: Fred Baker
> 
> 
> Number of Sessions: 1
> Length of Session(s):  1 Hour
> Number of Attendees: 100
> Conflicts to Avoid:
> Chair Conflict: spring lsr 6man intarea idr bess tsvwg
> 
> Key Participant Conflict: rtgwg panrg grow
> 
> 
> 
> 
> 
> People who must be present:
>  Fred Baker
>  Ron Bonica
>  Warren &quot;Ace&quot; Kumari
> 
> Resources Requested:
> 
> Special Requests:
> 
> ---------------------------------------------------------