BK21 Security Deadlines

Site: https://snp-labs.github.io/deadlines/

This repository maintains a GitHub Pages deadline tracker for security, privacy, crypto, and selected distributed systems conferences.

It is based on sec-deadlines, with additional filtering and tagging for:

• BK21플러스 IF (2018) >= 1
• Distributed Systems entries that overlap the BK21 list
• manually maintained conferences that do not exist in upstream sec-deadlines

Data sources:

• upstream sec-deadlines: https://github.com/sec-deadlines/sec-deadlines.github.io
• BK21 CSV gist: https://gist.github.com/Pusnow/6eb933355b5cb8d31ef1abcb3c3e1206

The generated site data lives in _data/conferences.yml. Do not edit that file by hand unless you intentionally want to bypass the sync pipeline.

Based on ai-deadlines by @abshkdz

Is my entry in scope?

This page is meant to host academic conference or workshop deadlines.

To check if an entry is a good fit for this page, in general, I would check for the following:

• Is there a "Call For Papers"? Is there a link for submissions? Are there formatting guidelines (page limits, style guide) etc?
• Is security, privacy, or cryptography mentioned in the list of topics?
• Is there a review process? Does the website name a general chair, program chair, or program committee?
• If accepted, will the paper be published in a proceedings?

If "Yes" to all of the above, then the conference or workshop is likely a good fit. Examples where conferences were not a good fit are FTC's PrivacyCon (see sec-deadlines/#246) and Real World Crypto (RWC) (see sec-deadlines/#475). Once PrivacyCon or RWC begin publishing proceedings, they'd become fit for inclusion.

How This Fork Works

_data/conferences.yml is rebuilt from:

• sec-deadlines/sec-deadlines.github.io upstream conference data
• the Pusnow gist: https://gist.github.com/Pusnow/6eb933355b5cb8d31ef1abcb3c3e1206
• the condition BK21플러스 IF (2018) >= 1

If you enable that workflow, this repository will periodically read the gist URL above and the upstream sec-deadlines data, then regenerate _data/conferences.yml. Treat _data/conferences.yml as generated output and update scripts/sync_conferences.py instead of editing the file by hand. Entries that do not exist in upstream sec-deadlines can be maintained in _data/manual_conferences.yml; the sync script merges them into the generated output.

Current site-level filters and tags:

• topic tags: SEC, PRIV, CRYPTO, DIST
• BK21 score tags: BK21-4, BK21-3, BK21-2, BK21-1

Adding/Updating Conferences

• Read the data format description below. Note that the timezone format sign is inverted (e.g., UTC+7 is written as Etc/GMT-7). It's not a bug. I hate this format too. I'd be happy to move to a different timezone JavaScript library that uses a friendlier format, but I don't have time for that.
• If the conference already exists in upstream sec-deadlines, update the sync logic or wait for upstream changes.
• If the conference does not exist in upstream sec-deadlines, add it to _data/manual_conferences.yml.
• Regenerate _data/conferences.yml by running python3 scripts/sync_conferences.py.
• Please check if an entry for a prior year's offering exists; if so, please update the prior entry, rather than adding a new one.
• Commit and push the result

Conference entry record

Example record:

- name: Euro S&P
  description: IEEE European Symposium on Security and Privacy
  year: 2018
  link: http://www.ieee-security.org/TC/EuroSP2018/
  dblp: https://dblp.org/db/conf/eurosp/index.html
  deadline: ["2017-08-15 23:59"] # must be a list
  date: April 24-26
  place: London, UK
  tags: [SEC, PRIV]

Descriptions of the fields:

Field name	Description
name*	Short conference name, without year
year*	Year the conference is happening
description	Description, or long name
comment	Additional comments, e.g., co-located conference, rolling deadline
link*	URL to the conference home page
dblp	URL to the DBLP page of the conference
deadline*	A list of deadlines. (Gory details below)
timezone	Timezone in tz format. By default is UTC-12 (AoE)
date	When the conference is happening
place	Where the conference is happening
tags	One or multiple tags such as SEC, PRIV, CRYPTO, DIST, CONF, SHOP, BK21-4, BK21-3, BK21-2, BK21-1

Fields marked with asterisk (*) are required.

Deadline format

The deadline field can contain:

1. The simplest option: a date and time in ISO format. Example: ["2017-08-19 23:59"] (Note that you need to wrap even a single deadline in a list).
2. If a deadline is rolling, you can use a template date, just substitute the year with %y and the year before the conference with %Y. Example: ["%y-01-15 23:59"] means there is a deadline on the 15th January in the same year as the conference.
3. A list of (1) or (2). Example of two rolling deadlines, with one in the end of October in the year prior to the conference year, and the second in the end of February in the same year as the conference:

- "%Y-10-31 23:59"
- "%y-02-28 23:59"

On the page, all deadlines are displayed in viewer's local time (that's a feature).

Note: If the deadline hour is {h}:00, it will be automatically translated into {h-1}:59:59 to avoid pain and confusion when it happens to be midnight in local time.

Timezones

The timezone is specified in tz format. Unlike abbreviations (e.g. EST), these are un-ambiguous. Here are tz codes for some common timezones:

Common name	tz
UTC	Etc/UTC
America Pacific Time	America/Los_Angeles
Pacific Standard Time (UTC-8)	Etc/GMT+8 (Yes, the sign is inverted for some weird reason)
America Eastern Time	America/New_York
Eastern Standard Time (UTC-5)	Etc/GMT+5
American Samoa Time (UTC-11)	Pacific/Samoa or Etc/GMT+11. This timezone does not use DST.
Aleutian Islands	America/Adak