[core] draft-hartke-t2trg-coral-reef

[Jim Schaad <[e-mail]>]

Looking at doing more implementation work on this - specific the
registration side rather than the retrieval side.


1.  Looking at section 5.2.5 - "Create Resource Registration"  I am going to
assume that you are keeping the same command line as what the current
document does, but I wonder if a better way to do it would be to use the
following as a resource

#using <http:/coreapps.org/reef#>
rd-unit <coap://[2001:db8:4::1]/> [
ep "node1"
domain "Floor 1"
lt 3600
et "LightBar"
rd-item <light/left> [rt "light" ct 0]
rd-item <light/middle> [rt "light" ct 0]
rd-item<light/middle> [rt "light" ct 0]
]

This has the advantage that all of the query parameters are moved into the
content which is going to make things easier to have new unknown items show
up.  I would think that it is just fine to restrict this to a single
rd-unit, but for third party registration it might be reasonable to allow
multiple rd-units to occur in a single body.

2.  A registration update could then have either the same as the content in
1 - or just an array of rd-items.  In the first case the attributes
associated with the endpoint would replaced - except for the ep and domain
attributes, in the second case just the items associated with it would be
replaced.

3.  If the CoRAL format is used, are the paging attributes still going to be
supported to keep the document size down?   Does not say anywhere.

Jim