Giter VIP home page Giter VIP logo

Comments (5)

nemesifier avatar nemesifier commented on July 3, 2024

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"

Reference: https://lists.funkfeuer.at/pipermail/interop-dev/2015-August/000498.html

from netjson.

nemesifier avatar nemesifier commented on July 3, 2024

This attribute would suits also Babeld's needs, according to @jech in
https://lists.funkfeuer.at//pipermail/interop-dev/2015-August/000505.html

from netjson.

jech avatar jech commented on July 3, 2024

Should the new attributes be mandatory or optional?

All attributes should be optional, since any attribute will be difficult to provide by some software.

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"

Yes.

from netjson.

nemesifier avatar nemesifier commented on July 3, 2024

To recap, it seems there is consensus on adding the following OPTIONAL attributes:

NetworkRoutes:

  • destination_id
  • next_id

NetworkGraph:

  • source_id
  • target_id

@jech would this change make NetJSON compatible with Babel and other vector distance protocols?

from netjson.

HRogge avatar HRogge commented on July 3, 2024

"All data optional" means no automatic processing.

We need mandatory values which allow us to move from one part of the data to the other one.

the "id" fields would allow us to connect nodes and edges... if a routing protocol does not use special id's, it can just repeat the address (as long as its unique).

from netjson.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.