Re: #162: Add application/link-format to code registry

#162: Add application/link-format to code registry

Changes (by zach <at> …):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Done for coap-07.

--

-- 
--------------------------------+-------------------------------------------
 Reporter:  zach <at> …              |        Owner:  zach <at> …            
     Type:  task                |       Status:  closed            
 Priority:  trivial             |    Milestone:                    
Component:  coap                |      Version:                    
 Severity:  -                   |   Resolution:  fixed             
 Keywords:                      |  
--------------------------------+-------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/core/trac/ticket/162#comment:1>
core <http://tools.ietf.org/core/>

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

Re: #150: Allow zero-length Content-Type

#150: Allow zero-length Content-Type

Changes (by zach <at> …):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Done in coap-07.

--

-- 
--------------------------------+-------------------------------------------
 Reporter:  cabo <at> …              |        Owner:  cabo <at> …      
     Type:  protocol defect     |       Status:  closed      
 Priority:  trivial             |    Milestone:              
Component:  coap                |      Version:              
 Severity:  Active WG Document  |   Resolution:  fixed       
 Keywords:                      |  
--------------------------------+-------------------------------------------

Ticket URL: <http://wiki.tools.ietf.org/wg/core/trac/ticket/150#comment:1>
core <http://tools.ietf.org/core/>

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

Re: #153: Make congestion control recommendation more actionable

#153: Make congestion control recommendation more actionable

Changes (by zach <at> …):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Added to Section 4.5 of coap-07.

--

-- 
----------------------------------+-----------------------------------------
 Reporter:  cabo <at> …                |        Owner:  draft-ietf-core-coap <at> …             
     Type:  protocol enhancement  |       Status:  closed                             
 Priority:  major                 |    Milestone:                                     
Component:  coap                  |      Version:                                     
 Severity:  Active WG Document    |   Resolution:  fixed                              
 Keywords:                        |  
----------------------------------+-----------------------------------------

Ticket URL: <http://wiki.tools.ietf.org/wg/core/trac/ticket/153#comment:1>
core <http://tools.ietf.org/core/>

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

Re: #149: Text for PUT/POST response payloads is missing

#149: Text for PUT/POST response payloads is missing

Changes (by zach <at> …):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Changes made to coap-07.

--

-- 
--------------------------------+-------------------------------------------
 Reporter:  cabo <at> …              |        Owner:  cabo <at> …      
     Type:  protocol defect     |       Status:  closed      
 Priority:  major               |    Milestone:              
Component:  coap                |      Version:              
 Severity:  Active WG Document  |   Resolution:  fixed       
 Keywords:                      |  
--------------------------------+-------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/core/trac/ticket/149#comment:1>
core <http://tools.ietf.org/core/>

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

draft-shelby-core-resource-directory-00

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

Re: Fwd: New Version Notification for draft-shelby-core-resource-directory-00.txt

Thanks everyone for the helpful feedback, ideas and interest on the resource directory draft. This week I
am going to dedicate my time to releasing coap-07 and am on vacation after that, so forgive my silence on
answering questions about this draft for the next couple weeks. The intention is to take the feedback into
account and release a -01 rev in Quebec.

Zach 

On Jun 27, 2011, at 3:20 PM, Zach Shelby wrote:

> We have submitted an initial resource directory interface specification draft, and would like to spend
10 minutes in Quebec to present it.
> 
> http://tools.ietf.org/html/draft-shelby-core-resource-directory-00
> 
> Zach
> 
> Begin forwarded message:
> 
>> From: internet-drafts <at> ietf.org
>> Date: June 27, 2011 3:15:06 PM GMT+03:00
>> To: zach <at> sensinode.com
>> Cc: srdjan.krco <at> ericsson.com, zach <at> sensinode.com
>> Subject: New Version Notification for draft-shelby-core-resource-directory-00.txt
>> 
>> A new version of I-D, draft-shelby-core-resource-directory-00.txt has been successfully submitted
by Zach Shelby and posted to the IETF repository.
>> 
>> Filename:	 draft-shelby-core-resource-directory
>> Revision:	 00
>> Title:		 CoRE Resource Directory
>> Creation date:	 2011-06-27
>> WG ID:		 Individual Submission
>> Number of pages: 16
>> 
>> Abstract:
>>  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 hosts descriptions of
>>  resources held on other servers, allowing lookups to be performed for
>>  those resources.  This document specifies the web interfaces that a
>>  Resource Directory supports in order for web servers to discover the
>>  RD and to registrer, maintain, lookup and remove resources
>>  descriptions.  Furthermore, new link attributes useful in conjunction
>>  with an RD are defined.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
> 
> -- 
> Zach Shelby, Chief Nerd, Sensinode Ltd.
> http://www.sensinode.com
> http://zachshelby.org  - My blog "On the Internet of Things"
> http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
> Mobile: +358 40 7796297
> 
> _______________________________________________
> core mailing list
> core <at> ietf.org
> https://www.ietf.org/mailman/listinfo/core

--

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

_______________________________________________
core mailing list
core <at> ietf.org
https://www.ietf.org/mailman/listinfo/core

FW: New Version Notification for draft-arkko-core-sleepy-sensors-00.txt

FYI. Comments appreciated.

http://tools.ietf.org/html/draft-arkko-core-sleepy-sensors-00

> Filename:	 draft-arkko-core-sleepy-sensors
> Revision:	 00
> Title:		 Implementing Tiny COAP Sensors
> Creation date:	 2011-07-04
>
> Abstract:
>    The authors are developing COAP and IPv6-based sensor networks for
>    environments where lightweight implementations, long battery
>    lifetimes, and minimal management burden are important.  The memo
>    shows how different communication models supported by COAP affect
>    implementation complexity and energy consumption, far more so than
>    mere changes in message syntax.  Our prototype implements a
>    multicast-based IPv6, UDP, COAP, and XML protocol stack in less than
>    50 assembler instructions.  While this extremely minimal
>    implementation is suitable only for limited applications and makes a
>    number of assumptions, the general conclusions point to need for
>    further work in developing the COAP multicast and observation
>    frameworks.
>   

Fwd: I-D Action: draft-cao-core-aol-req-00.txt

A very simple draft yet, but easy to read and discuss.

---------- Forwarded message ----------
From:  <internet-drafts <at> ietf.org>
Date: Mon, Jul 4, 2011 at 9:55 PM
Subject: I-D Action: draft-cao-core-aol-req-00.txt
To: i-d-announce <at> ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.

       Title           : Allways-online Requirement for Sleeping CoAP Node
       Author(s)       : Zhen Cao
       Filename        : draft-cao-core-aol-req-00.txt
       Pages           : 5
       Date            : 2011-07-04

  CoAP is to enable a concept of web of sensors, but there are many
  cases that the sensors are not always online and hence the requests
  from the web client cannot reach them in timely manner.  This
  document analyzes this problem and describes the requirements for a
  CoAP enabled sensor to behave always online.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cao-core-aol-req-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-cao-core-aol-req-00.txt
_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--

-- 
Best regards,
Zhen

Fwd: New Version Notification for draft-castellani-core-http-mapping-00.txt

All,

we have submitted a new draft about the mapping of CoAP to/from HTTP.

We would like to have a slot in Quebec to present it.

Best,
Angelo, Salvatore, Akbar, Thomas and Esko

---------- Forwarded message ----------
From:  <internet-drafts <at> ietf.org>
Date: Mon, Jul 4, 2011 at 18:03
Subject: New Version Notification for draft-castellani-core-http-mapping-00.txt
To: angelo <at> castellani.net
Cc: angelo <at> castellani.net, salvatore.loreto <at> ericsson.com,
akbar.rahman <at> interdigital.com, tho <at> koanlogic.com,
esko.dijk <at> philips.com

A new version of I-D, draft-castellani-core-http-mapping-00.txt has
been successfully submitted by Angelo P. Castellani and posted to the
IETF repository.

Filename:        draft-castellani-core-http-mapping
Revision:        00
Title:           Best practices for HTTP-CoAP mapping implementation
Creation date:   2011-07-04
WG ID:           Individual Submission
Number of pages: 23

Abstract:
  This draft aims at being a base reference documentation for HTTP-CoAP
  proxy implementors.  It details deployment options, discusses
  possible approaches for URI mapping, and provides useful
  considerations related to protocol translation.

The IETF Secretariat

Re: Fwd: New Version Notification for draft-castellani-core-http-mapping-00.txt

here the link
http://www.ietf.org/id/draft-castellani-core-http-mapping-00.txt

-- 
Salvatore Loreto
www.sloreto.com

On 7/4/11 7:04 PM, Angelo P. Castellani wrote:
> All,
>
> we have submitted a new draft about the mapping of CoAP to/from HTTP.
>
> We would like to have a slot in Quebec to present it.
>
> Best,
> Angelo, Salvatore, Akbar, Thomas and Esko
>
>
> ---------- Forwarded message ----------
> From:<internet-drafts <at> ietf.org>
> Date: Mon, Jul 4, 2011 at 18:03
> Subject: New Version Notification for draft-castellani-core-http-mapping-00.txt
> To: angelo <at> castellani.net
> Cc: angelo <at> castellani.net, salvatore.loreto <at> ericsson.com,
> akbar.rahman <at> interdigital.com, tho <at> koanlogic.com,
> esko.dijk <at> philips.com
>
>
> A new version of I-D, draft-castellani-core-http-mapping-00.txt has
> been successfully submitted by Angelo P. Castellani and posted to the
> IETF repository.
>
> Filename:        draft-castellani-core-http-mapping
> Revision:        00
> Title:           Best practices for HTTP-CoAP mapping implementation
> Creation date:   2011-07-04
> WG ID:           Individual Submission
> Number of pages: 23
>
> Abstract:
>    This draft aims at being a base reference documentation for HTTP-CoAP
>    proxy implementors.  It details deployment options, discusses
>    possible approaches for URI mapping, and provides useful
>    considerations related to protocol translation.
>
>
>
>
> The IETF Secretariat
> _______________________________________________
> core mailing list
> core <at> ietf.org
> https://www.ietf.org/mailman/listinfo/core