On 26/02/15 15:37, Stephen Kent wrote:
I disagree with this proposed resolution of the issue.
RFC 5246 says of the syntax:
... The following very basic and somewhat casually
defined presentation syntax will be used. The syntax draws from
several sources in its structure. Although it resembles the
programming language "C" in its syntax and XDR [XDR] in both its
syntax and intent, it would be risky to draw too many parallels. *The**
** purpose of this presentation language is to document TLS only; it has**
** no general application beyond that particular goal.*
Thus use of this syntax in an X.509 cert extension is contrary to the
spirit of 5246.
If that was the intended spirit, why didn't the 5246 authors write this
instead:
"; it MUST NOT be used beyond that particular goal."
?
Steve
#34: use of RFC 5246 syntax to define the SCT
Changes ([email protected]):
* status: new => closed
* resolution: => wontfix
Comment:
TLS extensions are defined using RFC 5246 format, so clearly it is correct
to use that format for the TLS extension.
There is no compelling reason to have multiple SCT formats, and good
reasons to not do so (complexity, extra signing overhead).
So, closing this ticket without changing the format.
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online
Office Tel: +44.(0)1274.730505
Office Fax: +44.(0)1274.730909
www.comodo.com
COMODO CA Limited, Registered in England No. 04058690
Registered Office:
3rd Floor, 26 Office Village, Exchange Quay,
Trafford Road, Salford, Manchester M5 3EQ
This e-mail and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
sender by replying to the e-mail containing this attachment. Replies to
this email may be monitored by COMODO for operational or business
reasons. Whilst every endeavour is taken to ensure that e-mails are free
from viruses, no liability can be accepted and the recipient is
requested to use their own virus checking software.
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
