> I like this approach on several levels but it does rely on the
> implementer to ensure the immutability of the object referenced by the
> URL, doesn't it?
My opinion would be no. Just like any web resource, the object identified by a particular URL could change over time (e.g., same ID, new version). That said, we could make immutability a rule if we thought it was beneficial. Were you thinking immutability would be a positive or a negative?
Thank you.
-Mark
-----Original Message-----
From: Trey Darley [mailto:]
Sent: Friday, October 30, 2015 5:29 AM
To: Jordan, Bret <>
Cc: Davidson II, Mark S <>; Barnum, Sean D. <>; Jerome Athias <>; Terry MacDonald <>; Taylor, Marlon <>; Wunder, John A. <>;
Subject: Re: [cti-stix] Proposal to establish Sightings (#306) and Relationships (#291) as our official issue topics under active consideration for STIX v2.0
On 29.10.2015 20:49:30, Jordan, Bret wrote:
> I could see the ID in URL format being just an entry points in to a
> RESTful API location on a TAXII server. So if a TAXII server has two
> core concepts (elements of the RESTful API):
>
> 1) Channel Communications
> 2) Data Storage / Query
>
> Then it is possible that IDs could easily fall in to the Data
> Storage / Query portion of the TAXII 2.0 RESTful API. If it is
> decided that something like this is desirable, then we can take up
> the task in the TAXII SC on what the URLs / REST entry points need
> to look like.
>
I like this approach on several levels but it does rely on the
implementer to ensure the immutability of the object referenced by the
URL, doesn't it?
--
Cheers,
Trey
--
Trey Darley
Senior Security Engineer
4DAA 0A88 34BC 27C9 FD2B A97E D3C6 5C74 0FB7 E430
Soltra | An FS-ISAC & DTCC Company
www.soltra.com
--
"For all resources, whatever it is, you need more." --RFC 1925
