Mark Nottingham

OK, trying that - thx

This is where I ended up: ~~~ Makefile clean:: -rm -f .*.http-lint.txt lint:: http-lint rfc-http-validate ?= rfc-http-validate .SECONDARY: $(drafts_xml) .PHONY: http-lint http-lint: http-lint-install $(addsuffix .http-lint.txt,$(addprefix .,$(drafts))) .PHONY: .%.http-lint.txt .%.http-lint.txt: %.xml...

Don't get too hung up on the high-level semantic categories of responses. While one could argue that 101 is more appropriately cast as a final response (e.g., 2xx), there are...

## Fastly - [docs](https://docs.fastly.com/en/guides/working-with-surrogate-keys) - 1024 bytes for each group label - 16,384 max bytes for whole header ## Cloudflare - [docs](https://developers.cloudflare.com/cache/how-to/purge-cache/purge-by-tags/) - no max length on a label in...

Based on those limits and being conservative, we could say that an implementation should support at least 128 groups, each with a 128 character label.

Perhaps what we should do is remove revalidation, but assure that tags can be extended in a way that allows future uses like that to be safely specified.

What would it say? The semantics of repeated list items are specific to the field in question -- they might be truly separate items (the common case), or it might...

It sounds like the media type should be whatever the 'native' format is -- if there's no 'native' structured format or format-associated processing model for a dictionary, it doesn't need...

This would be a breaking change, and so is out of scope for a bis.

You're correct - it might conceivably be introduced in a new specification without breaking existing fields. However, I don't believe we should do so now, and I'll try to explain...