CoAP Simple Congestion Control/Advanced
draft-ietf-core-cocoa-03
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2020-09-10
|
03 | Marco Tiloca | Changed document external resources from: [] to: github_repo https://github.com/core-wg/cocoa (Working Group Repo) |
2018-11-14
|
03 | (System) | Document has expired |
2018-11-14
|
03 | (System) | IESG state changed to Dead from AD is watching |
2018-11-13
|
03 | Mirja Kühlewind | IESG state changed to AD is watching from AD Evaluation |
2018-11-09
|
03 | Mirja Kühlewind | Tag Revised I-D Needed - Issue raised by WG set. |
2018-11-09
|
03 | Mirja Kühlewind | IETF WG state changed to WG Document from Submitted to IESG for Publication |
2018-04-23
|
03 | Mirja Kühlewind | Removed from agenda for telechat |
2018-04-03
|
03 | Mirja Kühlewind | Telechat date has been changed to 2018-05-10 from 2018-04-19 |
2018-03-28
|
03 | Mirja Kühlewind | Changed consensus to Unknown from Yes |
2018-03-28
|
03 | Mirja Kühlewind | IESG state changed to AD Evaluation from Publication Requested |
2018-03-22
|
03 | Tero Kivinen | Request for Telechat review by SECDIR Completed: Has Nits. Reviewer: Vincent Roca. |
2018-03-21
|
03 | Mirja Kühlewind | Telechat date has been changed to 2018-04-19 from 2018-04-05 |
2018-03-16
|
03 | Christer Holmberg | Request for Telechat review by GENART Completed: Ready with Issues. Reviewer: Christer Holmberg. Sent review to list. |
2018-03-08
|
03 | Jean Mahoney | Request for Telechat review by GENART is assigned to Christer Holmberg |
2018-03-08
|
03 | Jean Mahoney | Request for Telechat review by GENART is assigned to Christer Holmberg |
2018-03-06
|
03 | Wesley Eddy | Request for Telechat review by TSVART Completed: Ready. Reviewer: Wesley Eddy. |
2018-02-28
|
03 | Martin Stiemerling | Request for Telechat review by TSVART is assigned to Wesley Eddy |
2018-02-28
|
03 | Martin Stiemerling | Request for Telechat review by TSVART is assigned to Wesley Eddy |
2018-02-23
|
03 | Gunter Van de Velde | Request for Telechat review by OPSDIR Completed: Serious Issues. Reviewer: Scott Bradner. Sent review to list. |
2018-02-23
|
03 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Scott Bradner |
2018-02-23
|
03 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Scott Bradner |
2018-02-22
|
03 | Mirja Kühlewind | Telechat date has been changed to 2018-04-05 from 2018-03-08 |
2018-02-21
|
03 | Scott Bradner | Request for Telechat review by OPSDIR Completed: Serious Issues. Reviewer: Scott Bradner. Sent review to list. |
2018-02-21
|
03 | Carsten Bormann | New version available: draft-ietf-core-cocoa-03.txt |
2018-02-21
|
03 | (System) | New version approved |
2018-02-21
|
03 | (System) | Request for posting confirmation emailed to previous authors: Carsten Bormann , Ilker Demirkol , Carles Gomez , August Betzler |
2018-02-21
|
03 | Carsten Bormann | Uploaded new revision |
2018-02-21
|
02 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Scott Bradner |
2018-02-21
|
02 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Scott Bradner |
2018-02-16
|
02 | Henrik Levkowetz | Request for Telechat review by OPSDIR is assigned to (None) |
2018-02-16
|
02 | Henrik Levkowetz | Request for Telechat review by OPSDIR is assigned to (None) |
2018-02-16
|
02 | Tero Kivinen | Request for Telechat review by SECDIR is assigned to Vincent Roca |
2018-02-16
|
02 | Tero Kivinen | Request for Telechat review by SECDIR is assigned to Vincent Roca |
2018-02-14
|
02 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Éric Vyncke |
2018-02-14
|
02 | Gunter Van de Velde | Request for Telechat review by OPSDIR is assigned to Éric Vyncke |
2018-02-12
|
02 | Jaime Jimenez | ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Mirja Kuehlewind The CoAP protocol needs to be implemented in such a way … ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Mirja Kuehlewind The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. The CoRE CoAP specification defines basic behavior that exhibits low risk of congestion with minimal implementation requirements. It also leaves room for combining the base specification with advanced congestion control mechanisms with higher performance. This specification defines more advanced, but still simple CoRE Congestion Control mechanisms, called CoCoA. The core of these mechanisms is a Retransmission TimeOut (RTO) algorithm that makes use of Round-Trip Time (RTT) estimates, in contrast with how the RTO is determined as per the base CoAP specification (RFC 7252). The mechanisms defined in this document have relatively low complexity, yet they improve the default CoAP RTO algorithm. The design of the mechanisms in this specification has made use of input from simulations and experiments in real networks. The document is intended as Informational, as it provides an optimisation of the existing CoAP congestion control mechanism with a Retransmission TimeOut (RTO) algorithm based on RTT estimation. ###Review and Consensus The document has gone through multiple expert reviews and has been discussed on multiple IETF meetings. Before the last IETF the WGLC was completed. ###Intellectual Property Each author has stated that they do not have direct, personal knowledge of any IPR related to this document. I am not aware of any IPR discussion about this document on the CoRE WG. ###Other Points There are RFC Editor comments that need to be edited out. This document makes no requirements on IANA. ###Checklist * [x] Does the shepherd stand behind the document and think the document is ready for publication? * [x] Is the correct RFC type indicated in the title page header? * [x] Is the abstract both brief and sufficient, and does it stand alone as a brief summary? * [x] Is the intent of the document accurately and adequately explained in the introduction? * [x] Have all required formal reviews (MIB Doctor, Media Type, URI, etc.) been requested and/or completed? * [x] Has the shepherd performed automated checks -- idnits (see http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist), checks of BNF rules, XML code and schemas, MIB definitions, and so on -- and determined that the document passes the tests? * [x] Has each author stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79? * [x] Have all references within this document been identified as either normative or informative, and does the shepherd agree with how they have been classified? * [x] Are all normative references made to documents that are ready for advancement and are otherwise in a clear state? * [x] If publication of this document changes the status of any existing RFCs, are those RFCs listed on the title page header, and are the changes listed in the abstract and discussed (explained, not just mentioned) in the introduction? `Does not apply` * [x] If this is a "bis" document, have all of the errata been considered? `Does not apply` * **IANA** Considerations: `There are no requirements on IANA` * [x] Are the IANA Considerations clear and complete? Remember that IANA have to understand unambiguously what's being requested, so they can perform the required actions. * [x] Are all protocol extensions that the document makes associated with the appropriate reservations in IANA registries? * [x] Are all IANA registries referred to by their exact names (check them in http://www.iana.org/protocols/ to be sure)? * [x] Have you checked that any registrations made by this document correctly follow the policies and procedures for the appropriate registries? * [x] For registrations that require expert review (policies of Expert Review or Specification Required), have you or the working group had any early review done, to make sure the requests are ready for last call? * [x] For any new registries that this document creates, has the working group actively chosen the allocation procedures and policies and discussed the alternatives? * [x] Have reasonable registry names been chosen (that will not be confused with those of other registries), and have the initial contents and valid value ranges been clearly specified? |
2018-02-12
|
02 | Jaime Jimenez | Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Mirja Kuehlewind The CoAP … Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Mirja Kuehlewind The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. The CoRE CoAP specification defines basic behavior that exhibits low risk of congestion with minimal implementation requirements. It also leaves room for combining the base specification with advanced congestion control mechanisms with higher performance. This specification defines more advanced, but still simple CoRE Congestion Control mechanisms, called CoCoA. The core of these mechanisms is a Retransmission TimeOut (RTO) algorithm that makes use of Round-Trip Time (RTT) estimates, in contrast with how the RTO is determined as per the base CoAP specification (RFC 7252). The mechanisms defined in this document have relatively low complexity, yet they improve the default CoAP RTO algorithm. The design of the mechanisms in this specification has made use of input from simulations and experiments in real networks. The document is intended as Informational, as it provides an optimisation of the existing CoAP congestion control mechanism with a Retransmission TimeOut (RTO) algorithm based on RTT estimation. ###Review and Consensus The document has gone through multiple expert reviews and has been discussed on multiple IETF meetings. Before the last IETF the WGLC was completed. ###Intellectual Property Each author has stated that they do not have direct, personal knowledge of any IPR related to this document. I am not aware of any IPR discussion about this document on the CoRE WG. ###Other Points There are RFC Editor comments that need to be edited out. This document makes no requirements on IANA. ###Checklist * [x] Does the shepherd stand behind the document and think the document is ready for publication? * [x] Is the correct RFC type indicated in the title page header? * [x] Is the abstract both brief and sufficient, and does it stand alone as a brief summary? * [x] Is the intent of the document accurately and adequately explained in the introduction? * [x] Have all required formal reviews (MIB Doctor, Media Type, URI, etc.) been requested and/or completed? * [x] Has the shepherd performed automated checks -- idnits (see http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist), checks of BNF rules, XML code and schemas, MIB definitions, and so on -- and determined that the document passes the tests? * [x] Has each author stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79? * [x] Have all references within this document been identified as either normative or informative, and does the shepherd agree with how they have been classified? * [x] Are all normative references made to documents that are ready for advancement and are otherwise in a clear state? * [x] If publication of this document changes the status of any existing RFCs, are those RFCs listed on the title page header, and are the changes listed in the abstract and discussed (explained, not just mentioned) in the introduction? `Does not apply` * [x] If this is a "bis" document, have all of the errata been considered? `Does not apply` * **IANA** Considerations: `There are no requirements on IANA` * [x] Are the IANA Considerations clear and complete? Remember that IANA have to understand unambiguously what's being requested, so they can perform the required actions. * [x] Are all protocol extensions that the document makes associated with the appropriate reservations in IANA registries? * [x] Are all IANA registries referred to by their exact names (check them in http://www.iana.org/protocols/ to be sure)? * [x] Have you checked that any registrations made by this document correctly follow the policies and procedures for the appropriate registries? * [x] For registrations that require expert review (policies of Expert Review or Specification Required), have you or the working group had any early review done, to make sure the requests are ready for last call? * [x] For any new registries that this document creates, has the working group actively chosen the allocation procedures and policies and discussed the alternatives? * [x] Have reasonable registry names been chosen (that will not be confused with those of other registries), and have the initial contents and valid value ranges been clearly specified? |
2018-02-12
|
02 | Jaime Jimenez | Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: "Mirja Kuehlewind" The CoAP … Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: "Mirja Kuehlewind" The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. The CoRE CoAP specification defines basic behavior that exhibits low risk of congestion with minimal implementation requirements. It also leaves room for combining the base specification with advanced congestion control mechanisms with higher performance. This specification defines more advanced, but still simple CoRE Congestion Control mechanisms, called CoCoA. The core of these mechanisms is a Retransmission TimeOut (RTO) algorithm that makes use of Round-Trip Time (RTT) estimates, in contrast with how the RTO is determined as per the base CoAP specification (RFC 7252). The mechanisms defined in this document have relatively low complexity, yet they improve the default CoAP RTO algorithm. The design of the mechanisms in this specification has made use of input from simulations and experiments in real networks. The document is intended as Informational, as it provides an optimisation of the existing CoAP congestion control mechanism with a Retransmission TimeOut (RTO) algorithm based on RTT estimation. ###Review and Consensus The document has gone through multiple expert reviews and has been discussed on multiple IETF meetings. Before the last IETF the WGLC was completed. ###Intellectual Property Each author has stated that they do not have direct, personal knowledge of any IPR related to this document. I am not aware of any IPR discussion about this document on the CoRE WG. ###Other Points There are RFC Editor comments that need to be edited out. This document makes no requirements on IANA. ###Checklist * [x] Does the shepherd stand behind the document and think the document is ready for publication? * [x] Is the correct RFC type indicated in the title page header? * [x] Is the abstract both brief and sufficient, and does it stand alone as a brief summary? * [x] Is the intent of the document accurately and adequately explained in the introduction? * [x] Have all required formal reviews (MIB Doctor, Media Type, URI, etc.) been requested and/or completed? * [x] Has the shepherd performed automated checks -- idnits (see http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist), checks of BNF rules, XML code and schemas, MIB definitions, and so on -- and determined that the document passes the tests? * [x] Has each author stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79? * [x] Have all references within this document been identified as either normative or informative, and does the shepherd agree with how they have been classified? * [x] Are all normative references made to documents that are ready for advancement and are otherwise in a clear state? * [x] If publication of this document changes the status of any existing RFCs, are those RFCs listed on the title page header, and are the changes listed in the abstract and discussed (explained, not just mentioned) in the introduction? `Does not apply` * [x] If this is a "bis" document, have all of the errata been considered? `Does not apply` * **IANA** Considerations: `There are no requirements on IANA` * [x] Are the IANA Considerations clear and complete? Remember that IANA have to understand unambiguously what's being requested, so they can perform the required actions. * [x] Are all protocol extensions that the document makes associated with the appropriate reservations in IANA registries? * [x] Are all IANA registries referred to by their exact names (check them in http://www.iana.org/protocols/ to be sure)? * [x] Have you checked that any registrations made by this document correctly follow the policies and procedures for the appropriate registries? * [x] For registrations that require expert review (policies of Expert Review or Specification Required), have you or the working group had any early review done, to make sure the requests are ready for last call? * [x] For any new registries that this document creates, has the working group actively chosen the allocation procedures and policies and discussed the alternatives? * [x] Have reasonable registry names been chosen (that will not be confused with those of other registries), and have the initial contents and valid value ranges been clearly specified? |
2018-02-09
|
02 | Mirja Kühlewind | Placed on agenda for telechat - 2018-03-08 |
2018-01-08
|
02 | Wesley Eddy | Request for Early review by TSVART Completed: Not Ready. Reviewer: Wesley Eddy. Sent review to list. |
2018-01-08
|
02 | Martin Stiemerling | Request for Early review by TSVART is assigned to Wesley Eddy |
2018-01-08
|
02 | Martin Stiemerling | Request for Early review by TSVART is assigned to Wesley Eddy |
2017-12-18
|
02 | Mirja Kühlewind | Requested Early review by TSVART |
2017-12-16
|
02 | Alexey Melnikov | Shepherding AD changed to Mirja Kühlewind |
2017-12-16
|
02 | Alexey Melnikov | Changed consensus to Yes from Unknown |
2017-12-16
|
02 | Jaime Jimenez | Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Alexey Melnikov, The CoAP … Summary for this document can be found at: http://jaimejim.github.io/temp/draft-ietf-core-cocoa.html ## Shepherd Writeup ###Summary * Document Shepherd: Jaime Jiménez, * Area Director: Alexey Melnikov, The CoAP protocol needs to be implemented in such a way that it does not cause persistent congestion on the network it uses. The CoRE CoAP specification defines basic behavior that exhibits low risk of congestion with minimal implementation requirements. It also leaves room for combining the base specification with advanced congestion control mechanisms with higher performance. This specification defines more advanced, but still simple CoRE Congestion Control mechanisms, called CoCoA. The core of these mechanisms is a Retransmission TimeOut (RTO) algorithm that makes use of Round-Trip Time (RTT) estimates, in contrast with how the RTO is determined as per the base CoAP specification (RFC 7252). The mechanisms defined in this document have relatively low complexity, yet they improve the default CoAP RTO algorithm. The design of the mechanisms in this specification has made use of input from simulations and experiments in real networks. The document is intended as Informational. ###Review and Consensus The document has gone through multiple expert reviews and has been discussed on multiple IETF meetings. Before the last IETF the WGLC was completed. ###Intellectual Property Each author has stated that they do not have direct, personal knowledge of any IPR related to this document. I am not aware of any IPR discussion about this document on the CoRE WG. ###Other Points There are RFC Editor comments that need to be edited out. This document makes no requirements on IANA. ###Checklist * [x] Does the shepherd stand behind the document and think the document is ready for publication? * [x] Is the correct RFC type indicated in the title page header? * [x] Is the abstract both brief and sufficient, and does it stand alone as a brief summary? * [x] Is the intent of the document accurately and adequately explained in the introduction? * [x] Have all required formal reviews (MIB Doctor, Media Type, URI, etc.) been requested and/or completed? * [x] Has the shepherd performed automated checks -- idnits (see http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist), checks of BNF rules, XML code and schemas, MIB definitions, and so on -- and determined that the document passes the tests? * [x] Has each author stated that their direct, personal knowledge of any IPR related to this document has already been disclosed, in conformance with BCPs 78 and 79? * [x] Have all references within this document been identified as either normative or informative, and does the shepherd agree with how they have been classified? * [x] Are all normative references made to documents that are ready for advancement and are otherwise in a clear state? * [x] If publication of this document changes the status of any existing RFCs, are those RFCs listed on the title page header, and are the changes listed in the abstract and discussed (explained, not just mentioned) in the introduction? `Does not apply` * [x] If this is a "bis" document, have all of the errata been considered? `Does not apply` * **IANA** Considerations: `There are no requirements on IANA` * [x] Are the IANA Considerations clear and complete? Remember that IANA have to understand unambiguously what's being requested, so they can perform the required actions. * [x] Are all protocol extensions that the document makes associated with the appropriate reservations in IANA registries? * [x] Are all IANA registries referred to by their exact names (check them in http://www.iana.org/protocols/ to be sure)? * [x] Have you checked that any registrations made by this document correctly follow the policies and procedures for the appropriate registries? * [x] For registrations that require expert review (policies of Expert Review or Specification Required), have you or the working group had any early review done, to make sure the requests are ready for last call? * [x] For any new registries that this document creates, has the working group actively chosen the allocation procedures and policies and discussed the alternatives? * [x] Have reasonable registry names been chosen (that will not be confused with those of other registries), and have the initial contents and valid value ranges been clearly specified? |
2017-12-16
|
02 | Jaime Jimenez | Responsible AD changed to Alexey Melnikov |
2017-12-16
|
02 | Jaime Jimenez | IETF WG state changed to Submitted to IESG for Publication from In WG Last Call |
2017-12-16
|
02 | Jaime Jimenez | IESG state changed to Publication Requested |
2017-12-16
|
02 | Jaime Jimenez | IESG process started in state Publication Requested |
2017-12-16
|
02 | Jaime Jimenez | Intended Status changed to Informational from None |
2017-12-16
|
02 | Jaime Jimenez | Notification list changed to Jaime Jimenez <jaime.jimenez@ericsson.com> |
2017-12-16
|
02 | Jaime Jimenez | Document shepherd changed to Jaime Jimenez |
2017-12-16
|
02 | Jaime Jimenez | Changed document writeup |
2017-11-16
|
02 | Jaime Jimenez | IETF WG state changed to In WG Last Call from WG Document |
2017-10-30
|
02 | Carsten Bormann | New version available: draft-ietf-core-cocoa-02.txt |
2017-10-30
|
02 | (System) | New version approved |
2017-10-30
|
02 | (System) | Request for posting confirmation emailed to previous authors: Carsten Bormann , Ilker Demirkol , core-chairs@ietf.org, Carles Gomez , August Betzler |
2017-10-30
|
02 | Carsten Bormann | Uploaded new revision |
2017-10-30
|
02 | Carsten Bormann | Uploaded new revision |
2017-09-14
|
01 | (System) | Document has expired |
2017-03-13
|
01 | Carsten Bormann | New version available: draft-ietf-core-cocoa-01.txt |
2017-03-13
|
01 | (System) | New version approved |
2017-03-13
|
01 | (System) | Request for posting confirmation emailed to previous authors: Carsten Bormann , Ilker Demirkol , Carles Gomez , August Betzler |
2017-03-13
|
01 | Carsten Bormann | Uploaded new revision |
2016-10-31
|
00 | Carsten Bormann | This document now replaces draft-bormann-core-cocoa instead of None |
2016-10-21
|
00 | Carsten Bormann | New version available: draft-ietf-core-cocoa-00.txt |
2016-10-21
|
00 | (System) | WG -00 approved |
2016-10-20
|
00 | Carsten Bormann | Set submitter to "Carsten Bormann ", replaces to (none) and sent approval email to group chairs: core-chairs@ietf.org |
2016-10-20
|
00 | Carsten Bormann | Uploaded new revision |