[tipc-discussion] Re: [tipc-news] TIPC Feature Candidate Priorities

[Jon M. <jon...@er...>]

Hi Allan,
A good list.

I would only add three items:

1) The zone master. Ability to manage the whole cluster/zone by 
tipc-config from a single node. This support is almost there, but the 
original approach with a running daemon can be avoided, by letting 
tipc-config order the local module to persistently publish a reserved 
port name indicating "this node is zone master". This publication 
remains until counterorder is given, or until the module crashes/is 
removed. (Idea from Per/Torbjorn)

2) Making the retransmission protocol at the link layer omittable. I.e. 
when a bearer type registers, it may give a boolean parameter 
"reliable", indicating that buffers sent over this bearer don't need to 
be added to the link send queue. This would also make zero-copy buffer 
handling possible, something particularly desirable if we have a shared 
memory media. This may be a sub-item under "performance".

3) Support for multi-core CPUs. This is becoming hot now, and if 2) 
above is implemented, it should be possible to position TIPC as THE 
communication media between the different cores on such computers.

Regards
///jon

Stephens, Allan wrote:

>The upcoming TIPC Working Group meeting in Santa Clara will include
>discussions about the next steps in the evolution of TIPC; however, it
>won't be possible to review all potential areas of development in a
>single afternoon.  Therefore, the Working Group would like to know which
>ones are of the greatest interest to the TIPC community.
>
>Please review of the following list of candidate features and let us
>know your top priorities by:
>
>a) attending the March 23rd Working Group meeting in person,
>b) sending me an email with your selections
>(mailto:all...@wi...), or
>c) posting your preferences to the TIPC mailing list
>(mailto:tip...@li...).
>
>In addition, feel free to make your own feature suggestions if you don't
>see them on the list below.
>
>Regards,
>Al Stephens
>
>=========================
>
>1. Secondary Node support
>- Allows the use of nodes with incomplete connectivity within a cluster
>- Relaxes the current "full mesh network" constraint
>
>2. Multi-cluster support
>- Allows the creation of TIPC networks with 2 or more clusters
>- Enables TIPC networks to scale up to larger numbers of nodes more
>easily
>
>3. Wide-area TIPC support
>- Adds support for secure bearer types (eg. SSL TCP bearer and/or UDP
>bearer)
>- Allows TIPC traffic to run over the Internet
>
>4. Network Management enhancements
>- Improves tools for monitoring the behavior of a TIPC network
>  (eg. display more status info, log abnormal conditions better, raise
>alarms, ...) 
>- Makes it easier to identify problems
>
>5. Debugging enhancements
>- Improves tools for debugging problems within a TIPC network
>  (eg. display more status info, provide message tracking tools, ...) 
>- Makes it easier to debug problems
>
>6. Robustness enhancements
>- Improves TIPC's ability to handle abnormal conditions without failing
>  (eg. complete detection of invalid arguments & messages, additional
>stress testing, ...)
>- Moves TIPC towards carrier-grade reliability
>
>7. Quality of Service (QoS) enhancements
>- Allows better control over service degradation when resource
>limitations arise
>  (eg. ensure links stay up, impact low importance applications first,
>...)
>- Moves TIPC towards carrier-grade reliability
>
>8. Performance enhancements
>- Improves the throughput and latency of the TIPC datapath
>- Allows TIPC to handle a wider range of applications
>
>9. IP Application Migration enhancements
>- Enhances TIPC's socket API to ease porting of IP-based applications to
>TIPC
>- Lowers cost of transitioning applications from IP to TIPC
>
>10. Footprint Reduction
>- Allows users to build a reduced-size version of TIPC with reduced
>capabilities 
>- Permits TIPC to run on resource-constrained devices (such as DSPs)
>
>11. Topology Service enhancements
>- Increases flexibility of the TIPC name subscription service
>  (eg. allow subscription cancellation, suppress unwanted events, etc.)
>- Provides capabilities requested by programmers writing TIPC 1.5
>applications
>
>12. TIPC 1.5 on Linux 2.4
>- Provides the latest TIPC capabilities on older versions of Linux
>kernel
>
>13. TIPC 1.5 on VxWorks 5.x
>- Provides the latest TIPC capabilities on older versions of VxWorks
>
>14. SAF Over TIPC
>- Implements the Service Availability Forum's AIS specification
>- Allows equipment vendors to build carrier-grade network elements more
>easily
>
>[END OF LIST]
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
>_______________________________________________
>tipc-news mailing list
>tip...@li...
>https://lists.sourceforge.net/lists/listinfo/tipc-news
>  
>