Changeset 23


Ignore:
Timestamp:
Jul 4, 2013, 7:04:06 AM (6 years ago)
Author:
kovatsch@…
Message:

Added reference to new draft-kovatsch-lwig-coap.

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-hex-lwig-energy-efficient.mkd

    r22 r23  
    5656informative:
    5757  I-D.ietf-lwig-terminology:
    58   I-D.kovatsch-lwig-class1-coap:
     58  I-D.kovatsch-lwig-coap:
    5959  I-D.arkko-core-sleepy-sensors:
    6060  I-D.vial-core-mirror-proxy:
     
    178178be more energy-efficient.  Only few efforts were spent on energy-
    179179efficient designs for IETF protocols and standardized network stacks
    180 for such constrained devices {{I-D.kovatsch-lwig-class1-coap}}.
     180for such constrained devices {{I-D.kovatsch-lwig-coap}}.
    181181
    182182The IETF has developed a suite of Internet protocols suitable for
  • draft-hex-lwig-energy-efficient.xml

    r22 r23  
    105105be more energy-efficient.  Only few efforts were spent on energy-
    106106efficient designs for IETF protocols and standardized network stacks
    107 for such constrained devices <xref target="I-D.kovatsch-lwig-class1-coap"/>.</t>
     107for such constrained devices <xref target="I-D.kovatsch-lwig-coap"/>.</t>
    108108
    109109<t>The IETF has developed a suite of Internet protocols suitable for
     
    677677
    678678
    679 <reference anchor='I-D.kovatsch-lwig-class1-coap'>
    680 <front>
    681 <title>Implementing CoAP for Class 1 Devices</title>
     679<reference anchor='I-D.kovatsch-lwig-coap'>
     680<front>
     681<title>CoAP Implementation Guidance</title>
    682682
    683683<author initials='M' surname='Kovatsch' fullname='Matthias Kovatsch'>
     
    685685</author>
    686686
    687 <date month='October' day='15' year='2012' />
    688 
    689 <abstract><t>The Constrained Application Protocol (CoAP) is designed for resource-constrained nodes and networks, e.g., sensor nodes in low-power lossy networks (LLNs). Still, to implement this Internet protocol on Class 1 devices, i.e., ~10KiB of RAM and ~100KiB of ROM, light-weight implementation techniques are necessary. This document provides the lessons learned from implementing CoAP for Contiki, an operating system for tiny, battery-operated networked embedded systems. The information may become part of the Light-Weight Implementation Guidance document planned by the IETF working group LWIG.</t></abstract>
     687<author initials='O' surname='Bergmann' fullname='Olaf Bergmann'>
     688    <organization />
     689</author>
     690
     691<author initials='A' surname='Castellani' fullname='Angelo Castellani'>
     692    <organization />
     693</author>
     694
     695<author initials='E' surname='Dijk' fullname='Esko Dijk'>
     696    <organization />
     697</author>
     698
     699<author initials='C' surname='Bormann' fullname='Carsten Bormann'>
     700    <organization />
     701</author>
     702
     703<date month='July' day='1' year='2013' />
     704
     705<abstract><t>The Constrained Application Protocol (CoAP) is designed for resource- constrained nodes and networks, e.g., sensor nodes in low-power lossy networks (LLNs).  Still, to implement this Internet protocol on Class 1 devices, i.e., ~ 10 KiB of RAM and ~ 100 KiB of ROM, lightweight implementation techniques are necessary.  This document provides lessons learned from implementing CoAP for tiny, battery-operated networked embedded systems.  The guidelines for transmission state management and developer APIs can also help with the implementation of CoAP for less constrained nodes.</t></abstract>
    690706
    691707</front>
    692708
    693 <seriesInfo name='Internet-Draft' value='draft-kovatsch-lwig-class1-coap-00' />
     709<seriesInfo name='Internet-Draft' value='draft-kovatsch-lwig-coap-00' />
    694710<format type='TXT'
    695         target='http://www.ietf.org/internet-drafts/draft-kovatsch-lwig-class1-coap-00.txt' />
     711        target='http://www.ietf.org/internet-drafts/draft-kovatsch-lwig-coap-00.txt' />
    696712</reference>
    697713
Note: See TracChangeset for help on using the changeset viewer.