IPv6 over Constrained Node Networks (6lo) Applicability & Use cases
draft-ietf-6lo-use-cases-12
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2022-04-06
|
12 | (System) | IESG state changed to Waiting for Writeup from In Last Call |
|
2022-04-05
|
12 | Peter Yee | Request for Last Call review by GENART Completed: Ready with Issues. Reviewer: Peter Yee. Sent review to list. |
|
2022-04-05
|
12 | Robert Sparks | Request for Last Call review by SECDIR Completed: Has Issues. Reviewer: Robert Sparks. Review has been revised by Robert Sparks. |
|
2022-04-05
|
12 | Robert Sparks | Request for Last Call review by SECDIR Completed: Has Issues. Reviewer: Robert Sparks. Sent review to list. |
|
2022-03-28
|
12 | (System) | IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed |
|
2022-03-28
|
12 | (System) | (Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs: The IANA Functions Operator has reviewed draft-ietf-6lo-use-cases-12, which is currently in Last Call, and has the following comments: We … (Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs: The IANA Functions Operator has reviewed draft-ietf-6lo-use-cases-12, which is currently in Last Call, and has the following comments: We understand that this document doesn't require any registry actions. While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object. If this assessment is not accurate, please respond as soon as possible. Thank you, Michelle Thangtamsatid IANA Services Specialist |
|
2022-03-25
|
12 | Jean Mahoney | Request for Last Call review by GENART is assigned to Peter Yee |
|
2022-03-25
|
12 | Jean Mahoney | Request for Last Call review by GENART is assigned to Peter Yee |
|
2022-03-24
|
12 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Robert Sparks |
|
2022-03-24
|
12 | Tero Kivinen | Request for Last Call review by SECDIR is assigned to Robert Sparks |
|
2022-03-24
|
12 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Fred Baker |
|
2022-03-24
|
12 | Gunter Van de Velde | Request for Last Call review by OPSDIR is assigned to Fred Baker |
|
2022-03-23
|
12 | Cindy Morgan | IANA Review state changed to IANA - Review Needed |
|
2022-03-23
|
12 | Cindy Morgan | The following Last Call announcement was sent out (ends 2022-04-06):<br><br>From: The IESG <iesg-secretary@ietf.org> To: IETF-Announce <ietf-announce@ietf.org> CC: 6lo-chairs@ietf.org, 6lo@ietf.org, … The following Last Call announcement was sent out (ends 2022-04-06):<br><br>From: The IESG <iesg-secretary@ietf.org> To: IETF-Announce <ietf-announce@ietf.org> CC: 6lo-chairs@ietf.org, 6lo@ietf.org, draft-ietf-6lo-use-cases@ietf.org, ek.ietf@gmail.com, shwetha.bhandari@gmail.com Reply-To: last-call@ietf.org Sender: <iesg-secretary@ietf.org> Subject: Last Call: <draft-ietf-6lo-use-cases-12.txt> (IPv6 over Constrained Node Networks (6lo) Applicability & Use cases) to Informational RFC The IESG has received a request from the IPv6 over Networks of Resource-constrained Nodes WG (6lo) to consider the following document: - 'IPv6 over Constrained Node Networks (6lo) Applicability & Use cases' <draft-ietf-6lo-use-cases-12.txt> as Informational RFC 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 2022-04-06. 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 This document describes the applicability of IPv6 over constrained node networks (6lo) and provides practical deployment examples. In addition to IEEE Std 802.15.4, various link layer technologies such as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy, DECT-ULE, MS/TP, NFC, and PLC are used as examples. The document targets an audience who would like to understand and evaluate running end-to-end IPv6 over the constrained node networks for local or Internet connectivity. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-6lo-use-cases/ No IPR declarations have been submitted directly on this I-D. |
|
2022-03-23
|
12 | Cindy Morgan | IESG state changed to In Last Call from Last Call Requested |
|
2022-03-23
|
12 | Cindy Morgan | Last call announcement was generated |
|
2022-03-22
|
12 | Erik Kline | Changed consensus to Yes from Unknown |
|
2022-03-22
|
12 | Erik Kline | Last call was requested |
|
2022-03-22
|
12 | Erik Kline | Last call announcement was generated |
|
2022-03-22
|
12 | Erik Kline | Ballot approval text was generated |
|
2022-03-22
|
12 | Erik Kline | Ballot writeup was generated |
|
2022-03-22
|
12 | Erik Kline | IESG state changed to Last Call Requested from AD Evaluation::AD Followup |
|
2022-03-22
|
12 | Erik Kline | # Internet AD comments for draft-ietf-6lo-use-cases-12 CC @ekline This is an attempt to provide review using [this syntaxt]( https://github.com/mnot/ietf-comments/blob/main/format.md), but likely has formatting issues. … # Internet AD comments for draft-ietf-6lo-use-cases-12 CC @ekline This is an attempt to provide review using [this syntaxt]( https://github.com/mnot/ietf-comments/blob/main/format.md), but likely has formatting issues. Below are some comments to consider, but none of them are strong enough to warrant waiting any further for moving to IETF LC. Please consider them, but with no special urgency relative to, say, other LC comments. Thanks! ## Comments ### blemesh? Should blemesh get a mention in here? Perhaps it's not relevant; I don't know. ### S3, Addressing Model privacy recommendations In addition to the reference to RFC 8065, consider whether any of RFCs 7217, 7721, 8064, and 8981 are applicable or worth mentioning. ### S4.3, "massive deployments" Making a claim like "has got massive deployments" invites the reader to ask "where is the citation for this?" If there is a citation to add here, that might be helpful. ### S5.5, /senior citizen/patient (in general)/? I wonder if "senior citizen" is important, or if the same statements are all equally compelling for any patient. ### S5.5, don't tempt the security dragons I'm no security expert, but a strong statement like "cannot gather the personal data" might require an equally strong reference. Maybe just "cannot as easily gather"? |
|
2022-03-22
|
12 | Erik Kline | IESG state changed to AD Evaluation::AD Followup from AD Evaluation |
|
2022-02-09
|
12 | Erik Kline | IESG state changed to AD Evaluation from Publication Requested |
|
2022-02-09
|
12 | (System) | Changed action holders to Erik Kline (IESG state changed) |
|
2022-02-09
|
12 | Erik Kline | Responsible AD changed to Erik Kline |
|
2022-02-09
|
12 | Erik Kline | Intended Status changed to Informational |
|
2022-02-09
|
12 | Erik Kline | IESG process started in state Publication Requested |
|
2022-02-09
|
12 | Erik Kline | Working group state set to Submitted to IESG for Publication |
|
2022-02-09
|
12 | Erik Kline | Mailarchive search link: https://mailarchive.ietf.org/arch/browse/6lo/?q=draft-ietf-6lo-use-cases |
|
2022-02-09
|
12 | Erik Kline | IETF WG state changed to Submitted to IESG for Publication from In WG Last Call |
|
2022-01-28
|
12 | Shwetha Bhandari | As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated … As required by RFC 4858, this is the current template for the Document Shepherd Write-Up. Changes are expected over time. This version is dated 1 November 2019. (1) What type of RFC is being requested (BCP, Proposed Standard, Internet Standard, Informational, Experimental, or Historic)? Why is this the proper type of RFC? Is this type of RFC indicated in the title page header? Informational (2) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up. Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary: This document describes the applicability of IPv6 over constrained node networks (6lo) and provides practical deployment examples. In addition to IEEE Std 802.15.4, various link layer technologies such as ITU-T G.9959 (Z-Wave), Bluetooth Low Energy, DECT-ULE, MS/TP, NFC, and PLC are used as examples. The document targets an audience who would like to understand and evaluate running end-to-end IPv6 over the constrained node networks for local or Internet connectivity. Working Group Summary: The discussion and evolution of the document has been smooth with workgroup consensus. It is worth noting that the draft was adopted in 2016 and has evolved to include 6lo use cases over this period of time. Document Quality: This is an Informational draft describing use cases and examples of 6lo deployments. It described various IETF and IEEE developed standards in the examples. The following work group participants have done reviews and provided feedback to help shape the document: Thomas Watteyne, Pascal Thubert, Xavier Vilajosana, Daniel Migault, Jianqiang Hou, Kerry Lynn, S.V.R. Anand, Seyed Mahdi Darroudi and Tero kivinen have provided valuable feedback for this draft. Personnel: Who is the Document Shepherd? Shwetha Bhandari Who is the Responsible Area Director? Erik Kline (3) Briefly describe the review of this document that was performed by the Document Shepherd. If this version of the document is not ready for publication, please explain why the document is being forwarded to the IESG. I have read the document and based on the publicly available reference material it appears to capture the use cases and example accurately. It is ready for publication. (4) Does the document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? No concerns (5) Do portions of the document need review from a particular or from broader perspective, e.g., security, operational complexity, AAA, DNS, DHCP, XML, or internationalization? If so, describe the review that took place. No (6) Describe any specific concerns or issues that the Document Shepherd has with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. No concerns. (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why? Yes. (8) Has an IPR disclosure been filed that references this document? If so, summarize any WG discussion and conclusion regarding the IPR disclosures. No IPR was disclosed related to this draft. (9) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? The workgroup as a whole agrees to publish this Informational document. (10) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise 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.) None. (11) Identify any ID nits the Document Shepherd has found in this document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts Checklist). Boilerplate checks are not enough; this check needs to be thorough. Table 2 in Section 2.7 has the following nit: ** There are 35 instances of too long lines in the document, the longest one being 4 characters in excess of 72. (12) Describe how the document meets any required formal review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. Not applicable (13) Have all references within this document been identified as either normative or informative? Yes. (14) Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the plan for their completion? None (15) Are there downward normative references (see RFC 3967)? If so, list these downward references to support the Area Director in the Last Call procedure. None. (16) Will publication of this document change the status of any existing RFCs? Are those RFCs listed on the title page header, listed in the abstract, and discussed in the introduction? If the RFCs are not listed in the Abstract and Introduction, explain why, and point to the part of the document where the relationship of this document to the other RFCs is discussed. If this information is not in the document, explain why the WG considers it unnecessary. No, this document will not influence status of any existing documents, (17) 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 protocol extensions that the document makes are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a reasonable name for the new registry has been suggested (see RFC 8126). No IANA considerations. (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find useful in selecting the IANA Experts for these new registries. No IANA considerations. (19) Describe reviews and automated checks performed by the Document Shepherd to validate sections of the document written in a formal language, such as XML code, BNF rules, MIB definitions, YANG modules, etc. No formal language in this draft. (20) If the document contains a YANG module, has the module been checked with any of the recommended validation tools (https://trac.ietf.org/trac/ops/wiki/yang-review-tools) 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 RFC8342? No yang module in the draft. |
|
2022-01-25
|
12 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-12.txt |
|
2022-01-25
|
12 | (System) | New version approved |
|
2022-01-25
|
12 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, Yong-Geun Hong <yonggeun.hong@gmail.com> |
|
2022-01-25
|
12 | Yong-Geun Hong | Uploaded new revision |
|
2022-01-24
|
11 | Shwetha Bhandari | Notification list changed to Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, shwetha.bhandari@gmail.com from Gabriel Montenegro <Gabriel.Montenegro@microsoft.com> because the document shepherd was set |
|
2022-01-24
|
11 | Shwetha Bhandari | Document shepherd changed to Shwetha Bhandari |
|
2022-01-13
|
11 | (System) | Document has expired |
|
2021-07-12
|
11 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-11.txt |
|
2021-07-12
|
11 | (System) | New version approved |
|
2021-07-12
|
11 | (System) | Request for posting confirmation emailed to previous authors: Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, Yong-Geun Hong … Request for posting confirmation emailed to previous authors: Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, Yong-Geun Hong <yonggeun.hong@gmail.com> |
|
2021-07-12
|
11 | Yong-Geun Hong | Uploaded new revision |
|
2021-02-21
|
10 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-10.txt |
|
2021-02-21
|
10 | (System) | New version approved |
|
2021-02-21
|
10 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Yong-Geun Hong <YGHONG@ETRI.RE.KR> |
|
2021-02-21
|
10 | Yong-Geun Hong | Uploaded new revision |
|
2021-02-21
|
10 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Yong-Geun Hong <YGHONG@ETRI.RE.KR> |
|
2021-02-21
|
10 | Yong-Geun Hong | Uploaded new revision |
|
2021-01-14
|
09 | (System) | Document has expired |
|
2020-07-13
|
09 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-09.txt |
|
2020-07-13
|
09 | (System) | New version approved |
|
2020-07-13
|
09 | (System) | Request for posting confirmation emailed to previous authors: Take Aanstoot <take@modio.se>, Samita Chakrabarti <samitac.ietf@gmail.com>, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Abdur Sangi … Request for posting confirmation emailed to previous authors: Take Aanstoot <take@modio.se>, Samita Chakrabarti <samitac.ietf@gmail.com>, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Abdur Sangi <sangi_bahrian@yahoo.com>, 6lo-chairs@ietf.org, Carles Gomez <carlesgo@entel.upc.edu> |
|
2020-07-13
|
09 | Yong-Geun Hong | Uploaded new revision |
|
2020-05-07
|
08 | (System) | Document has expired |
|
2019-11-04
|
08 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-08.txt |
|
2019-11-04
|
08 | (System) | New version approved |
|
2019-11-04
|
08 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2019-11-04
|
08 | Yong-Geun Hong | Uploaded new revision |
|
2019-09-10
|
07 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-07.txt |
|
2019-09-10
|
07 | (System) | New version approved |
|
2019-09-10
|
07 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2019-09-10
|
07 | Yong-Geun Hong | Uploaded new revision |
|
2019-03-11
|
06 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-06.txt |
|
2019-03-11
|
06 | (System) | New version approved |
|
2019-03-11
|
06 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2019-03-11
|
06 | Yong-Geun Hong | Uploaded new revision |
|
2019-01-02
|
05 | (System) | Document has expired |
|
2018-11-04
|
05 | Gabriel Montenegro | IETF WG state changed to In WG Last Call from WG Document |
|
2018-07-01
|
05 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-05.txt |
|
2018-07-01
|
05 | (System) | New version approved |
|
2018-07-01
|
05 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2018-07-01
|
05 | Yong-Geun Hong | Uploaded new revision |
|
2018-05-31
|
04 | Gabriel Montenegro | Notification list changed to Gabriel Montenegro <Gabriel.Montenegro@microsoft.com> |
|
2018-05-31
|
04 | Gabriel Montenegro | Document shepherd changed to Gabriel Montenegro |
|
2018-03-05
|
04 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-04.txt |
|
2018-03-05
|
04 | (System) | New version approved |
|
2018-03-05
|
04 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2018-03-05
|
04 | Yong-Geun Hong | Uploaded new revision |
|
2017-10-30
|
03 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-03.txt |
|
2017-10-30
|
03 | (System) | New version approved |
|
2017-10-30
|
03 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, … Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Yong-Geun Hong <YGHONG@ETRI.RE.KR>, Samita Chakrabarti <samitac.ietf@gmail.com>, Take Aanstoot <take@modio.se>, Abdur Sangi <sangi_bahrian@yahoo.com>, Carles Gomez <carlesgo@entel.upc.edu> |
|
2017-10-30
|
03 | Yong-Geun Hong | Uploaded new revision |
|
2017-07-03
|
02 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-02.txt |
|
2017-07-03
|
02 | (System) | New version approved |
|
2017-07-03
|
02 | (System) | Request for posting confirmation emailed to previous authors: Abdur Sangi <rashid.sangi@huawei.com>, Take Aanstoot <take@modio.se>, 6lo-chairs@ietf.org, Carles Gomez <carlesgo@entel.upc.edu>, … Request for posting confirmation emailed to previous authors: Abdur Sangi <rashid.sangi@huawei.com>, Take Aanstoot <take@modio.se>, 6lo-chairs@ietf.org, Carles Gomez <carlesgo@entel.upc.edu>, Yong-Geun Hong <YGHONG@ETRI.RE.KR> |
|
2017-07-03
|
02 | Yong-Geun Hong | Uploaded new revision |
|
2017-03-13
|
01 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-01.txt |
|
2017-03-13
|
01 | (System) | New version approved |
|
2017-03-13
|
01 | (System) | Request for posting confirmation emailed to previous authors: 6lo-chairs@ietf.org, Carles Gomez <carlesgo@entel.upc.edu>, Yong-Geun Hong <YGHONG@ETRI.RE.KR> |
|
2017-03-13
|
01 | Yong-Geun Hong | Uploaded new revision |
|
2016-12-02
|
00 | Yong-Geun Hong | New version available: draft-ietf-6lo-use-cases-00.txt |
|
2016-12-02
|
00 | (System) | WG -00 approved |
|
2016-11-29
|
00 | Yong-Geun Hong | Set submitter to "Yong-Geun Hong <yghong@etri.re.kr>", replaces to (none) and sent approval email to group chairs: 6lo-chairs@ietf.org |
|
2016-11-29
|
00 | Yong-Geun Hong | Uploaded new revision |