--- 1/draft-ietf-roll-terminology-10.txt 2013-02-20 21:19:53.171876804 +0100 +++ 2/draft-ietf-roll-terminology-11.txt 2013-02-20 21:19:53.187875414 +0100 @@ -1,18 +1,18 @@ Networking Working Group JP. Vasseur Internet-Draft Cisco Systems, Inc -Intended status: Informational January 31, 2013 -Expires: August 4, 2013 +Intended status: Informational February 16, 2013 +Expires: August 20, 2013 Terminology in Low power And Lossy Networks - draft-ietf-roll-terminology-10.txt + draft-ietf-roll-terminology-11.txt Abstract The documents defines a terminology for discussing routing requirements and solutions for networks referred to as Low power and Lossy Networks (LLN). A LLN is typically composed of many embedded devices with limited power, memory, and processing resources interconnected by a variety of links. There is a wide scope of application areas for LLNs, including industrial monitoring, building automation (e.g. Heating, Ventilating, Air Conditioning, lighting, @@ -34,21 +34,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on August 4, 2013. + This Internet-Draft will expire on August 20, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -282,20 +282,22 @@ 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 6.2. Informative References + [HART] HART Communication Foundation (http://www.hartcomm.org) + [RFC4461] Yasukawa, S., "Signaling Requirements for Point-to- Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs)", RFC 4461, April 2006. [RFC4875] Aggarwal, R., Papadimitriou, D., and S. Yasukawa, "Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)", RFC 4875, May 2007. [RFC5548] Dohler, M., Watteyne, T., Winter, T., and D. Barthel,