Skip to content

A simple python tool to identify the contributions to RFCs for any IETF participant

License

Notifications You must be signed in to change notification settings

martinduke/count-rfcs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 
 
 
 
 

Repository files navigation

count-rfcs

A simple python tool to identify the contributions to RFCs for any IETF participant. It currently classifies RFCs in the following categories, in declining order of priority:

  • Listed as author

  • Document Shepherd

  • Responsible AD

  • Acknowledged somewhere in the text

  • Submitted an IESG ballot that contained text (COMMENT or DISCUSS)

  • Any document where the attempt to retrieve from the rfc-editor or datatracker failed for some reason.

Change the parameters in the first code block, then just type

python3 count-rfcs.py

to run it.

These parameters also affect the speed at which things run. Every RFC that is not discarded due to being the wrong status, date, or area takes about 1 second to process, so if there are no filters whatsoever 10,000 RFC's will take ~3 hours.

Parameters:

  • name: how the name would appear in the datatracker, or in an acknowledgements section (usually '[first name] [last name]')

  • include_informational, include_experimental: set to False if you don't care about documents with this status

  • include_acknowledgments: if True, the script will download and search the document itself to find your name

  • first_year: the first year an RFC might have been published that the person affected (set to 1969 or earlier to disable)

  • first_rfc: the earliest RFC number the person might have affected (set to 0000 to disable)

  • last_rfc: skip over all RFC numbers beyond this (mostly useful for debugging)

  • first_ad_year: the first year someone was an AD; before that year, the tool does not check if the person balloted on a draft. To disable, set it to a future year. Also, after first_ad_year the script ignores any limits on area, stream, or wg. Prior to first_ad_year, the script will process an RFC that matches ANY of the three lists below:

  • streams: before first_ad_year, the tool will check any RFC from this stream

  • areas: before first_ad_year, the tool will check any RFC from the areas listed here

  • wgs: before first_ad_year, the tool will check any RFC from wgs listed here. 'NON' is a reserved word for non-working-group IETF stream documents; 'IESG' is a reserved word too

About

A simple python tool to identify the contributions to RFCs for any IETF participant

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages