Re: [cti-taxii] Use of well

In fairness, the robots.txt file was in use nearly two decades before .well-known came along, so expecting that to move is unlikely. But every standards-track document since requiring a well-known URI has used the .well-known prefix, including those from the IETF and W3C as well as other documents from EFF, Google, etc.

The reasoning is that it avoids any potential collision. While I don't know of any reason we're likely to hit a collision with "taxii", I also don't think it's reasonable to assume that nobody else will ever use that prefix - and we certainly cannot enforce it in any way.

As to Bret's comment that it adds an additional layer of indirection, I don't follow this - it's simply a different string. I did suggest adding some text about following redirections, but that applies equally to a "/taxii" or "/.well-known/taxii" URI path.

On 11 October 2016 at 13:13, Jason Keirstead <Jason.Keirstead@ca.ibm.com> wrote:

- The RFC has been around for 6 years and there are only 25 registered entries. If the standard was successful, one should expect hundreds of entries by now. Interestingly, one of the use cases given in the RFC itself (robots.txt placement) still to this day does not even use it.

- Nearly the only use has been from other RFCs.. which points to no one outside the IETF community is bothering to register

Therefore myself... I see .well_known as a failed standard, and would rather avoid it.

-
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

"Bret Jordan (CS)" ---10/09/2016 07:14:06 PM---All, We previously had pretty good consensus around the entry point for the TAXII API being the foll

From: "Bret Jordan (CS)" <Bret_Jordan@symantec.com>
To: "cti-taxii@lists.oasis-open.org" <cti-taxii@lists.oasis-open.org>
Date: 10/09/2016 07:14 PM
Subject: [cti-taxii] Use of well_known
Sent by: <cti-taxii@lists.oasis-open.org>

All,

We previously had pretty good consensus around the entry point for the TAXII API being the following:

https://something.somewhere.com/taxii

It has been suggested that we might look in to using the ".well_known" structure. After doing some research it appears that in fact a very few number of sites do in fact use this, however, it appears that it is not widely used or adopted.

I am curious to know what everyone thinks? Personally I am not a fan of using things like ".well_known" as it just adds an extra layer of abstraction and complication that I do not believe we need. If you would like this in TAXII, please speak up and let us know why. Otherwise we will pull the suggestion from the document.

Thanks
Bret

Dave Cridland

phone +448454681066

email dave.cridland@surevine.com

skype dave.cridland.surevine

Surevine

Participate | Collaborate | Innovate

Surevine Limited, registered in England and Wales with number 06726289. Mailing Address : PO Box 1136, Guildford GU1 9ND

If you think you have received this message in error, please notify us.

cti-taxii message