Trusted Execution Environment Provisioning (TEEP) Protocol
draft-ietf-teep-protocol-18
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2023-11-06
|
18 | Akira Tsukamoto | New version available: draft-ietf-teep-protocol-18.txt |
2023-11-06
|
18 | Akira Tsukamoto | New version accepted (logged-in submitter: Akira Tsukamoto) |
2023-11-06
|
18 | Akira Tsukamoto | Uploaded new revision |
2023-10-23
|
17 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-17.txt |
2023-10-23
|
17 | Hannes Tschofenig | New version accepted (logged-in submitter: Hannes Tschofenig) |
2023-10-23
|
17 | Hannes Tschofenig | Uploaded new revision |
2023-09-11
|
16 | Dave Thaler | Added to session: interim-2023-suit-01 |
2023-09-05
|
16 | Dave Thaler | New version available: draft-ietf-teep-protocol-16.txt |
2023-09-05
|
16 | Dave Thaler | New version accepted (logged-in submitter: Dave Thaler) |
2023-09-05
|
16 | Dave Thaler | Uploaded new revision |
2023-07-23
|
15 | Tirumaleswar Reddy.K | Title: Trusted Execution Environment Provisioning (TEEP) Protocol Current Version: https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol-15 ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of … Title: Trusted Execution Environment Provisioning (TEEP) Protocol Current Version: https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol-15 ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? The draft was adopted in Dec, 2017 with good WG support for adoption. It has been thoroughly reviewed by working group members. The authors have given updates on progress of the draft during all of the WG meetings. A number of detailed reviews of the document were posted to the working group mailing list, along with the issues and pull requests logged on GitHub. Further, there has been active participation in IETF Hackathon activities from WG members to implement, test and interop TEEP protocol. The authors of this document have extensive experience with the TEE technologies and implementations. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? No, there was no controversy about any points in the draft. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) There are no open issues that I am aware of, nor any other outstanding areas of concern, nor are there any known issues of extreme discontent or conflict. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as [RFC 7942][3] recommends) or elsewhere (where)? Multiple open source code repositories of the TEEP protocol is available and are listed in the "Additional resources" Section of https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/. The protocol was implemented and interop was done during IETF hackathons to identify and fix issues. IETF hackathon reports were presented in the WG meetings. ## Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The TEEP protocol uses CBOR and relies on COSE for security. It leverages the work in SUIT (SUIT manifest format is used) and RATS (EAT format is used) WGs. The draft has been reviewed by members actively contributing to these working groups. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. No. 7. If the document contains a YANG module, has the final version of the module been checked with any of the [recommended validation tools][4] for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342][5]? No. 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. Yes, CBOR's CDDL validation was done for every commit (see https://github.com/ietf-teep/teep-protocol) ## Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? Yes, it is ready to be handed off to the responsible AD. 10. Several IETF Areas have assembled [lists of common issues that their reviewers encounter][6]. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent reviews? This draft requires reviews from SECDIR and IOTDIR representatives. 11. What type of RFC publication is being requested on the IETF stream ([Best Current Practice][12], [Proposed Standard, Internet Standard][13], [Informational, Experimental or Historic][14])? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? Proposed Standard as indicated on the title page header and in the datatracker. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in [BCP 79][7]? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. All authors and contributors confirmed that they are not aware of any IPR related to this draft. 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. The total number of authors of this specification are 5. 14. Document any remaining I-D nits in this document. Simply running the [idnits tool][8] is not enough; please review the ["Content Guidelines" on authors.ietf.org][15]. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) IDnits reported issues and it will be fixed in the next revision. 15. Should any informative references be normative or vice-versa? See the [IESG Statement on Normative and Informative References][16]. None. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? None. 17. Are there any normative downward references (see [RFC 3967][9] and [BCP 97][10]) that are not already listed in the [DOWNREF registry][17]? If so, list them. None. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? a) draft-ietf-rats-eat: submitted to IESG b) draft-ietf-suit-manifest: submitted to IESG c) draft-ietf-suit-trust-domains: WGLC done, revised I-D needed d) draft-ietf-suit-mti: getting ready for WGLC e) draft-ietf-suit-report: getting ready for WGLC 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. No, publication of this document will not change the status of any existing RFCs. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see [RFC 8126][11]). It requests IANA to assign a media type for "application/teep+cbor". 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. Not applicable [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ |
2023-07-19
|
15 | Tirumaleswar Reddy.K | Title: Trusted Execution Environment Provisioning (TEEP) Protocol Current Version: https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol-15 ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of … Title: Trusted Execution Environment Provisioning (TEEP) Protocol Current Version: https://datatracker.ietf.org/doc/html/draft-ietf-teep-protocol-15 ## Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? The draft was adopted in Dec, 2017 with good WG support for adoption. It has been thoroughly reviewed by working group members. The authors have given updates on progress of the draft during all of the WG meetings. A number of detailed reviews of the document were posted to the working group mailing list, along with the issues and pull requests logged on GitHub. Further, there has been active participation in IETF Hackathon activities from WG members to implement, test and interop TEEP protocol. The authors of this document have extensive experience with the TEE technologies and implementations. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? No, there was no controversy about any points in the draft. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) There are no open issues that I am aware of, nor any other outstanding areas of concern, nor are there any known issues of extreme discontent or conflict. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as [RFC 7942][3] recommends) or elsewhere (where)? Multiple open source code repositories of the TEEP protocol is available and are listed in the "Additional resources" Section of https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/. The protocol was implemented and interop was done during IETF hackathons to identify and fix issues. IETF hackathon reports were presented in the WG meetings. ## Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The TEEP protocol uses CBOR and relies on COSE for security. It leverages the work in SUIT (SUIT manifest format is used) and RATS (EAT format is used) WGs. The draft has been reviewed by members actively contributing to these working groups. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. No. 7. If the document contains a YANG module, has the final version of the module been checked with any of the [recommended validation tools][4] for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in [RFC 8342][5]? No. 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. Yes, CBOR's CDDL validation was done for every commit (see https://github.com/ietf-teep/teep-protocol) ## Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? Yes, it is ready to be handed off to the responsible AD. 10. Several IETF Areas have assembled [lists of common issues that their reviewers encounter][6]. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent reviews? This draft requires reviews from SECDIR and IOTDIR representatives. 11. What type of RFC publication is being requested on the IETF stream ([Best Current Practice][12], [Proposed Standard, Internet Standard][13], [Informational, Experimental or Historic][14])? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? Proposed Standard as indicated on the title page header and in the datatracker. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in [BCP 79][7]? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. All authors and contributors confirmed that they are not aware of any IPR related to this draft. 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. The total number of authors of this specification are 5. 14. Document any remaining I-D nits in this document. Simply running the [idnits tool][8] is not enough; please review the ["Content Guidelines" on authors.ietf.org][15]. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) IDnits reported issues and it will be fixed in the next revision. 15. Should any informative references be normative or vice-versa? See the [IESG Statement on Normative and Informative References][16]. None. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? None. 17. Are there any normative downward references (see [RFC 3967][9] and [BCP 97][10]) that are not already listed in the [DOWNREF registry][17]? If so, list them. None. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? a)ietf-rats-eat: ready for submit to ISEG for review b)suit-manifest : WGLC is complete, AD review c)suit-mti : WG document d)suit-report : WG document e)suit-trust-domains : In WGLC 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. No, publication of this document will not change the status of any existing RFCs. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see [RFC 8126][11]). It requests IANA to assign a media type for "application/teep+cbor". 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. Not applicable [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ [1]: https://www.ietf.org/about/groups/iesg/ [2]: https://www.rfc-editor.org/rfc/rfc4858.html [3]: https://www.rfc-editor.org/rfc/rfc7942.html [4]: https://wiki.ietf.org/group/ops/yang-review-tools [5]: https://www.rfc-editor.org/rfc/rfc8342.html [6]: https://wiki.ietf.org/group/iesg/ExpertTopics [7]: https://www.rfc-editor.org/info/bcp79 [8]: https://www.ietf.org/tools/idnits/ [9]: https://www.rfc-editor.org/rfc/rfc3967.html [10]: https://www.rfc-editor.org/info/bcp97 [11]: https://www.rfc-editor.org/rfc/rfc8126.html [12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5 [13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1 [14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2 [15]: https://authors.ietf.org/en/content-guidelines-overview [16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/ [17]: https://datatracker.ietf.org/doc/downref/ |
2023-07-19
|
15 | Tirumaleswar Reddy.K | Notification list changed to kondtir@gmail.com because the document shepherd was set |
2023-07-19
|
15 | Tirumaleswar Reddy.K | Document shepherd changed to Tirumaleswar Reddy.K |
2023-07-11
|
15 | Tirumaleswar Reddy.K | Changed consensus to Yes from Unknown |
2023-07-11
|
15 | Tirumaleswar Reddy.K | Intended Status changed to Proposed Standard from None |
2023-07-03
|
15 | Akira Tsukamoto | New version available: draft-ietf-teep-protocol-15.txt |
2023-07-03
|
15 | (System) | New version approved |
2023-07-03
|
15 | (System) | Request for posting confirmation emailed to previous authors: Akira Tsukamoto , Dave Thaler , David Wheeler , Hannes Tschofenig , Mingliang Pei , teep-chairs@ietf.org |
2023-07-03
|
15 | Akira Tsukamoto | Uploaded new revision |
2023-06-19
|
14 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-14.txt |
2023-06-19
|
14 | Hannes Tschofenig | New version accepted (logged-in submitter: Hannes Tschofenig) |
2023-06-19
|
14 | Hannes Tschofenig | Uploaded new revision |
2023-06-06
|
13 | Tirumaleswar Reddy.K | IETF WG state changed to WG Consensus: Waiting for Write-Up from WG Document |
2023-05-01
|
13 | Dave Thaler | New version available: draft-ietf-teep-protocol-13.txt |
2023-05-01
|
13 | Dave Thaler | New version accepted (logged-in submitter: Dave Thaler) |
2023-05-01
|
13 | Dave Thaler | Uploaded new revision |
2023-03-13
|
12 | Dave Thaler | New version available: draft-ietf-teep-protocol-12.txt |
2023-03-13
|
12 | Dave Thaler | New version accepted (logged-in submitter: Dave Thaler) |
2023-03-13
|
12 | Dave Thaler | Uploaded new revision |
2022-10-24
|
11 | Dave Thaler | New version available: draft-ietf-teep-protocol-11.txt |
2022-10-24
|
11 | Dave Thaler | New version accepted (logged-in submitter: Dave Thaler) |
2022-10-24
|
11 | Dave Thaler | Uploaded new revision |
2022-07-28
|
10 | Dave Thaler | New version available: draft-ietf-teep-protocol-10.txt |
2022-07-28
|
10 | Dave Thaler | New version accepted (logged-in submitter: Dave Thaler) |
2022-07-28
|
10 | Dave Thaler | Uploaded new revision |
2022-07-27
|
09 | Tirumaleswar Reddy.K | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep (C Implementation: TEEP protocol and HTTP transport for TEEP) related_implementations https://github.com/ko-isobe/tamproto/ … Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep (C Implementation: TEEP protocol and HTTP transport for TEEP) related_implementations https://github.com/ko-isobe/tamproto/ (TAM server functionality) related_implementations https://github.com/yuichitk/libteep/ (C Implementation for encoding/decoding TEEP Protocol messages) |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (\n https://github.com/dthaler/teep) to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (<https://github.com/yuichitk/libteep/>) to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (\n https://github.com/dthaler/teep) |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (https://github.com/yuichitk/libteep/) to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (<https://github.com/yuichitk/libteep/>) |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep () to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep (https://github.com/yuichitk/libteep/) |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol (\n https://github.com/dthaler/teep) related_implementations https://github.com/yuichitk/libteep to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep () |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep to: github_repo https://github.com/ietf-teep/teep-protocol (\n https://github.com/dthaler/teep) related_implementations https://github.com/yuichitk/libteep |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/yuichitk/libteep |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep () to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep |
2022-07-27
|
09 | Nancy Cam-Winget | Changed document external resources from: github_repo https://github.com/ietf-teep/teep-protocol to: github_repo https://github.com/ietf-teep/teep-protocol related_implementations https://github.com/dthaler/teep () |
2022-07-11
|
09 | Dave Thaler | New version available: draft-ietf-teep-protocol-09.txt |
2022-07-11
|
09 | (System) | New version approved |
2022-07-11
|
09 | (System) | Request for posting confirmation emailed to previous authors: Akira Tsukamoto , Dave Thaler , David Wheeler , Hannes Tschofenig , Mingliang Pei |
2022-07-11
|
09 | Dave Thaler | Uploaded new revision |
2022-03-07
|
08 | Dave Thaler | New version available: draft-ietf-teep-protocol-08.txt |
2022-03-07
|
08 | (System) | New version accepted (logged-in submitter: Dave Thaler) |
2022-03-07
|
08 | Dave Thaler | Uploaded new revision |
2021-10-25
|
07 | Dave Thaler | New version available: draft-ietf-teep-protocol-07.txt |
2021-10-25
|
07 | (System) | New version approved |
2021-10-25
|
07 | (System) | Request for posting confirmation emailed to previous authors: Akira Tsukamoto , Dave Thaler , David Wheeler , Hannes Tschofenig , Mingliang Pei |
2021-10-25
|
07 | Dave Thaler | Uploaded new revision |
2021-07-28
|
06 | Nancy Cam-Winget | Changed document external resources from: None to: github_repo https://github.com/ietf-teep/teep-protocol |
2021-07-12
|
06 | Dave Thaler | New version available: draft-ietf-teep-protocol-06.txt |
2021-07-12
|
06 | (System) | New version approved |
2021-07-12
|
06 | (System) | Request for posting confirmation emailed to previous authors: Akira Tsukamoto , Dave Thaler , David Wheeler , Hannes Tschofenig , Mingliang Pei , teep-chairs@ietf.org |
2021-07-12
|
06 | Dave Thaler | Uploaded new revision |
2021-02-22
|
05 | Dave Thaler | New version available: draft-ietf-teep-protocol-05.txt |
2021-02-22
|
05 | (System) | New version approved |
2021-02-22
|
05 | (System) | Request for posting confirmation emailed to previous authors: Akira Tsukamoto , Dave Thaler , David Wheeler , Hannes Tschofenig , Mingliang Pei |
2021-02-22
|
05 | Dave Thaler | Uploaded new revision |
2020-11-02
|
04 | Dave Thaler | New version available: draft-ietf-teep-protocol-04.txt |
2020-11-02
|
04 | (System) | New version accepted (logged-in submitter: Dave Thaler) |
2020-11-02
|
04 | Dave Thaler | Uploaded new revision |
2020-07-13
|
03 | Dave Thaler | New version available: draft-ietf-teep-protocol-03.txt |
2020-07-13
|
03 | (System) | New version approved |
2020-07-13
|
03 | (System) | Request for posting confirmation emailed to previous authors: David Wheeler , Dave Thaler , Hannes Tschofenig , Mingliang Pei , Akira Tsukamoto |
2020-07-13
|
03 | Dave Thaler | Uploaded new revision |
2020-04-14
|
02 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-02.txt |
2020-04-14
|
02 | (System) | New version approved |
2020-04-14
|
02 | (System) | Request for posting confirmation emailed to previous authors: Dave Thaler , teep-chairs@ietf.org, David Wheeler , Mingliang Pei , Hannes Tschofenig |
2020-04-14
|
02 | Hannes Tschofenig | Uploaded new revision |
2020-03-09
|
01 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-01.txt |
2020-03-09
|
01 | (System) | New version approved |
2020-03-09
|
01 | (System) | Request for posting confirmation emailed to previous authors: Hannes Tschofenig , Dave Thaler , Mingliang Pei , David Wheeler |
2020-03-09
|
01 | Hannes Tschofenig | Uploaded new revision |
2019-12-12
|
00 | Tirumaleswar Reddy.K | This document now replaces draft-tschofenig-teep-protocol instead of draft-tschofenig-teep-protocol |
2019-12-12
|
00 | Tirumaleswar Reddy.K | This document now replaces draft-tschofenig-teep-protocol instead of draft-tschofenig-teep-protocol |
2019-12-12
|
00 | Tirumaleswar Reddy.K | This document now replaces draft-tschofenig-teep-protocol instead of None |
2019-12-12
|
00 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-00.txt |
2019-12-12
|
00 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-00.txt |
2019-12-12
|
00 | (System) | WG -00 approved |
2019-12-12
|
00 | (System) | WG -00 approved |
2019-12-12
|
00 | Hannes Tschofenig | New version available: draft-ietf-teep-protocol-00.txt |
2019-12-12
|
00 | (System) | WG -00 approved |
2019-12-07
|
00 | Hannes Tschofenig | Set submitter to "Hannes Tschofenig ", replaces to draft-tschofenig-teep-protocol and sent approval email to group chairs: teep-chairs@ietf.org |
2019-12-07
|
00 | Hannes Tschofenig | Set submitter to "Hannes Tschofenig ", replaces to draft-tschofenig-teep-protocol and sent approval email to group chairs: teep-chairs@ietf.org |
2019-12-07
|
00 | Hannes Tschofenig | Set submitter to "Hannes Tschofenig ", replaces to draft-tschofenig-teep-protocol and sent approval email to group chairs: teep-chairs@ietf.org |
2019-12-07
|
00 | Hannes Tschofenig | Uploaded new revision |
2019-12-07
|
00 | Hannes Tschofenig | Uploaded new revision |
2019-12-07
|
00 | Hannes Tschofenig | Uploaded new revision |