search

maidsafe-archive / safe_examples

examples showcasing various features of the SAFE Network
BSD 3-Clause "New" or "Revised" License
82 stars 50 forks source link

How to define TAG_TYPE for a new service? #334

Open happybeing opened 6 years ago

happybeing commented 6 years ago

I see MaidSafe using TAG_TYPE_DNS=15001 etc with values from 15,000 upwards here:

https://github.com/maidsafe/safe_examples/blob/4294f06d0294c114153694f09f2d2303df5aac69/email_app/app/constants.js#L5

Whereas RFC-0003-reserved-names indicates values from 0-8,000 being reserved and has DNS entry as 5.

What is the relationship between the above two different DNS values if any?

Where should I declare a new service such as 'ldp' (for Solid Linked Data Protocol)?

What range should this value be in, and would 8,655 be ok for example?

Is anything above 8,000 still the free for all range?

hunterlester commented 6 years ago

Thank you for bringing this up, as it's a catalyst for discussion about updating and maintaining our RFC's.

This RFC, in particular, needs a major update. Numbers 2-5 may not be applicable anymore.

What is the relationship between the above two different DNS values if any?

5 at one time was reserved for the core network, 15001 is meant to be defined by the client. I've been informed that safe-core previously preferred files to be store inside a Mutable Data instance with a 15000 type tag, although didn't enforce it.

Where should I declare a new service such as 'ldp' (for Solid Linked Data Protocol)?

It should be declared >10000. 8000-10000 are reserved for core network.

happybeing commented 6 years ago

Thanks, I'll grab 80655. Anyone who guesses why can feel smug.