Subject: [core] New Version Notification for draft-ietf-core-coap-04

From: Zach Shelby <[email-masked]>
Date: Mon, 24 Jan 2011 14:52:17 +0200

http://www.ietf.org/internet-drafts/draft-ietf-core-coap-04.txt

Today we completed the -04 release of CoAP, which closes all known issues. Although we are a few weeks late on this release, the author team worked extremely hard on closing 25 tickets and made countless editorial improvements (special thanks to Klaus and Carsten). We now hope this document can be considered a complete specification. Although the vast majority of coap-04 tickets were editorial, some tickets did require technical changes that implementors should be aware of:

- Max-Age length now 0-4 bytes
- Token length now 0-8 bytes
- New response codes (now base 32)
- New Proxy-Uri option for proxy requests
- Greatly improved HTTP mapping section
- Uri-Path and Location-Path options now segmented

The complete list of changes can be found from Appendix D of the draft. 

Regards,
Zach et. al

Begin forwarded message:

> From: IETF I-D Submission Tool <[email-masked]>
> Date: January 24, 2011 2:41:19 PM GMT+02:00
> To: [email-masked]
> Cc: [email-masked], [email-masked], [email-masked]
> Subject: New Version Notification for draft-ietf-core-coap-04 
> 
> 
> A new version of I-D, draft-ietf-core-coap-04.txt has been successfully submitted by Zach Shelby and posted to the IETF repository.
> 
> Filename:	 draft-ietf-core-coap
> Revision:	 04
> Title:		 Constrained Application Protocol (CoAP)
> Creation_date:	 2011-01-24
> WG ID:		 core
> Number_of_pages: 75
> 
> Abstract:
> This document specifies the Constrained Application Protocol (CoAP),
> a specialized web transfer protocol for use with constrained networks
> and nodes for machine-to-machine applications such as smart energy
> and building automation.  These constrained nodes often have 8-bit
> microcontrollers with small amounts of ROM and RAM, while networks
> such as 6LoWPAN often have high packet error rates and a typical
> throughput of 10s of kbit/s.  CoAP provides a method/response
> interaction model between application end-points, supports built-in
> resource discovery, and includes key web concepts such as URIs and
> content-types.  CoAP easily translates to HTTP for integration with
> the web while meeting specialized requirements such as multicast
> support, very low overhead and simplicity for constrained
> environments.
> 
> 
> 
> The IETF Secretariat.
> 
> 

-- 
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297