Draft: draft-ietf-core-resource-directory

Commentary: This should catch users of either term , without moving away from   in use cases where it might be the more popular term within the field ( car park management , building automation ) . Closes : 
 From : If we want to change that , the M2 M ( machine to machine ) references would largely be replaced with IoT ( Internet of Things ) in abstract , introduction and use cases ( LWM2 M obviously unaffected ) , where " new users : machines " could be replaced with " new users : devices without physical operator interaction " . you wrote those texts and are probably more up to date with widespread terminology than I am – keep or change ? 
 I do n't care too much about this terminology . IoT or LWM2 M are used to address a market segment . From that point of view we need to keep them both ,
Paragraph (version A):
In the work on Constrained RESTful Environments (CoRE), a REST
architecture suitable for constrained nodes (e.g. with limited RAM
and ROM RFC7228) and networks (e.g. 6LoWPAN RFC4944) has been
established and is used in machine-to-machine (M2M) applications such
as smart energy and building automation.
Paragraph (version B):
In the work on Constrained RESTful Environments (CoRE), a REST
architecture suitable for constrained nodes (e.g. with limited RAM
and ROM RFC7228) and networks (e.g. 6LoWPAN RFC4944) has been
established and is used in Internet-of-Things (IoT) or machine-to-
machine (M2M) applications such as smart energy and building
automation.
Paragraph (version A):
The discovery of resources offered by a constrained server is very
important in machine-to-machine applications where there are no
humans in the loop and static interfaces result in fragility.  The
discovery of resources provided by an HTTP Web Server is typically
called Web Linking RFC8288.  The use of Web Linking for the
description and discovery of resources hosted by constrained web
servers is specified by the CoRE Link Format RFC6690.  However,
RFC6690 only describes how to discover resources from the web server
that hosts them by querying "/.well-known/core".  In many M2M
scenarios, direct discovery of resources is not practical due to
sleeping nodes, disperse networks, or networks where multicast
traffic is inefficient.  These problems can be solved by employing an
entity called a Resource Directory (RD), which contains information
about resources held on other servers, allowing lookups to be
performed for those resources.
Paragraph (version B):
The discovery of resources offered by a constrained server is very
important in machine-to-machine applications where there are no
humans in the loop and static interfaces result in fragility.  The
discovery of resources provided by an HTTP Web Server is typically
called Web Linking RFC8288.  The use of Web Linking for the
description and discovery of resources hosted by constrained web
servers is specified by the CoRE Link Format RFC6690.  However,
RFC6690 only describes how to discover resources from the web server
that hosts them by querying "/.well-known/core".  In many constrained
scenarios, direct discovery of resources is not practical due to
sleeping nodes, disperse networks, or networks where multicast
traffic is inefficient.  These problems can be solved by employing an
entity called a Resource Directory (RD), which contains information
about resources held on other servers, allowing lookups to be
performed for those resources.