Q-in-Q
E162316
Q-in-Q is a networking technique that encapsulates one VLAN tag inside another to allow service providers to transport multiple customer VLANs across their backbone.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Q-in-Q canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1404963 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Q-in-Q Context triple: [Provider Bridging, alsoKnownAs, Q-in-Q]
-
A.
IEEE 802.1Qer
IEEE 802.1Qer is an Ethernet networking standard that defines mechanisms for enhanced traffic management and queuing to improve quality of service in bridged and time-sensitive networks.
-
B.
IEEE 802.1Qci
IEEE 802.1Qci is an Ethernet networking standard that defines per-stream filtering and policing mechanisms to enhance traffic control and improve reliability and security in time-sensitive networks.
-
C.
IEEE 802.1Qfc
IEEE 802.1Qfc is an amendment to the IEEE 802.1Q standard that specifies enhancements for frame preemption and traffic scheduling in Time-Sensitive Networking (TSN) Ethernet networks.
-
D.
IEEE 802.1Qfi
IEEE 802.1Qfi is an Ethernet networking standard that defines per-stream filtering and policing mechanisms to provide deterministic, time-sensitive traffic handling in bridged networks.
-
E.
IEEE 802.1Qeu
IEEE 802.1Qeu is an IEEE networking standard that defines mechanisms for enhanced queuing and traffic management in bridged and virtualized Ethernet networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Q-in-Q Target entity description: Q-in-Q is a networking technique that encapsulates one VLAN tag inside another to allow service providers to transport multiple customer VLANs across their backbone.
-
A.
IEEE 802.1Qer
IEEE 802.1Qer is an Ethernet networking standard that defines mechanisms for enhanced traffic management and queuing to improve quality of service in bridged and time-sensitive networks.
-
B.
IEEE 802.1Qci
IEEE 802.1Qci is an Ethernet networking standard that defines per-stream filtering and policing mechanisms to enhance traffic control and improve reliability and security in time-sensitive networks.
-
C.
IEEE 802.1Qfc
IEEE 802.1Qfc is an amendment to the IEEE 802.1Q standard that specifies enhancements for frame preemption and traffic scheduling in Time-Sensitive Networking (TSN) Ethernet networks.
-
D.
IEEE 802.1Qfi
IEEE 802.1Qfi is an Ethernet networking standard that defines per-stream filtering and policing mechanisms to provide deterministic, time-sensitive traffic handling in bridged networks.
-
E.
IEEE 802.1Qeu
IEEE 802.1Qeu is an IEEE networking standard that defines mechanisms for enhanced queuing and traffic management in bridged and virtualized Ethernet networks.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
VLAN encapsulation mechanism
ⓘ
networking technique ⓘ |
| adds |
S-VLAN tag
ⓘ
service provider VLAN tag ⓘ |
| alsoKnownAs |
802.1Q tunneling
ⓘ
VLAN stacking ⓘ |
| benefit |
preservation of customer VLAN configuration
ⓘ
scalable VLAN provisioning for providers ⓘ traffic isolation between customers ⓘ |
| canCoexistWith | standard 802.1Q VLANs ⓘ |
| canProvide |
Layer 2 tunneling across WAN
ⓘ
per-customer traffic separation ⓘ |
| designGoal |
isolation between customer and provider control domains
ⓘ
scalability of VLAN IDs in provider networks ⓘ |
| enables |
overlapping customer VLAN IDs
ⓘ
separation of customer and provider VLAN spaces ⓘ |
| encapsulates |
C-VLAN tag
ⓘ
customer VLAN tag ⓘ |
| encapsulationDepth | double VLAN tagging ⓘ |
| headerStructure | outer 802.1Q tag plus inner 802.1Q tag ⓘ |
| implementedIn | Ethernet switches ⓘ |
| innerTagRole | identifies customer VLAN ⓘ |
| layer | Data Link layer ⓘ |
| oftenCombinedWith |
MPLS-based services
ⓘ
QoS mechanisms in carrier Ethernet ⓘ |
| operatesAtLayer | OSI Layer 2 ⓘ |
| outerTagRole | identifies provider VLAN ⓘ |
| portMode |
customer-facing access ports
ⓘ
provider network trunk ports ⓘ |
| purpose |
extend customer VLANs over a service provider network
ⓘ
provide Layer 2 VPN services ⓘ transport multiple customer VLANs across a provider backbone ⓘ |
| relatedTo |
IEEE 802.1ad
ⓘ
VLAN tagging ⓘ provider bridging ⓘ |
| requires | Q-in-Q capable switches ⓘ |
| requiresConfiguration | provider edge ports ⓘ |
| risk | misconfiguration leading to VLAN leakage ⓘ |
| supports |
VLAN multiplexing
ⓘ
multiple customer VLANs over a single provider VLAN ⓘ |
| trafficType | Ethernet frames ⓘ |
| typicalUseCase |
connecting multiple customer sites over a carrier network
ⓘ
wholesale Ethernet access services ⓘ |
| usedBy |
carrier Ethernet networks
ⓘ
service providers ⓘ |
| usedFor |
Metro Ethernet services
ⓘ
transparent LAN services ⓘ |
| usesStandard |
IEEE 802.1Q series
ⓘ
surface form:
IEEE 802.1Q
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Q-in-Q Description of subject: Q-in-Q is a networking technique that encapsulates one VLAN tag inside another to allow service providers to transport multiple customer VLANs across their backbone.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.