#168: Section 4.1 Reserved Header Parameter Names Changes (by [email protected]):
* status: new => closed * resolution: => fixed Old description: > A. s/Reserved/Registered/ > > * FIXED > > B. Short names and short values belongs in the introduction and not here. > This is going to be something that needs to be used everywhere. It also > belongs in the registry evaluation guide. > > * FIXED > > C. There should be a description of why the usage is compatible between > specifications - also needs to have some guidance for experts > > D. All of paragraph 2 belongs in the registry guidelines and most of it > does not belong here. New description: A. s/Reserved/Registered/ * FIXED B. Short names and short values belongs in the introduction and not here. This is going to be something that needs to be used everywhere. It also belongs in the registry evaluation guide. * FIXED C. There should be a description of why the usage is compatible between specifications - also needs to have some guidance for experts * WON'T FIX D. All of paragraph 2 belongs in the registry guidelines and most of it does not belong here. * WON'T FIX -- -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- [email protected] | [email protected] Type: defect | Status: closed Priority: Editorial | Milestone: Component: json-web- | Version: encryption | Resolution: fixed Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/168#comment:2> jose <http://tools.ietf.org/jose/> _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
