RFC SERIES OVERSIGHT COMMITTEE (RSOC)
April 12, 2018 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES
---------------------------------
- Nevil Brownlee
- Heather Flanagan (RSE, non-voting)
- Joel Halpern
- Bob Hinden
- Cindy Morgan (Scribe, non-voting)
- Adam Roach
- Robert Sparks (Lead) 
- Martin Thomson
- Portia Wenze-Danley 

REGRETS
---------------------------------
- Sarah Banks (Chair) 
- Tony Hansen 

MINUTES
---------------------------------

0. Review of minutes

  The minutes of the 22 March 2018 meeting were approved.

1. Format work update

  Heather Flanagan reported that the RPC is currently testing the 
  xmldiff tool. 

  The v3 to text formatter is expected to be done within the next couple 
  of weeks; once it is available, it will allow the RPC to start 
  seriously putting v3 through its paces. 

2. Style Guide update

  Heather Flanagan reported that a revised draft of the style guide was 
  posted earlier this month. 

  Adam Roach has posted draft-roach-id-cite, which would update the 
  "Work in Progress" text in RFC 2026. That document will likely be 
  progressed as an AD-sponsored document on the IETF stream.


3. Protocol actions and standards documents

  Heather Flanagan reported that there are two experimental BIER RFCs 
  that the IESG recently approved moving to Proposed Standard. The 
  current practice for status changes is that a Protocol Action 
  announcement is sent and the metadata changed, but the text of the 
  document does not. However, there is different boilerplate text for 
  Standard-Track documents, which has led to confusion in the past. 

  Adam Roach noted that the IESG is also having a larger discussion 
  about how our tooling represents such changes.

  The RFC Editor proposes that for future documents, the RPC will create 
  a -bis document (assuming the only change is to the boilerplate). 
  However, that leaves open questions about what the AUTH48 process 
  would be, who would be the approver, and whether there are any legal 
  considerations in changing the boilerplate. Robert Sparks added that 
  there may be cases where an author's affiliation changed between the 
  original RFC publication and the new RFC publication.

  The IESG and IAB will discuss this further at their retreat later this 
  month. Heather Flanagan will dial in to the meeting to participate in 
  the conversation.

4. GitHub Experiment

  Heather Flanagan reported that discussions about piloting a GitHub-
  based workflow for the TLS 1.3 and JSEP documents are ongoing. She is 
  in the process of writing a proposal that will clearly outline what 
  the process would be for the RPC. Adam Roach and Martin Thomson agreed 
  to work with Heather to further refine that proposal.

5. IETF-IEEE Data Usage License

  Heather Flanagan reported that she sent comments to IEEE about the 
  Data Usage License and is waiting for a response.

6. GDPR Statement

  Heather Flanagan reported that she sent a draft of the RFC Editor's 
  statement on GDPR to Portia Wenze-Danley, who will forward it on to 
  legal counsel for review.