update error response as an object or as a string

[fimbault]

Closes #79

This issue also checks all errors :

• in section 1 : when referring to errors, it is a generic term / no change needed
• same in the security considerations
• elsewhere we aim to have specific errors

[netlify]

✅ Deploy Preview for gnap-core-protocol-editors-draft ready!

Name	Link
🔨 Latest commit	4dff4ed
🔍 Latest deploy log	https://app.netlify.com/sites/gnap-core-protocol-editors-draft/deploys/635696366992370008c806cf
😎 Deploy Preview	https://deploy-preview-452--gnap-core-protocol-editors-draft.netlify.app/draft-ietf-gnap-core-protocol
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[fimbault]

This doesn't build, will look at that tomorrow

[jricher]

@fimbault : the build errors are due to the IANA section anchors being changed: you have a reference to the (old) IANA-error-response-template which should now be IANA-error-code-template, and you need to update the anchor for IANA-error-response-contents to IANA-error-code-contents. I only see those two but do a text search on those anchors.

[fimbault]

thanks @jricher for the hint, i'll fix that

[jricher]

There were a number of places where the error is displayed to the user instead of returned from the AS in a message, so in those places error codes aren't needed/used. I've backed those out and will merge them. Those error codes can probably be marked as being returned from the AS in the post interaction stage though, so we might want to put more text there.