6841

@prefix azonOnto: <http://id.e-science.pl/ontologies/azonOnto#> .
@prefix collection: <http://id.e-science.pl/vocab/collection/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix kv: <http://id.e-science.pl/vocab/kv/> .
@prefix person: <http://id.e-science.pl/vocab/person/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix records: <http://id.e-science.pl/records/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix unit: <http://id.e-science.pl/vocab/unit/> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

kv:6841 a skos:Concept ;
    rdfs:seeAlso "https://en.wikipedia.org/wiki/Switching_loop"@en ;
    skos:altLabel "bridge loop"@en ;
    skos:definition "A Switching loop or bridge loop occurs in computer networks when there is more than one Layer 2 (OSI model) path between two endpoints (e.g. multiple connections between two network switches or two ports on the same switch connected to each other). The loop creates broadcast storms as broadcasts and multicasts are forwarded by switches out every port, the switch or switches will repeatedly rebroadcast the broadcast messages flooding the network. Since the Layer 2 header does not support a time to live (TTL) value, if a frame is sent into a looped topology, it can loop forever."@en ;
    skos:inScheme kv:keywordsVocabulary ;
    skos:prefLabel "switching loop"@en .