cti message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [cti] On current TAXII discussions
- From: "Jason Keirstead" <Jason.Keirstead@ca.ibm.com>
- To: <cti@lists.oasis-open.org>, Alexandre Dulaunoy <Alexandre.Dulaunoy@circl.lu>
- Date: Tue, 14 Mar 2017 08:22:13 -0400
Some other places content-range units other
than bytes are in use:
New IETF proposal for bytes-live range
unit: https://tools.ietf.org/html/draft-pratt-httpbis-bytes-live-range-unit-01
Postgresql web client using "items":
https://postgrest.readthedocs.io/en/stable/admin.html
Angular example using "customers":
https://billdelude.com/2014/08/18/paging-with-range-headers-using-angularjs-and-web-api-2-part-1/
etc etc... I can Google up many of these..
-
Jason Keirstead
STSM, Product Architect, Security Intelligence, IBM Security Systems
www.ibm.com/security| www.securityintelligence.com
Without data, all you are is just another person with an opinion - Unknown
__________________
You are making false assumptions here
- You are making the assumption that
registering the unit with IANA is required. It is not, registering the
unit with IANA is optional, as per the RFC.
- You are making the assumption that
proxies do not deal with this properly. I can assure you, they already
deal with it just fine (as they should, otherwise they would be violating
the RFC)
Content-Range units other than "bytes"
are in use in the wild throughout the web. We use them in our own product
("items"), and it's also a core facet of Dojo and other libraries
used everywhere on the web (Dojo is used on at minimum tens of thousandands
of public websites**). It is not uncommon at all.
**reference: https://trends.builtwith.com/_javascript_/Dojo-Toolkit
-
Jason Keirstead
STSM, Product Architect, Security Intelligence,
IBM Security Systems
www.ibm.com/security|
www.securityintelligence.com
Without data, all you are is just another
person with an opinion - Unknown
From:
Alexandre Dulaunoy <Alexandre.Dulaunoy@circl.lu>
To:
Bret Jordan <Bret_Jordan@symantec.com>,
"cti@lists.oasis-open.org" <cti@lists.oasis-open.org>
Date:
03/14/2017 05:57 AM
Subject:
Re: [cti] On current
TAXII discussions
Sent by:
<cti@lists.oasis-open.org>
On 13/03/17 18:09, Bret Jordan wrote:
> Alexandre,
>
>
> How then do you paginate STIX objects if not
by objects? You can not really do it by bytes. Breaking JSON
objects up by bytes is a disaster waiting to happen.
Yes, the clean way to do it IMHO is to use a MANIFEST
or an INDEX file instead of relying on the transport mechanism's
underlying systems to do the parsing JSON objects
and alike.
I think that this is cleaner and makes the real separation
between transport and format clean.
Asking for IANA to implement a new unit registry is
extremely far fetched, especially is we consider the possible compatibility
issues with HTTP proxies.
We know that our weight on the overall discussion
is low but our objective was always to keep the things as simple as possible.
Cheers
--
Alexandre Dulaunoy
CIRCL - Computer Incident Response Center Luxembourg
41, avenue de la gare L-1611 Luxembourg
info@circl.lu - www.circl.lu
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave
the OASIS TC that
generates this mail. Follow this link to all
your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]