[Interop-dev] NetJSON: clarify what an ID is

[Nemesis]

Correct, that's because we were discussing the possibility of
implementing the following changes in NetworkRoutes:

  * rename "destination" to "destination_address"
  * add "destination_id"
  * rename "next" to "next_address"
  * add "next_id"

And in "NetworkGraph":

  * rename "source" to "source_address"
  * add "source_id"
  * rename "target" to "target_address"
  * add "target_id"

Question:

  * Are you (plural you) sure of wanting to add more attributes?

if yes:

  * Should the new attributes be mandatory or optional?
  * Can we avoid the renaming by keeping the attribute name without the
    "_address" suffix? We can write in the spec that those attributes
    without the suffix refer to addresses by default, while the ones
    with "_id" suffix refer to the "router_id"

Federico


On 08/11/2015 02:21 PM, Henning Rogge wrote:
> yes.
>
> I just noticed your list of "ids" were not complete.
>
> Henning
>
> On Tue, Aug 11, 2015 at 1:54 PM, Nemesis <(spam-protected)> wrote:
>> On 08/11/2015 01:34 PM, Henning Rogge wrote:
>>> On Tue, Aug 11, 2015 at 1:30 PM, Nemesis <(spam-protected)> wrote:
>>>> which attributes do refer to IDs in NetworkGraph and NetworkRoutes
>>>>
>>>>
>>>> In NetworkRoutes:
>>>>
>>>> router_id
>>> maybe a "next_hop_id" would also be good.
>>>
>>> This would declare which router/node is used as the next hop of this route.
>>> We (of course) also need the address. So this would be another case of
>>> "split up into id/address".
>> I guess you are talking about this:
>> https://github.com/interop-dev/netjson/issues/9
>> Correct?
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150811/84a0f07a/attachment.html>