Hiya,

On 14/02/2019 19:26, Salz, Rich wrote:
>> That just says you can't report it as successful.
> 
> "MUST NOT surface" seems like bad phrasing then.
> 
> 
>   *   I'm blanking on better wording. I wanted to keep the wording 
> independent of whether your TLS stack knows how to open transport connections 
> or not, which changes things a bunch, which constrained things a bit. Any 
> thoughts?
> 
> Represent instead of surface?

I'd be fine if the PR wasn't fully wordsmithed, e.g. I've often
written drafts that have text like "[[this needs more right,
"surface" isn't quite right]]" - there will, after all, be a -04
and so on when we can fix that.

Cheers,
S.




Attachment: 0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to