MAC-in-MAC
E634602
MAC-in-MAC is an IEEE 802.1ah provider backbone bridging technology that encapsulates customer Ethernet frames inside provider MAC headers to enable scalable, isolated Layer 2 networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| MAC-in-MAC canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7000233 — 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MAC-in-MAC Context triple: [IEEE 802.1ah, alsoKnownAs, MAC-in-MAC]
-
A.
Carter–Wegman MACs
Carter–Wegman MACs are a family of message authentication codes that use universal hashing combined with a secret key to provide efficient and provably secure authentication.
-
B.
IEEE 802.1AE MACsec standard
The IEEE 802.1AE MACsec standard is a network security protocol that provides data confidentiality, integrity, and origin authenticity for Ethernet traffic at the media access control (MAC) layer.
-
C.
CRAM-MD5
CRAM-MD5 is a challenge–response authentication mechanism that uses MD5 hashing to securely verify a user's identity without transmitting their password in plaintext.
-
D.
HMAC
HMAC (Hash-based Message Authentication Code) is a cryptographic construction that combines a secret key with a hash function to provide data integrity and authentication.
-
E.
Merkle–Damgård construction
The Merkle–Damgård construction is a fundamental method for building collision-resistant cryptographic hash functions from fixed-size compression functions, used in many classic hash algorithms like MD5 and SHA-1.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MAC-in-MAC Target entity description: MAC-in-MAC is an IEEE 802.1ah provider backbone bridging technology that encapsulates customer Ethernet frames inside provider MAC headers to enable scalable, isolated Layer 2 networks.
-
A.
Carter–Wegman MACs
Carter–Wegman MACs are a family of message authentication codes that use universal hashing combined with a secret key to provide efficient and provably secure authentication.
-
B.
IEEE 802.1AE MACsec standard
The IEEE 802.1AE MACsec standard is a network security protocol that provides data confidentiality, integrity, and origin authenticity for Ethernet traffic at the media access control (MAC) layer.
-
C.
CRAM-MD5
CRAM-MD5 is a challenge–response authentication mechanism that uses MD5 hashing to securely verify a user's identity without transmitting their password in plaintext.
-
D.
HMAC
HMAC (Hash-based Message Authentication Code) is a cryptographic construction that combines a secret key with a hash function to provide data integrity and authentication.
-
E.
Merkle–Damgård construction
The Merkle–Damgård construction is a fundamental method for building collision-resistant cryptographic hash functions from fixed-size compression functions, used in many classic hash algorithms like MD5 and SHA-1.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Ethernet encapsulation mechanism
ⓘ
IEEE 802.1ah technology ⓘ provider backbone bridging technology ⓘ |
| addsHeaderType |
backbone MAC addresses (B‑SA and B‑DA)
ⓘ
backbone MAC header ⓘ backbone VLAN tag (B‑VID) ⓘ |
| alsoKnownAs |
IEEE 802.1ah PBB
NERFINISHED
ⓘ
PBB NERFINISHED ⓘ |
| belongsToFamily | IEEE 802.1 bridging standards NERFINISHED ⓘ |
| classifiedAs | carrier Ethernet technology ⓘ |
| compatibleWith | IEEE 802.1Q VLAN tagging NERFINISHED ⓘ |
| definedInStandard | IEEE 802.1ah NERFINISHED ⓘ |
| designedFor |
large-scale metro Ethernet networks
ⓘ
multi-tenant Ethernet environments ⓘ |
| enables |
customer MAC transparency across provider network
ⓘ
isolated Layer 2 networks ⓘ scalable Layer 2 networks ⓘ |
| encapsulates |
customer MAC addresses
ⓘ
customer VLAN tags ⓘ |
| extends | traditional Ethernet bridging ⓘ |
| focusesOn | data plane encapsulation ⓘ |
| helpsWith | scaling MAC address space in provider networks ⓘ |
| improves | scalability of Ethernet provider networks ⓘ |
| operatesOver | Ethernet provider backbone ⓘ |
| provides | customer traffic separation at MAC layer ⓘ |
| reduces |
MAC address learning requirements in the core
ⓘ
size of provider MAC address tables ⓘ |
| requires | PBB-capable edge bridges ⓘ |
| separates |
customer addressing from provider addressing
ⓘ
customer control plane from provider control plane ⓘ |
| supports |
carrier Ethernet services
ⓘ
hierarchical Ethernet network design ⓘ multi-domain provider networks ⓘ multipoint Ethernet services ⓘ point-to-point Ethernet services ⓘ service multiplexing over a shared backbone ⓘ service provider VPN-like Ethernet services ⓘ traffic isolation between customers ⓘ virtual private LAN services (VPLS) over Ethernet backbones ⓘ |
| supportsLayer | Layer 2 ⓘ |
| usedAt | provider edge (PE) devices ⓘ |
| usedBy |
carrier Ethernet networks
ⓘ
telecommunications service providers ⓘ |
| usedFor | carrier-class Ethernet transport ⓘ |
| usedIn | provider backbone bridging (PBB) ⓘ |
| usesEncapsulation | customer Ethernet frames inside provider MAC headers ⓘ |
| usesIdentifierType | I‑SID (Service Instance Identifier) ⓘ |
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.
Instruction
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.
Input
Subject: MAC-in-MAC Description of subject: MAC-in-MAC is an IEEE 802.1ah provider backbone bridging technology that encapsulates customer Ethernet frames inside provider MAC headers to enable scalable, isolated Layer 2 networks.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.