OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bdxr message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: SV: [bdxr] Minutes of BDXR TC meeting November 25 2015


I'm afraid it is 'an SMP'. One of the oddities of English. I think it's because the S is soft and sounds like 'ess'.

Sent from my iPad

On 12 Dec 2015, at 2:02 AM, Bergheim, Erlend Klakegg <erlend.klakegg.bergheim@difi.no> wrote:

Hi Kenneth,

 

I have no objections to the updated text. I think it should be “a SMP”, but my grammar is rusty… :)

 

- Erlend

 

Fra: Kenneth Bengtsson [mailto:kbengtsson@efact.pe]
Sendt: 9. desember 2015 19:11
Til: Bergheim, Erlend Klakegg <erlend.klakegg.bergheim@difi.no>
Kopi: bdxr@lists.oasis-open.org
Emne: Re: [bdxr] Minutes of BDXR TC meeting November 25 2015

 

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" <erlend.klakegg.bergheim@difi.no>
Date: Tuesday, December 8, 2015 at 7:20 AM
To: Kenneth Bengtsson <kbengtsson@efact.pe>
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

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]