Terminology for Constrained-Node Networks
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: RFC Editor <email@example.com>, lwig mailing list <firstname.lastname@example.org>, lwig chair <email@example.com> Subject: Document Action: 'Terminology for Constrained Node Networks' to Informational RFC (draft-ietf-lwig-terminology-07.txt) The IESG has approved the following document: - 'Terminology for Constrained Node Networks' (draft-ietf-lwig-terminology-07.txt) as Informational RFC This document is the product of the Light-Weight Implementation Guidance Working Group. The IESG contact persons are Brian Haberman and Ted Lemon. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-lwig-terminology/
Technical Summary The Internet Protocol Suite is increasingly used on small devices with severe constraints, creating constrained node networks. This document provides a number of basic terms that have turned out to be useful in the standardization work for constrained environments. Working Group Summary The document originally was extracted as a stable part of the LWIG guidance document that the WG considered to be immediately useful. After extraction, additional terminology was added on energy/power availability and usage. This document was finished collectively by a number of people who worked in the constrained network area. The WGLC was conducted on April 7 for two weeks. Five supports have been expressed on the mailing list, with positive discussion. Document Quality This is a document that summarizes the terminologies that has been and will be used for people and groups that are working on constrained networks. This is generally considered to be a useful document for people to refer when they would like to find the definition of certain terms. Experts from Philips, Orange, Ericsson reviewed the document, from the time when it still was an individual document. Several wording details in the draft before the WGLC had been discussed and the draft was updated to incorporate these changes. Personnel Zhen Cao (firstname.lastname@example.org) is the Document Shepherd. Brian Haberman is the Responsible AD.