RFC Editor Report IETF 90 Toronto

RFC Editor at IETF 90

� Office Hours RPC: Mon - Thu RSE: Mon & Wed ISE: Tue & Thur http://www.rfc-editor.org/ietf.html

� RFC Format Session 13:00 – 14:00 (Ballroom)

7/19/14 IETF 90 2

Annual Subs & Pubs

7/19/14 IETF 90 3

0

50

100

150

200

250

300

350

400

450

500

2005 2006 2007 2008 2009 2010 2011 2012 17-Jul

Subs

Pubs

Monthly Queue

7/19/14 IETF 90 4

Jan – 18 Jul 2014 Subs Pubs

IETF 150 164

IETF non-wg 27 31

IAB 5 5

IRTF 2 4

Independent 16 13

0

10

20

30

40

50

60

70

80

Jan

Feb

Mar

Apr

May

June

Jul

Aug

Sep

t

Oct

Nov

Dec

Jan

Feb

Mar

Apr

May

June

18-J

ul

Aug

Sep

t

Oct

Nov

Dec

2013 2014

Submitted

Moved to EDIT

Published

Queue Movement

7/19/14 IETF 90 5

0

20

40

60

80

100

120

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Jan

Feb

Mar

Apr

May

Jun

18-J

ul

Aug

Sep

Oct

Nov

Dec

2013 2014

Doc

Cou

nt

# of Docs in Primary Processing States

AUTH48-DONE

AUTH48

RFC-EDITOR

EDIT

RPC PROCESSING TIMES

7/19/14 IETF 90 6

Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun 18-Jul

93% 91% 82% 73% 88% 63% 60% 36% 17% 5% 2% 46%

14 21 14 22 15 15 12 8 7 2 1 11

15 23 17 30 17 24 20 22 41 43 43 24

15 31 26 15 23 46 48 21 26 20 34 6

33 27 20 34 51 67 36 32 32 21 33 13

5.3 5.5 5.1 6 5.9 6.1 6.1 7.1 9.7 10 11 8.2

12mo Avg

Met SLA Target (67% RET or better) 42%

2013 2014

% of docs pub <= 6 wks 55%

# of docs pub <=6 wks 12

total # of docs pub 27

total # of docs entering EDIT 33

total # of docs sub 26

67th percentile (wks) 7.2

Total Errata over 8 IETFs

7/19/14 IETF 90 7 as of 2014-07-16

387 212 183 163 88 72 88 80

1372 1474 1515 1578 1731 1767 1819 1891

295 338 358 378 406 423 437 481

1033 1193 1264

1307 1370 1416

1444 1474

0

500

1000

1500

2000

2500

3000

3500

4000

4500

IETF 83 IETF 84 IETF 85 IETF 86 IETF 87 IETF 88 IETF 89 IETF 90

Num

ber

of E

rrat

a

Total Errata (by Status)

Held Rejected

Verified Reported

Reported Errata by Source of RFC

7/19/14 IETF 90 8

as of 2014-02-26

3 9

1

9

24

28

2

Reported Errata by Source of the RFC

app (1)

gen (3)

int (9)

ops (8)

rai (1)

rtg (9)

sec (24)

tsv (28)

Independent (2)

IAB (2)

IRTF (0)

IETF 89

3

1

7 2

32

26

5

Reported Errata by Source of the RFC

app (0)

gen (3)

int (1)

ops (1)

rai (7)

rtg (2)

sec (32)

tsv (26)

Independent (5)

IAB (1)

IRTF (0)

IETF 90

as of 2014-07-16

What’s New �  Updated Official Internet Protocol Standards page

http://www.rfc-editor.org/search/standards.php

�  Upgraded the hardware and software used by the RFC Editor's website and RFC repository.  New hardware with additional computing resources, a new operating system version, and new software versions were all included in the comprehensive upgrade.  These upgrades will provide better security, faster processing, and increased storage, to support the future growth of the RFC Editor and related services.

7/19/14 IETF 90 9

RFC Format �  Progress since IETF 89

�  Tools Development Team working on the various SoWs required for the tools

�  Design Team continues to work on the requirements and descriptions

�  List of the latest drafts can be found on the Format FAQ �  http://www.rfc-editor.org/rse/FormatFAQ.html

RFC Format Session = Tuesday, 22 July 2014 @ 13:00-14:00, Ballroom C

Timeline �  July 2014 – October 2014

�  Team to finish drafts to the point that coding can start against the requirements �  Drafts to remain as drafts pending discoveries during the

coding effort

�  SoWs to be posted as a group for community comment

�  October 2014 – December 2015 �  RFPs, programming, QA, draft updates, more QA,

tutorials and training, more QA, go-live

Style Guide �  RFC-to-be 7322

�  Significant changes include: �  Update to reference structure, esp. I-Ds

�  Web component of the Style Guide to capture tentative and experimental guidance

�  Table of Contents is required and will be added by RFC Editor if not present in the approved I-D

�  Guidance regarding Acknowledgements, Contributors, and Authors is clarified

Digital Object Identifiers (DOIs) �  IAB approved starting the assignment of Digital

Object Identifier (DOI) [ISO 26324] to RFCs �  Both past and future RFCs – not I-Ds �  A DOI might look like: 10.123456/rfc1234

�  Tools Development Team is wrapping up the draft for the SoW for the project; expect that to go out for community comment soon

�  The draft describing how DOIs will be handled will be updated as we learn more �  https://datatracker.ietf.org/doc/draft-iab-doi/

RSE Avenues of Communication �  The RSE wiki

�  http://www.rfc-editor.org/rse/wiki

�  rfc-interest mailing list �  http://www.rfc-editor.org/mailman/listinfo/rfc-

interest

�  RFC Series Oversight Committee (RSOC) �  http://www.iab.org/activities/programs/rfc-editor-

program/