Re: [secdir] SECDIR review of draft-ietf-weirds-json-response-10

Andy Newton <andy@arin.net> Mon, 27 October 2014 22:57 UTC

From: Andy Newton <andy@arin.net>
To: Chris Inacio <inacio@cert.org>, "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-weirds-json-response.all@tools.ietf.org" <draft-ietf-weirds-json-response.all@tools.ietf.org>
Thread-Topic: SECDIR review of draft-ietf-weirds-json-response-10
Thread-Index: AQHP8Y1YaIwz5nPq40qGThlj74eNJZxEj12A
Date: Mon, 27 Oct 2014 22:56:27 +0000
Message-ID: <D0744202.3115A%andy@arin.net>
In-Reply-To: <F5B32DFF-FD3C-48A7-B24B-0232BFFA7127@cert.org>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.7.130812
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <481777CC68CEEB42BEE2D61C3833D1EB@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/8bGaJvMjD5Bva7bEvZo0Mx0-eaU
Subject: Re: [secdir] SECDIR review of draft-ietf-weirds-json-response-10
Precedence: list

Thanks for the review Chris. Comments are in-line...

On 10/26/14, 10:25 PM, "Chris Inacio" <inacio@cert.org> wrote:

>My only concern about the security considerations section is related to
>self-references necessary in the responses to cache results.  Is it
>possible to create a poisoned cache based on the self-reference?  What
>should a client do in order to protect itself from such an attack.

Yes, I guess cache poisoning is possible. Good catch!

I plan to add the following paragraph to Section 5 where caching is
described:

  Clients using ³self² links for caching SHOULD not cache any object
  class instances where the authority of the self link is different
  than the authority of the server returning the data. Failing to do
  so might result in cache poisoning.

-andy

[secdir] SECDIR review of draft-ietf-weirds-json-… Chris Inacio
Re: [secdir] SECDIR review of draft-ietf-weirds-j… Andy Newton