Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/IETFreports/2009/ietf76.pdf Дата изменения: Tue Nov 10 08:05:35 2009 Дата индексирования: Tue Sep 14 16:09:15 2010 Кодировка:

November 2009

RFC Editor Report
76th IETF Meeting Hiroshima, Japan

IETF 76

RFC Editor

1


IETF 76

RFC Editor Office Hours
Monday - Wednesday 9:30 - 4:30

Sunday Tutorial Session Participation
RFC Editor Tutorial

Acacia West 1:00 - 2:50
IETF 76
RFC Editor

2


Copyright Transition

Independent & IRTF Streams still stuck


draft-braden-independent-submission drafted to describe the incoming and outgoing rights desired for the Independent stream
30-day last call expired 14 October 2009





Aaron Falk has updated draft-irtf-rfcs to describe the incoming and outgoing rights requested IRTF documents The Trust issued request for comments on proposed TLP changes Uncertainty about language for code

http://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=934&k2=7109&tid=1257193753



IETF 76

RFC Editor

3


Stream Info in Indices



Stream information added to XML and HTML indices.
http://www.rfc-editor.org/rfc-index.html http://www.rfc-editor.org/rfc-index2.html ftp://ftp.rfc-editor.org/in-notes/rfc-index.xml ftp://ftp.rfc-editor.org/in-notes/rfc-index.xsd



Also available from metatdata pages
http://www.rfc-editor.org/info/rfc4346


Stream is as defined in RFC 4844, or marked as Legacy (stream info not recorded) IETF stream RFCs are listed with area and WG
RFC Editor

IETF 76

4


AUTH48 Pages

Created to




Help publicly track author sign off Note any particulars for publication delay Track AD approval (when requested) One-stop shop for authors to see status of their document Help track sign off for clusters of documents Example: http://www.rfc-editor.org/auth48/rfc5661 Are linked to from queue page and individual cluster pages http://www.rfc-editor.org/queue2.html http://www.rfc-editor.org/cluster_info.php?cid=C23

IETF 76

RFC Editor

5


4-Month Summary
1 July - 31 October 2009

Since IETF 75 IETF WG IETF Non-WG IAB IRTF Independent
IETF 76

Submissions 108 80 19 2 2 5
RFC Editor

Publications 104~3077 86 17 1 0 0

pgs

6


Current Queue Breakdown
as of 31 2009
Median Wks in Q

Current Q EDIT RFC-EDITOR AUTH48 AUTH IANA REF MISSREF TO IESG ISR ISR-AUTH TOTAL

IETF 10 11 25 1 1 6 27 1

IETF Non-WG 4 3

IAB

IRTF

Independent 1 2

Total 11 17 52 1 1 6

.7 .3 3.4

2

22

2

1

6 1 25 4

36 1 1 25 4 155

82

9

3

6

55

IETF 76

RFC Editor

7


Publication Rate

~4-Month Submitted/ Period Month Mar - Jun07 40.5 Jul - Oct07 21.25 Nov07 - Feb08 20 Mar - Jun08 26.75 Jul - Oct08 25.5 Nov08 - Feb09 25 Mar - Jun09 28.7 Jul - Oct09 28
IETF 76

Published/ Month 26.25 35.25 25.5 23.25 28.25 14.75 30 24
RFC Editor

Reported @ IETF IETF IETF IETF IETF IETF IETF IETF 69 70 71 72 73 74 75 76
8


Annual Publication Rate

2004: 281 2005: 327 2006: 459 2007: 320 2008: 290 YTD: 260

IETF 76

RFC Editor

9


Annual Pub & Errata Rate

Shows distinct RFCs with Technical Errata Note: "Technical" label is not necessarily accurate.

IETF 76

RFC Editor

10


More Information

Web site: http://www.rfc-editor.org/ RFC Editor reports and statistics are
available at:


http://www.rfc-editor.org/RFCeditor.html

IETF 76

RFC Editor

11


Contact Us



Send us Email: rfc-editor@rfc-editor.org Interest list: rfc-interest@rfc-editor.org
This list was created to facilitate community discussion on the RFC series
and to make suggestions about RFC Editor functions. The RFC Editor hopes that this mailing list will provide a focal point for input, information, and discussion about the details of the RFC process, as well as an archive to avoid the continual re-hashing of some issues. Topics appropriate to this list may include formatting, tools, style, content, and indexing aspects of the RFC series. It will not be used for discussion of the IETF standards process, general IETF organizational issues, or issues for which the NOTE WELL admonition is needed for IPR reasons. The posting policy is subscriber-only to reduce spam. It will initially be unmoderated, but the RFC Editor will cut off any discussions that are inappropriate according to the guidelines above.

IETF 76

RFC Editor

12