Below a few late comments..
6. Serializing Origins
- It really really seems that the two algorithms need to be swapped (the
first one converts to ASCII, but the second does not).
- Also, I'd prefer a declarative definition.
7. The HTTP Origin header
- header *field*
- the syntax doesn't allow multiple header fields, and the prose says
clients MUST NOT generate them; what is the recipient supposed to do
when it get's multiple instances anyway? Is the default approach
(ignoring them all) good enough? Do we need to warn recipients so that
they check?
11. References
- the WEBSOCKETS reference should be updated (if a new draft is produced)
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf