Hello Kent,

Sadly you are right. So I should probably remove it.

On the other hand IMHO it is could be useful info. What would you think, if I found an alternative encoding for it. (It would be optional.)
It could be encoded as metadata on the content-data container/anydata. It could give a quick indication whether the data has changed. If config data is read/provided periodically, it could be useful.

So is it useful enough to bother? Is the encoding as metadata OK?

Or should I just remove it?

regards Balazs

On 2019. 03. 25. 8:03, Kent Watsen wrote:
Section 3 says this about Content data: “It MAY include entity-tags and timestamps as defined in [RFC8040]”.  How is this possible?  RFC 8040 only returns such data in HTTP headers; there’s no defined encoding for putting the data into instance data.
-- 
Balazs Lengyel                       Ericsson Hungary Ltd.
Senior Specialist
Mobile: +36-70-330-7909              email: [email protected] 


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to