Skip to main content

2017-07-20-rsoc-minutes
slides-interim-2022-rfcedprog-07-sessa-2017-07-20-rsoc-minutes-00

Meeting Slides RFC Series Oversight Committee (RSOC) (rfcedprog) IAB ASG
Date and time 2022-01-01 15:00
Title 2017-07-20-rsoc-minutes
State Active
Other versions plain text
Last updated 2022-06-10

slides-interim-2022-rfcedprog-07-sessa-2017-07-20-rsoc-minutes-00
RFC SERIES OVERSIGHT COMMITTEE (RSOC)
July 20, 2017 RSOC Meeting

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES
---------------------------------
Sarah Banks (Chair)
Nevil Brownlee
Heather Flanagan (RSE, non-voting)
Joel Halpern
Tony Hansen (remote) 
Bob Hinden
Cindy Morgan (Scribe, non-voting)
Ray Pelletier (IAOC Liaison, non-voting)
Adam Roach
Robert Sparks (Lead)
Martin Thomson


NOTES
---------------------------------

1. Approval of Minutes

  The minutes of the 12 June 2017 RSOC Meeting were approved.


2. Agenda bash

  An item on using HTTPS in citations was added to the agenda.


3. RPC SLA

  Heather Flanagan reported that the RPC met the SLA at Tier 2 for Q2 
  2017. Robert Sparks observed that it might be helpful for newer 
  members of RSOC to have a walkthrough of how the SLA works at a future 
  RSOC meeting. Heather agreed, and also said that she would send out an 
  explanation of the SLA to the mailing list.


4. Projects

4.1. Format

  Heather Flanagan reported that the id2xml tool that converts the text 
  of RFCs and I-Ds to XMLv2 files is currently in use but could use more 
  testing. The xml2rfc v2 to v3 converter is currently being tested.

  Tony Hansen will update https://xml2rfc.tools.ietf.org/
  experimental.html to direct bug reports to the mailing list.

4.2. Non-ASCII doc publication

  Heather Flanagan reported that the RPC is testing drafts with non-
  ASCII characters to see where the existing tool chain fails. Testing 
  has shown that updates will be required for the RFC Editor database 
  (Latin-1 to utf8mb4) and associated scripts. The scripts 
  converting .nroff to .txt and .txt to .pdf would also need to be 
  updated; after a brief discussion the RSOC agreed that updating those 
  scripts now (before v3 is published) is not worth it; for the test 
  documents, the RPC can use nroff as is an manually fix any characters 
  that break. Special instructions would be given to the authors to 
  check this carefully in AUTH48.

  Heather Flanagan will check with the IETF Trust about whether not 
  generating PDFs with the tools will be a problem for these test 
  documents. 

  The SVG checker is expected to be released for testing before IETF 
  100.

  Bob Hinden asked when authors will be able to start using the new 
  toolsets. Heather Flanagan replied that the v3 toolsets are expected 
  to be in production at the middle of next year.


5. RPC Programmer update

  Heather Flanagan reported that the RPC programmer has set up the v3 
  test page and made various internal updates and bug fixes. Future 
  projects include v3 errata updates, database updates for non-ASCII 
  characters, and working on the RFC 10K issue.

  Robert Sparks noted that getting the RPC code base into the public 
  repository has been tracked informally, and asked that this be added 
  to the project list. Robert suggested that the Taint extension for PHP 
  could help fix some of the form insertion attacks. Heather will follow 
  up with the programmer about this.

6. IRTF open access journal possibilities

  Heather Flanagan reported that she met with Allison Mankin (IRTF 
  Chair) to discuss IRTF publications outside of the RFC Series. The 
  IRTF is considering starting an academic journal. Heather noted that 
  such a journal would be outside the scope of work for the RPC; RSOC 
  suggested that this topic be added to a future IAB agenda in order to 
  get more information.

7. IESG author statement

  The IESG is considering a statement on the number of authors allowed 
  in an RFC. Some of the proposed changes would impact RPC tools. 
  Heather Flanagan noted that the proposed statement is expected to go 
  out for community comment; the RSOC agreed to note the impact on the 
  RFC tools during the comment period.

8. Use of HTTPS in RFC References

  Bob Hinden asked about the status of using HTTPS in RFC references. 
  Heather Flanagan replied that the citation libraries need to be 
  updated to use HTTPS instead of HTTP. The citation libraries also need 
  to be updated for a handful of other things.