TLS Ticket Requests
draft-ietf-tls-ticketrequests-07
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2024-01-26
|
07 | Gunter Van de Velde | Request closed, assignment withdrawn: Carlos Martínez Last Call OPSDIR review |
2024-01-26
|
07 | Gunter Van de Velde | Closed request for Last Call review by OPSDIR with state 'Overtaken by Events': Cleaning up stale OPSDIR queue |
2021-08-10
|
07 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
2021-08-09
|
07 | (System) | RFC Editor state changed to AUTH48 |
2021-07-16
|
07 | (System) | RFC Editor state changed to RFC-EDITOR from REF |
2021-06-28
|
07 | (System) | RFC Editor state changed to REF from EDIT |
2021-06-22
|
07 | (System) | RFC Editor state changed to EDIT from MISSREF |
2021-05-03
|
07 | (System) | RFC Editor state changed to MISSREF from EDIT |
2021-05-03
|
07 | (System) | RFC Editor state changed to EDIT from MISSREF |
2021-02-11
|
07 | Tero Kivinen | Closed request for Last Call review by SECDIR with state 'Overtaken by Events' |
2021-02-11
|
07 | Tero Kivinen | Assignment of request for Last Call review by SECDIR to Phillip Hallam-Baker was marked no-response |
2021-02-05
|
07 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
2021-02-05
|
07 | (System) | IANA Action state changed to Waiting on RFC Editor from In Progress |
2021-02-05
|
07 | (System) | IANA Action state changed to In Progress from Waiting on Authors |
2021-02-04
|
07 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
2021-02-01
|
07 | (System) | RFC Editor state changed to MISSREF |
2021-02-01
|
07 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
2021-02-01
|
07 | (System) | Announcement was received by RFC Editor |
2021-02-01
|
07 | (System) | IANA Action state changed to In Progress |
2021-02-01
|
07 | Amy Vezza | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
2021-02-01
|
07 | Amy Vezza | IESG has approved the document |
2021-02-01
|
07 | Amy Vezza | Closed "Approve" ballot |
2021-02-01
|
07 | Amy Vezza | Ballot approval text was generated |
2021-01-31
|
07 | Benjamin Kaduk | IESG state changed to Approved-announcement to be sent from Approved-announcement to be sent::AD Followup |
2021-01-31
|
07 | Benjamin Kaduk | RFC Editor Note was changed |
2021-01-31
|
07 | Benjamin Kaduk | RFC Editor Note for ballot was generated |
2021-01-31
|
07 | Benjamin Kaduk | RFC Editor Note for ballot was generated |
2020-12-17
|
07 | Cindy Morgan | IESG state changed to Approved-announcement to be sent::AD Followup from IESG Evaluation |
2020-12-17
|
07 | Martin Vigoureux | [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux |
2020-12-16
|
07 | Alvaro Retana | [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana |
2020-12-16
|
07 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2020-12-16
|
07 | Robert Wilton | [Ballot comment] Thanks for this easy to read document. |
2020-12-16
|
07 | Robert Wilton | [Ballot Position Update] New position, No Objection, has been recorded for Robert Wilton |
2020-12-15
|
07 | Barry Leiba | [Ballot comment] Thanks for a very clear, well-written document. Just one very tiny comment: — Section 1.1 — Please use the exact BCP 14 boilerplate … |
2020-12-15
|
07 | Barry Leiba | [Ballot Position Update] New position, No Objection, has been recorded for Barry Leiba |
2020-12-15
|
07 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2020-12-15
|
07 | Roman Danyliw | [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw |
2020-12-15
|
07 | Magnus Westerlund | [Ballot Position Update] New position, No Objection, has been recorded for Magnus Westerlund |
2020-12-14
|
07 | Michelle Cotton | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
2020-12-14
|
07 | Michelle Cotton | IANA Experts State changed to Expert Reviews OK |
2020-12-13
|
07 | Éric Vyncke | [Ballot comment] Thank you for the work put into this document. It is short and easy to understand. I find that the contents of section … [Ballot comment] Thank you for the work put into this document. It is short and easy to understand. I find that the contents of section 1 and of section 2 are quite duplicate. In section 2, the use of capitalized word after a ":" looks weird to me but I am not a native English speaker. I hope that this helps to improve the document, Regards, -éric |
2020-12-13
|
07 | Éric Vyncke | [Ballot Position Update] New position, No Objection, has been recorded for Éric Vyncke |
2020-12-13
|
07 | Murray Kucherawy | [Ballot comment] Some places in this document use "reuse", others "re-use". I'm not sure which one is right, but it should be consistent throughout. In … [Ballot comment] Some places in this document use "reuse", others "re-use". I'm not sure which one is right, but it should be consistent throughout. In Section 3: A client starting a new connection SHOULD set new_session_count to the desired number of session tickets and resumption_count to 0. Since it's only SHOULD, I'm curious about why an implementer might decide to do something other than this. |
2020-12-13
|
07 | Murray Kucherawy | [Ballot Position Update] New position, No Objection, has been recorded for Murray Kucherawy |
2020-12-13
|
07 | Erik Kline | [Ballot Position Update] New position, No Objection, has been recorded for Erik Kline |
2020-12-07
|
07 | Martin Duke | [Ballot Position Update] New position, Yes, has been recorded for Martin Duke |
2020-12-05
|
07 | Benjamin Kaduk | IESG state changed to IESG Evaluation from Waiting for Writeup |
2020-12-04
|
07 | Amy Vezza | Placed on agenda for telechat - 2020-12-17 |
2020-12-03
|
07 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA - Not OK |
2020-12-03
|
07 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-07.txt |
2020-12-03
|
07 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2020-12-03
|
07 | Christopher Wood | Uploaded new revision |
2020-12-03
|
06 | Benjamin Kaduk | Ballot has been issued |
2020-12-03
|
06 | Benjamin Kaduk | [Ballot Position Update] New position, Yes, has been recorded for Benjamin Kaduk |
2020-12-03
|
06 | Benjamin Kaduk | Created "Approve" ballot |
2020-12-03
|
06 | Benjamin Kaduk | Ballot writeup was changed |
2020-12-03
|
06 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
2020-12-02
|
06 | (System) | IANA Review state changed to IANA - Not OK from IANA - Review Needed |
2020-12-02
|
06 | Amanda Baber | (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Functions Operator has completed its review of draft-ietf-tls-ticketrequests-06. If any part of this review is inaccurate, please let … (Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs: The IANA Functions Operator has completed its review of draft-ietf-tls-ticketrequests-06. If any part of this review is inaccurate, please let us know. The IANA Functions Operator understands that upon approval of this document, there will be a single action to complete. In the TLS ExtensionType Values registry on the Transport Layer Security (TLS) Extensions registry page at https://www.iana.org/assignments/tls-extensiontype-values/ a single new ExtensionType is to be registered: Value: [ TBD-at-Registration ] Extension Name: ticket_request TLS 1.3: CH, EE Recommended: Y Reference: [ RFC-to-be ] As this document requests registration in an Expert Review or Specification Required (see RFC 8126) registry, we will initiate the required expert review via a separate request. This review must be completed before the document's IANA state can be changed to "IANA OK." Note: The action requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed. Thank you, Amanda Baber Lead IANA Services Specialist |
2020-11-27
|
06 | Dale Worley | Request for Last Call review by GENART Completed: Ready. Reviewer: Dale Worley. Sent review to list. |
2020-11-26
|
06 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Phillip Hallam-Baker |
2020-11-26
|
06 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Phillip Hallam-Baker |
2020-11-25
|
06 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martínez |
2020-11-25
|
06 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Carlos Martínez |
2020-11-21
|
06 | Jean Mahoney | Request for Last Call review by GENART is assigned to Dale Worley |
2020-11-21
|
06 | Jean Mahoney | Request for Last Call review by GENART is assigned to Dale Worley |
2020-11-19
|
06 | Amy Vezza | IANA Review state changed to IANA - Review Needed |
2020-11-19
|
06 | Amy Vezza | The following Last Call announcement was sent out (ends 2020-12-03): From: The IESG To: IETF-Announce CC: tls-chairs@ietf.org, draft-ietf-tls-ticketrequests@ietf.org, kaduk@mit.edu, sean@sn3rd.com, Sean … The following Last Call announcement was sent out (ends 2020-12-03): From: The IESG To: IETF-Announce CC: tls-chairs@ietf.org, draft-ietf-tls-ticketrequests@ietf.org, kaduk@mit.edu, sean@sn3rd.com, Sean Turner , tls@ietf.org Reply-To: last-call@ietf.org Sender: Subject: Last Call: (TLS Ticket Requests) to Proposed Standard The IESG has received a request from the Transport Layer Security WG (tls) to consider the following document: - 'TLS Ticket Requests' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2020-12-03. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract TLS session tickets enable stateless connection resumption for clients without server-side, per-client, state. Servers vend an arbitrary number of session tickets to clients, at their discretion, upon connection establishment. Clients store and use tickets when resuming future connections. This document describes a mechanism by which clients can specify the desired number of tickets needed for future connections. This extension aims to provide a means for servers to determine the number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-tls-ticketrequests/ No IPR declarations have been submitted directly on this I-D. |
2020-11-19
|
06 | Amy Vezza | IESG state changed to In Last Call from Last Call Requested |
2020-11-19
|
06 | Benjamin Kaduk | Last call was requested |
2020-11-19
|
06 | Benjamin Kaduk | Last call announcement was generated |
2020-11-19
|
06 | Benjamin Kaduk | Ballot approval text was generated |
2020-11-19
|
06 | Benjamin Kaduk | Ballot writeup was generated |
2020-11-19
|
06 | Benjamin Kaduk | IESG state changed to Last Call Requested from AD Evaluation::AD Followup |
2020-11-19
|
06 | (System) | Sub state has been changed to AD Followup from Revised ID Needed |
2020-11-19
|
06 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-06.txt |
2020-11-19
|
06 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2020-11-19
|
06 | Christopher Wood | Uploaded new revision |
2020-10-28
|
05 | Benjamin Kaduk | IESG state changed to AD Evaluation::Revised I-D Needed from AD Evaluation |
2020-10-28
|
05 | Benjamin Kaduk | IESG state changed to AD Evaluation from Publication Requested |
2020-05-01
|
05 | Sean Turner | # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform … # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform servers about the desired number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The draft is intended for standards track. The individual draft indicated informational and the initial WG draft did as well. A "Y" in the Recommended column requires standards track though. Changing the track to standards track was confirmed on list; there were no objections. # Review and Consensus The draft had a fairly quiet existence until the -02 version, which was also the version where the authors requested the chairs request WGLC. The WGLC and two issue-specific consensus calls that followed were all fairly contentious. The WGLC and the two issue-specific consensus calls resulted in changes to the draft: the count field was renamed new_session_count, a new counter called resumption_count was added, text was added to address racing pre-conditions. The addition of the second counter acknowledged that resumption is different and can tolerate the complexity of the additional counter. What was not added was text to address ticket reuse use cases; RFC 8446 indicates "clients SHOULD NOT reuse a ticket for multiple connections". One of the issue-specific consensus calls about this was about this point and there was no consensus to add text to address this use case. I would characterize the consensus as rough. I give it this characterization because, I believe, that the same people that supported adopting the draft support publishing the mechanism, but there are differences in how far the mechanism should go in supporting ticket reuse. I, however, have no specific concerns about this draft. # Intellectual Property I confirmed with each author that to their direct, personal knowledge of any IPR related to this draft has already been disclosed, in conformance with BCPs 78 and 79. # Other Points IANA considerations are correct; it refers to all the appropriate columns for a newly registered extension. There are no downrefs. IDNits has no complaints. |
2020-05-01
|
05 | Sean Turner | Responsible AD changed to Benjamin Kaduk |
2020-05-01
|
05 | Sean Turner | IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up |
2020-05-01
|
05 | Sean Turner | IESG state changed to Publication Requested from I-D Exists |
2020-05-01
|
05 | Sean Turner | IESG process started in state Publication Requested |
2020-05-01
|
05 | Sean Turner | # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform … # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform servers about the desired number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The draft is intended for standards track. The individual draft indicated informational and the initial WG draft did as well. A "Y" in the Recommended column requires standards track though. Changing the track to standards track was confirmed on list; there were no objections. # Review and Consensus The draft had a fairly quiet existence until the -02 version, which was also the version where the authors requested the chairs request WGLC. The WGLC and two issue-specific consensus calls that followed were all fairly contentious. The WGLC and the two issue-specific consensus calls resulted in changes to the draft: the count field was renamed new_session_count, a new counter called resumption_count was added, text was added to address racing pre-conditions. The addition of the second counter acknowledged that resumption is different and can tolerate the complexity of the additional counter. What was not added was text to address ticket reuse use cases; RFC 8446 indicates "clients SHOULD NOT reuse a ticket for multiple connections". One of the issue-specific consensus calls about this was about this point and there was no consensus to add text to address this use case. I would characterize the consensus as rough. I give it this characterization because, I believe, that the same people that supported adopting the draft support publishing the mechanism, but there are differences in how far the mechanism should go in supporting ticket reuse. I, however, have no specific concerns about this draft. # Intellectual Property I confirmed with each author that to their direct, personal knowledge of any IPR related to this draft has already been disclosed, in conformance with BCPs 78 and 79. # Other Points IANA considerations are correct; it refers to all the appropriate columns for a newly registered extension. There are no downrefs. IDNits has no complaints. |
2020-05-01
|
05 | Sean Turner | # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform … # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform servers about the desired number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The draft is intended for standards track. The individual draft indicated informational and the initial WG draft did as well. A "Y" in the Recommended column requires standards track though. Changing the track to standards track was confirmed on list; there were no objections. # Review and Consensus The draft had a fairly quiet existence until the -02 version, which was also the version where the authors requested the chairs request WGLC. The WGLC and two issue-specific consensus calls that followed were all fairly contentious. The WGLC and the two issue-specific consensus calls resulted in changes to the draft: the count field was renamed new_session_count, a new counter called resumption_count was added, text was added to address racing pre-conditions. The addition of the second counter acknowledged that resumption is different and can tolerate the complexity of the additional counter. What was not added was text to address ticket reuse use cases; RFC 8446 indicates "clients SHOULD NOT reuse a ticket for multiple connections". One of the issue-specific consensus calls about this was about this point and there was no consensus to add text to address this use case. I would characterize the consensus as rough. I give it this characterization because, I believe, that the same people that supported adopting the draft support publishing the mechanism, but there are differences in how far the draft should go in supporting ticket reuse. I, however, have no specific concerns about this draft. # Intellectual Property I confirmed with each author that to their direct, personal knowledge of any IPR related to this draft has already been disclosed, in conformance with BCPs 78 and 79. # Other Points IANA considerations are correct; it refers to all the appropriate columns for a newly registered extension. There are no downrefs. IDNits has no complaints. |
2020-05-01
|
05 | Sean Turner | Tag Revised I-D Needed - Issue raised by WG cleared. |
2020-05-01
|
05 | Sean Turner | IETF WG state changed to WG Consensus: Waiting for Write-Up from WG Document |
2020-04-24
|
05 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-05.txt |
2020-04-24
|
05 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2020-04-24
|
05 | Christopher Wood | Uploaded new revision |
2019-11-21
|
04 | Sean Turner | Tag Revised I-D Needed - Issue raised by WG set. |
2019-11-21
|
04 | Sean Turner | IETF WG state changed to WG Document from In WG Last Call |
2019-11-05
|
04 | Sean Turner | I inadvertently put this draft in WG Consensus before the WGLC had been issued. |
2019-11-05
|
04 | Sean Turner | IETF WG state changed to In WG Last Call from WG Consensus: Waiting for Write-Up |
2019-11-04
|
04 | Sean Turner | *** DRAFT *** # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can … *** DRAFT *** # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform servers about the desired number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The draft is intended for standards track. I will note that the draft has informational since it was an individual -00 and when it was adopted by the WG, but the IANA considerations also included marking the Recommended column as “Y” since its individual -00 version as well. I caught this mismatch, “Y” in the Recommended column requires Standards Track according to RFC 8446, during my Shepherd review. The version being submitted to the IESG indicates standards track. I emailed the WG to ensure there were no objections to the swap, but received radio silence. I interpreted this silence as acceptance that rationale to switch to Standards Track. But, I will also note that typically the TLS WG does not stand on process so I never really expected any kind of response from the WG. # Review and Consensus *** TBD I have no specific concerns about this draft. # Intellectual Property I confirmed with each author that to their direct, personal knowledge of any IPR related to this draft has already been disclosed, in conformance with BCPs 78 and 79. # Other Points IANA considerations are correct; it refers to all the appropriate columns for a newly registered extension. There are no downrefs. IDNits complains about an outdated normative reference. This draft makes reference to both RFC 5077 and 8446, 8446 obsoletes 5077, so please ignore this nit. |
2019-11-04
|
04 | Sean Turner | *** DRAFT *** # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can … *** DRAFT *** # Summary Sean Turner is the Shepherd. Ben Kaduk is the Area Director. This document defines a TLS extension that clients can use to inform servers about the desired number of tickets to generate in order to reduce ticket waste, while simultaneously priming clients for future connection attempts. The draft is intended for standards track. I will note that the draft has informational since it was an individual -00 and when it was adopted by the WG, but the IANA considerations also included marking the Recommended column as “Y” since its individual -00 version as well. I caught this mismatch, “Y” in the Recommended column requires Standards Track according to RFC 8446, during my Shepherd review. The version being submitted to the IESG indicates standards track. I emailed the WG to ensure there were no objections to the swap, but received radio silence. I interpreted this silence as acceptance that rationale to switch to Standards Track. But, I will also note that typically the TLS WG does not stand on process so I never really expected any kind of response from the WG. # Review and Consensus I would characterize the consensus as having been reached fairly quickly and being broad enough to publish. This draft has been discussed on the mailing list and at IETF 103. Because the draft is straightforward, clear, and short, there has not been a lot of list discussion about the draft. In my opinion, this is not such a bad thing. The WG should be able to adopt a simple idea, discuss it, and get the draft out the door. No reviews done to date, and there is no real need for any kind of special reviews. I have no specific concerns about this draft. # Intellectual Property ** CONFIRMATIONS from Tommy and Chris. Awaiting David. I confirmed with each author that to their direct, personal knowledge of any IPR related to this draft has already been disclosed, in conformance with BCPs 78 and 79. # Other Points IANA considerations are correct; it refers to all the appropriate columns for a newly registered extension. There are no downrefs. IDNits complains about an outdated normative reference. This draft makes reference to both RFC 5077 and 8446, 8446 obsoletes 5077, so please ignore this nit. |
2019-11-04
|
04 | Sean Turner | Changed document URLs from: [] to: repository https://github.com/tlswg/draft-ietf-tls-ticketrequest |
2019-11-04
|
04 | Sean Turner | Notification list changed to Sean Turner <sean@sn3rd.com> |
2019-11-04
|
04 | Sean Turner | Document shepherd changed to Sean Turner |
2019-11-04
|
04 | Sean Turner | IETF WG state changed to WG Consensus: Waiting for Write-Up from WG Document |
2019-11-04
|
04 | Sean Turner | Changed consensus to Yes from Unknown |
2019-11-04
|
04 | Sean Turner | Intended Status changed to Proposed Standard from None |
2019-11-04
|
04 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-04.txt |
2019-11-04
|
04 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2019-11-04
|
04 | Christopher Wood | Uploaded new revision |
2019-10-18
|
03 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-03.txt |
2019-10-18
|
03 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2019-10-18
|
03 | Christopher Wood | Uploaded new revision |
2019-09-27
|
02 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-02.txt |
2019-09-27
|
02 | (System) | New version accepted (logged-in submitter: Christopher Wood) |
2019-09-27
|
02 | Christopher Wood | Uploaded new revision |
2019-06-06
|
01 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-01.txt |
2019-06-06
|
01 | (System) | New version approved |
2019-06-06
|
01 | (System) | Request for posting confirmation emailed to previous authors: David Schinazi , Christopher Wood , Tommy Pauly |
2019-06-06
|
01 | Christopher Wood | Uploaded new revision |
2019-01-18
|
00 | Sean Turner | This document now replaces draft-wood-tls-ticketrequests instead of None |
2019-01-18
|
00 | Christopher Wood | New version available: draft-ietf-tls-ticketrequests-00.txt |
2019-01-18
|
00 | (System) | WG -00 approved |
2019-01-18
|
00 | Christopher Wood | Set submitter to ""Christopher A. Wood" ", replaces to (none) and sent approval email to group chairs: tls-chairs@ietf.org |
2019-01-18
|
00 | Christopher Wood | Uploaded new revision |