Re: [TLS] [tls13-spec] expand MTI Extensions and add more strict requirements (#232)

"Salz, Rich" <rsalz@akamai.com> Fri, 28 August 2015 15:08 UTC

From: "Salz, Rich" <rsalz@akamai.com>
To: "tls@ietf.org" <tls@ietf.org>
Thread-Topic: [tls13-spec] expand MTI Extensions and add more strict requirements (#232)
Thread-Index: AQHQ4Q8euOk3t0CCHUSpRsz8/mu4CZ4guImAgADLRrA=
Date: Fri, 28 Aug 2015 15:08:35 +0000
Message-ID: <6a08cc2038f749f8b94da7a09991c446@ustx2ex-dag1mb2.msg.corp.akamai.com>
References: <tlswg/tls13-spec/pull/232@github.com> <tlswg/tls13-spec/pull/232/r38151265@github.com>
In-Reply-To: <tlswg/tls13-spec/pull/232/r38151265@github.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/tDGJGYacoD3lf-8TNmOUbuQzqbY>
Subject: Re: [TLS] [tls13-spec] expand MTI Extensions and add more strict requirements (#232)
Precedence: list

Having discussions through github is a really bad idea.  Mail formatting can get even more mangled, and we lose the IETF mail archive and participation.  I think we need to be more diligent and avoid doing that.

> There's just no statement of what to do when it's required and not given.

That's not necessarily a problem.  The behavior of the other party need not be strictly defined.  It can send an alert or continue along as best as it wants.  Merely describing what must be done is enough.  Very few specs fully mandate what must be done if all the requirements are not met; I think XML was the first widespread Internet one to do so.

	/r$

--  
Senior Architect, Akamai Technologies
IM: richsalz@jabber.at Twitter: RichSalz

Re: [TLS] [tls13-spec] expand MTI Extensions and … Salz, Rich