This HTML5 document contains 48 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
n15https://github.com/USNavalResearchLaboratory/norm/blob/master/
n9http://wiki.zeromq.org/topics:
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n6https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
n13https://www.nrl.navy.mil/
n17https://ntrs.nasa.gov/api/citations/20180005140/downloads/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbchttp://dbpedia.org/resource/Category:
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/
n19https://datatracker.ietf.org/doc/html/rfc5740/

Statements

Subject Item
dbr:Acknowledgement_(data_networks)
dbo:wikiPageWikiLink
dbr:NACK-Oriented_Reliable_Multicast
Subject Item
dbr:Transport_layer
dbo:wikiPageWikiLink
dbr:NACK-Oriented_Reliable_Multicast
Subject Item
dbr:NACK-Oriented_Reliable_Multicast
rdfs:label
NACK-Oriented Reliable Multicast
rdfs:comment
NACK-Oriented Reliable Multicast (NORM) is a transport layer Internet protocol designed to provide reliable transport in multicast groups in data networks. It is formally defined by the Internet Engineering Task Force (IETF) in Request for Comments (RFC) 5740, which was published in November 2009. NORM also supports additional signaling mechanisms to facilitate session control, application-controlled positive acknowledgement, and other functions towards building complete point-to-point and group network communications applications that are highly robust and efficient.
dcterms:subject
dbc:Transport_layer_protocols
dbo:wikiPageID
38794271
dbo:wikiPageRevisionID
1079363992
dbo:wikiPageWikiLink
dbc:Transport_layer_protocols dbr:Flow_control_(data) dbr:Request_for_Comments dbr:Multicast dbr:Systematic_code dbr:Multicast_address dbr:Out-of-band_data dbr:Unicast dbr:Transport_layer dbr:Internet_Engineering_Task_Force dbr:Internet_protocol_suite dbr:Watermark_(data_synchronization) dbr:IP_addresses dbr:Forward_error_correction dbr:User_Datagram_Protocol dbr:Best-effort_delivery dbr:Session_(computer_science) dbr:Port_numbers dbr:Stream_Control_Transmission_Protocol dbr:Network_congestion dbr:Asynchronous_Layered_Coding dbr:Session_Announcement_Protocol dbr:Session_Description_Protocol dbr:Connection-oriented_communication
dbo:wikiPageExternalLink
n9:norm-protocol-transport n13: n15:README.md n17:20180005140.pdf n19:
owl:sameAs
n6:FvZJi wikidata:Q107646479
dbp:wikiPageUsesTemplate
dbt:Short_description dbt:Div_col dbt:Div_col_end dbt:Reflist dbt:IPstack
dbo:abstract
NACK-Oriented Reliable Multicast (NORM) is a transport layer Internet protocol designed to provide reliable transport in multicast groups in data networks. It is formally defined by the Internet Engineering Task Force (IETF) in Request for Comments (RFC) 5740, which was published in November 2009. NORM operates on top of the User Datagram Protocol (UDP), and ensures reliable communication based upon a negative acknowledgement (NACK), selective Automatic Repeat Request (ARQ) mechanism, as opposed to the positive acknowledgement (ACK) approach that the standard Transmission Control Protocol (TCP) uses. In other words, receivers using NORM only send feedback when they do not receive a packet, as opposed to the TCP model where receivers regularly acknowledge packet receipt as part of it protocol operation. This allows NORM to support large-scale receiver groups. To support further scalability, NORM also employs packet erasure coding using forward error correction (FEC) codes coupled with suppression of redundant NACK feedback from the receiver group. Additionally, NORM can be configured to operate with “silent receivers” relying upon its packet erasure coding for high assurance delivery, thus operating as a broadcast-only protocol. The FEC can be configured to be used either reactively (with NACKing receivers) or proactively (silent receivers), or in a hybrid manner that allows tradeoffs in latency and network overhead. Along with supporting reliable transport, NORM also provides TCP-compatible congestion control as well as end-to-end flow control. Unlike TCP, which uses the ACK mechanism for congestion control and flow control, NORM uses separate mechanisms for each. This allows for a wide variety of configurations to meet different application data delivery needs. NORM also supports additional signaling mechanisms to facilitate session control, application-controlled positive acknowledgement, and other functions towards building complete point-to-point and group network communications applications that are highly robust and efficient. Although NORM was developed primarily to support multicast group communication, it also supports unicast (point-to-point) data transfers.
prov:wasDerivedFrom
wikipedia-en:NACK-Oriented_Reliable_Multicast?oldid=1079363992&ns=0
dbo:wikiPageLength
42401
foaf:isPrimaryTopicOf
wikipedia-en:NACK-Oriented_Reliable_Multicast
Subject Item
wikipedia-en:NACK-Oriented_Reliable_Multicast
foaf:primaryTopic
dbr:NACK-Oriented_Reliable_Multicast