See today's thread on gen-art about this.

The answer to:

Why aren't per-directory well-known locations defined?

Given in Appendix A could be moved into Section 3.

  Allowing every URI path segment to have a well-known location
  (e.g., "/images/.well-known/") would increase the risks of

https://github.com/martinthomson/i-d-template/blob/master/v3.css selects the "Cabin Condensed" font for section titles. I find the narrow letters hard to read and would prefer a normal width font instead.

The current RFC for misp-core-format has two different timstamp formatings:

1. unix timestamp format as string value (REF: #3)
2. date as YYYY-MM-DD

To conform with standard API marshaling and unmarshaling the timestamps should all be formated conform with RFC 3339 (https://tools.ietf.org/html/rfc3339)

Currently, the tool will fail to run from the command-line in Windows.

This is because the command-line functionality is based on shebangs, which do not work on Windows

#!/usr/bin/env python3

RFC8392 doesn't say whether the URI tag #6.32 should or should not be used on the issuer, subject and audience claims. Without it the decoder would use a URI syntax matcher to decide between it being text or a URI.

The VP9 RTP payload format draft needs examples of VP9 RTP streams.

See section 4.6 of the VP8 RTP payload format (RFC 7741) for the sort of thing we're looking for.

We have

If an RStream is reset,
endpoints MUST reset the XStreams associated with that RStream. If the
RStream is closed, endpoints SHOULD allow the existing XStreams to complete
normally. The RStream SHOULD remain open while communication is ongoing.
Endpoints SHOULD refresh any timeout on the RStream while its associated
XStreams are open.

Along with some later text pu