Protocol Standardization Efforts: Difference between revisions
No edit summary |
No edit summary |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
This diagram illustrates the different projects that need to inter-operate within the standards being developed here. | This diagram illustrates the different projects that need to inter-operate within the standards being developed here. | ||
[[Image: | |||
A minimum requirement is for the 3 main areas to interoperate (but not projects within each area) | [[Image:Reddnet_design2.png|diagram]] | ||
*TSSP is the higher-level spec including use of protocols/standards IBP and exMSP | |||
*REDDnet software is the set of implementations shown here | |||
A minimum requirement is for the 3 main areas to interoperate | |||
*(but not initially among projects within each area) | |||
*ibp 1.4 compatibility | *ibp 1.4 compatibility | ||
*exMSP currently | *exMSP currently means | ||
**LoRS reads a base-exnode-schema (LoRS schema) | |||
**Lstcp reads a base-schema (or just IBP calls) from the L-Server | |||
The data-management systems L-Store and LoDN currently have no additional interoperability. | The data-management systems L-Store and LoDN currently have no additional interoperability. | ||
| Line 27: | Line 36: | ||
** The Metadata Hosting Service | ** The Metadata Hosting Service | ||
** [[exMSP Messages]] | ** [[exMSP Messages]] | ||
** [[Directory and data management services APIs]] | |||
* Internet Backplane Protocol | * Internet Backplane Protocol | ||
** [http://www.reddnet.org/mwiki/index.php/Internet_Backplane_Protocol Version 1.4] | ** [http://www.reddnet.org/mwiki/index.php/Internet_Backplane_Protocol Version 1.4] | ||
** [[1.4 Revision]] | ** [[1.4 Revision]] | ||
** [[Development ideas]] | |||
* Network Functional Unit (NFU) | |||
**[http://loci.cs.utk.edu/ibp/files/LoNC-FDNA03.pdf LOCI NFU doc] | |||
**[[NFU Specification]] | |||
Latest revision as of 10:36, 24 January 2008
SUMMARY - Given the increasing number of logistical networking software components, the REDDnet community is actively seeking to establish a series of standard protocols that would ensure the interoperability between these components and the services they need and/or the clients they serve. Although the Internet Backplane Protocol is already documented, it is also under revision by members of the REDDnet community, some of whom are the original authors.
This diagram illustrates the different projects that need to inter-operate within the standards being developed here.
- TSSP is the higher-level spec including use of protocols/standards IBP and exMSP
- REDDnet software is the set of implementations shown here
A minimum requirement is for the 3 main areas to interoperate
- (but not initially among projects within each area)
- ibp 1.4 compatibility
- exMSP currently means
- LoRS reads a base-exnode-schema (LoRS schema)
- Lstcp reads a base-schema (or just IBP calls) from the L-Server
The data-management systems L-Store and LoDN currently have no additional interoperability.
The following is the list of protocols under deliberation/refinement:
- Transfer and Storage Services Protocol
- Resource Discovery Protocol (see Resource Discovery Standardization)
- The Discovery Service
- RDP Messages
- Exnode Management Services Protocol
- Exnode specification
- The Metadata Hosting Service
- exMSP Messages
- Directory and data management services APIs
- Internet Backplane Protocol
- Network Functional Unit (NFU)