Hi Erlend
As promised today my suggestions for clarifications (in
blue ):
When using HTTP(S) for SMP lookup , client side
caching
MAY
be introduced using headers “Last-Modified” and “If-Modified-Since” as defined in
[RFC7232] .
An SMP server MAY implement support of caching, and an SMP client MAY implement caching in case it is supported by an SMP server.
Implementing caching or support of caching MUST NOT
be imposed. Strategy for invalidation is not specified here, but
MUST be implemented in accordance with [RFC7232] .
Only the "Last-Modified" and "If-Modified-Since" headers are supported for caching SMP responses. No other HTTP(S) headers in
[RFC7232] or elsewhere are used for client side caching in SMP.
Sample of “Last-Modified” in response (server):
Last-Modified: Tue, 01 Dec 2015 19:14:44 GMT
Sample of “If-Modified-Since” in request (client):
If-Modified-Since: Tue, 01 Dec 2015 19:14:44 GMT
Please let me know your comments.
Best regards,
Kenneth
From: "Bergheim, Erlend Klakegg" <
>
Date: Tuesday, December 8, 2015 at 7:20 AM
To: Kenneth Bengtsson <
>
Subject: RE: [bdxr] Minutes of BDXR TC meeting November 25 2015
Hi Kenneth,
I’ve gone from a more detailed approach to a simpler as this is not ment to take a lot of space in the specification.
Proposed text to be added:
When using HTTP(S) for SMP lookup caching may be introduced using headers “Last-Modified” and “If-Modified-Since” as defined
in RFC 7232. Implementing caching functionality should be entirely up to both SMP server and SMP client, and should not be imposed. Strategy for invalidation is not specified here, but must apply to RFC 7232.
Sample of “Last-Modified” in response (server):
Last-Modified: Tue, 01 Dec 2015 19:14:44 GMT
Sample of “If-Modified-Since” in request (client):
If-Modified-Since: Tue, 01 Dec 2015 19:14:44 GMT
- Erlend
