Hrm this is confusing. If 'answers' that do not attempt to answer the question are OK, and we shouldn't use 'not an answer' for this - as this answer seems to suggest -it sounds like "not an answer" isn't the correct name for this flag. I've just had my own account temporarily suspended for marking answers that weren't attempting to answer the question as 'not an answer' too frequently, which is a somewhat unpleasant reaction to trying to keep SO clear of people 'answering' questions with non-answers.

Thanks @JuanM! I just hit 100K, so I guess I can wait a little longer and some swag will come?

@JourneymanGeek a challenge coin would be lovely - easy to ship, beautiful and those of us who feel proud can have it framed. 🙂

Site no longer exists.

Formatting at 72 characters breaks anything wider or narrower than 72 characters. And what @kevin said.

@BilltheLizard 1. The answer was not 'link only' - in the screenshot above you can clearly see that it mentions a) there is a draft RFC b) the name of the draft RFC both of which are relevant answers to my question. 2. The question 'is there a standard for PEM encoding' is separate from 'Where is the PEM file format specified?' since the PEM file format does not include headers as already mentioned in the discussion 3. You're more than welcome to attempt to delete all questions around RFC standards from Stack Overflow. Good luck.

@BilltheLizard my question was 'is there a standard'. The essential parts of any answer is a) is there is a standard b) what that standard is. Saying 'yes, there is this RFC, here is a link' completely satisfies that. Internet RFCs are not transient like blog articles.