Regarding http://tools.ietf.org/html/draft-agl-tls-padding-03#section-3, which
makes the same requirements on padding that the current draft does:
that is, must be zero, no requirements to enforce this at the receiver
(though servers MAY validate this, which is as effective as a MUST in
ensuring compliance). I hold that Adam and the numerous reviewers of
this draft from the TLS community collectively know more about this
than I could ever hope to, and suggest that we defer to their
collective judgment.
I would like to close issue #602 with the single change included in
the following PR:
Received on Tuesday, 23 September 2014 16:44:12 UTC