Re: [TLS] Revised TLS Charter

[Sean Turner <[e-mail]>]

On 5/20/11 3:42 AM, Brian Smith wrote:
> Joe Salowey wrote:
>> [Joe] Our security AD has requested that we tighten up the charter
>> such that significant changes to the protocol require a charter
>> update. We can certainly discuss the topics you raise without a
>> charter update. It may be possible to publish documents for some of
>> the things you want without a charter update. For other things, in
>> particular things that require significant change to the TLS state
>> machine or other aspects of the protocol we are going to have to go
>> through the process of updating the charter. This does not have to be
>> a heavyweight process, but it does require more review than just
>> adding a working group milestone. Since TLS is in widespread use in
>> all areas of the IETF this ensures there is some cross area review
>> before we initiate the work for a major change
>
> In the next couple of weeks, I could work on getting some drafts of extensions (and/or resurrect some old ones) that I would like to be considered on the standards track, which we (Mozilla and others) are likely to implement and deploy soon. At least two of these extensions do affect the state machine and most of the changes have already been discussed at length in the working group. I think this would be useful input for the decision of what to include in the initial revision of the charter, and would probably prevent some unnecessary future debates about it.

I wanted to give everybody a heads up that I put the charter text Joe 
sent around on the telechat for tomorrow.  The current charter is really 
out of date and needs to be updated ASAP.

If the WG decides to adopt the items suggested by Brian then we can 
update the charter again (some WGs update their charters every time they 
finish a certain a draft).  Getting a charter through the IESG is not 
necessarily hard.  It can happen in a short time (like two weeks).  How 
long it takes to agree on the text to submit to the IESG is anybody's guess.

spt