Task 63 Scope – Ethernet Examples Purpose – Provide additional Ethernet Examples Specifically – Ethernet interface, Bridge VLAN Bridge, PB (Q-in-Q), PBB (Mac-in-Mac), Link Aggregation / LACP, Optical SFP, IP interface, TCp, UDP interface, P-P wireless transport interface, WiFi interface Includes – Excludes – none External Dependencies – none Assumptions – none Risks – none

Team Members Leader - Members ???

IPR Declaration Is there any IPR associated with this presentation NO NOTICE: This contribution has been prepared to assist the ONF. This document is offered to the ONF as a basis for discussion and is not a binding proposal on Cisco or any other company. The requirements are subject to change in form and numerical value after more study. Cisco specifically reserves the right to add to, amend, or withdraw statements contained herein. THE INFORMATION HEREIN IS PROVIDED “AS IS,” WITHOUT ANY WARRANTIES OR REPRESENTATIONS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION, WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Packet Encapsulation vs Header re-writing We need to be careful not to mix header encapsulation, such as when an IP header is encapsulated in an Ethernet header , vs ‘modifying’ a header as is done in 802.1Q (VLAN), 802.1ah (PBB) and 802.1ad (PB) { may actually be header removal + re-creation}

VLAN Tags vs VLAN-IDs The tag is the VLANID + Ethertype and some other bits : DE … If we are only concerned with the VLAN-ID then we can assume that x-VID == x-VLAN == x-TAG https://www.researchgate.net/publication/224392603_A_Survey_of_Advanced_Ethernet_Forwarding_Approaches

2 Port Bridge ETH = Ethernet MAC ETC = Ethernet Coding Note that this is the ITU-T representation of the IEEE ‘baggy pants’ model 2 Port Bridge MII = Media independent Interface PHY = Physical Layer Device (PHY>100M = PCS + PMA + PMD) PCS = Physical Coding Sublayer PMA = Physical Medium Attachment PMD = Physical Medium Dependent MDI = Medium Dependent Interface ETH C-MAC ETH ETH = Ethernet MAC ETC = Ethernet Coding ETY = Ethernet Phy C-MAC ETY ETY https://trac.ietf.org/trac/edu/raw-attachment/wiki/IETF86/86-IEEE-8021-Thaler.pdf

Openconfig Ethernet Interface

Ethernet ONF Model Extension Put in package org.onf.cim.ethernet ETH

2 Port Bridge ITU-T G.8011.1/Y.1307.1 (08/2013)

2 Port Q-Bridge – 1 access port, one trunk port (0x8100) C-Tag added on ingress, stripped on egress C-TAG not modified, only used for filtering Note that there are 2 types of Q-Bridge : SVL (SFD) Shared VLAN Learning (Single Forwarding Database) IVL (MFD) Independent VLAN Learning (Multiple Forwarding Databases) From http://www.dspcsp.com/lectures/AdvEth.pptx 1 ETH-m C-MAC + C-TAG ETH-m C-MAC + C-TAG FD N ETH C-MAC ETH C-MAC ETY ETY Access Port Trunk Port https://erg.abdn.ac.uk/users/gorry/course/lan-pages/vlan.html

Openconfig Ethernet Bridge An OpenConfig L2 “network instance” is equivalent to an Ethernet Bridge Processing Construct function https://datatracker.ietf.org/meeting/94/materials/slides-94-rtgwg-9

IEEE Yang

Bridge ONF Model Extension Put in package org.onf.cim.bridge

OpenConfig VLANs

Q-Bridge Mental Model Bridge Legend Ingress Access Port Egress Match Action Access Port If <match> Then <action> Else <drop> A M Ingress Egress Trunk Port MAC filtering Database targets known MAC Broadcast + Unknown MAC is broadcast to all but ingress port A M Ingress Egress SVI Port

Filter / Match (Allow) Unmatched == DROP frame Note – only one match statement and one action per port per (ingress / egress) direction Q-Bridge Port Types Port Type Direction Filter / Match (Allow) Unmatched == DROP frame Match VLAN Action Match ETYPE Set Action Comment Access Ingress UNTAGGED PUSH_VLAN 0x8100 (.Q)   Egress MATCH_VLAN POP_VLAN -----   Converted to .D Etype Trunk MATCH_VLANS NO_ACTION NONE SVI ----  Header added Header removed

VLAN ONF Model Extension Put in package org.onf.cim.bridge.vlan Could split out Trunk and Access port specific attributes from SwitchedLtp (optional composition)

2 Port Q-Bridge with PoE 1 FD N PoE injection / extraction No PoE ETH-m C-MAC + C-TAG ETH-m C-MAC + C-TAG FD N ETH C-MAC ETH C-MAC PoE injection / extraction ETY ETY No PoE Access Port Trunk Port

Q-in-Q / PB / IEEE 802.1ad / Stacked VLANs (0x88A8) https://www.slideserve.com/aliza/802-1ad-provider-provider-edge-bridges CEP = Customer Edge Port CNP = Customer Network Port PEP = Provider Edge Port PNP = Provider Network Port PEB = Provider Edge Bridge PB = Provider Bridge CE = Customer Equipment C-MAC = Customer MAC C-VID / C-VLAN / C-TAG : Customer (internal) S-VID / S-VLAN / S-TAG : Service (external) Note that a PEB has one S-component, and one C-component per customer using C-tagged services. Each C-Component has only one CEP and a PEP for every S-VLAN that it uses (one S-VLAN per PEP). Each S-VLAN id can only be used by 1 customer in a PBN ! Note that this should read S-Component and C-Component, not S-VLAN and C-VLAN

PB Management Representation from OpenConfig YANG A PEB could be designed using a C-component for every customer plus a S-component plus all the internal interfaces This would add a lot of complexity Looking closely, we can see that we only need a single bridge that is S-VLAN aware We also need the ability for CNP and CEP to manipulate the header (push / pop S-VLAN, modify the ETYPE) The last thing is how many MAC tables we need : A 802.1D MAC table is mac address + port. A 802.1Q MAC table is vlan + mac address + port So for PB if we can use a single MAC table with S-vlan + C-vlan + mac address + port

PEB Mental Model S-Component C-Component1 Ingress Egress Ingress PNP CEP C-Component2 A M Ingress Egress A M Ingress Egress CEP PNP A M Ingress Egress MAC filtering Database targets known MAC Broadcast + Unknown MAC is broadcast to all but ingress port CNP S-VLANz or Port Based

PEB Alternate Mental Model Many PNP, CNP, CEP per S-VLAN – only 1 shown. Many CEP per physical port. Each CEP maps to one S-VLAN only. Physical Port PEB Alternate Mental Model S-Component A M Ingress Egress A M Ingress Egress S-VLANx PNP CEP A M Ingress Egress S-VLANy A M Ingress Egress CEP PNP A M Ingress Egress MAC filtering Database targets known MAC Broadcast + Unknown MAC is broadcast to all but ingress port CNP S-VLANz S-VLANz or Port Based

PEB Alternate Mental Model Many PNP, CNP, CEP per S-VLAN – only 1 shown. Many CEP per physical port. Each CEP maps to one S-VLAN only. Physical Port PEB Alternate Mental Model S-Component C-Component A M Ingress Egress A M Ingress Egress S-VLANx PNP CEP A M Ingress Egress A M Ingress Egress CEP PNP A M Ingress Egress MAC filtering Database targets known MAC Broadcast + Unknown MAC is broadcast to all but ingress port CNP S-VLANz or Port Based

PB Mental Model S-Component Ingress PNP Egress Ingress PNP Egress A M MAC filtering Database targets known MAC Broadcast + Unknown MAC is broadcast to all but ingress port

PB/PEB-Bridge Port Types Direction Filter / Match (Allow) VLAN Action ETYPE Set Action Comment CEP Ingress MATCH_C_VLANS PUSH_S_VLAN 0x88A8 (.ad Q-in-Q)   Egress MATCH_S_VLAN POP_S_VLAN 0x8100 (.Q) PEP PEP integrated into CEP CNP Port Based UNTAGGED ????? CNP S-Tagged MATCH_S_VLANS NO_ACTION NONE PNP Many PNP, CNP, CEP per S-VLAN. Many CEP per physical port. Each CEP maps to one S-VLAN only. CNP port based maps to one S-VLAN only. CNP S-tagged and PNP map to many S-VLAN.

Q-in-Q / PB / IEEE 802.1ad / Stacked VLANs C-Tagged Service Interface PEB CE PEB PB CE FD FD ETH-m C-MAC + S-TAG & ETH-m C-MAC + S-TAG ETH-m C-MAC + S-TAG ETH-m C-MAC + S-TAG #& ETH-m C-MAC + C-TAG ETH-m C-MAC + C-TAG C-Component S-Component S-Component CEP/PEP/CNP PNP PNP PNP # S-TAG based on port + C-TAG & S-TAG can be translated from CNP to PNP

Q-in-Q / PB / IEEE 802.1ad / Stacked VLANs Port Based Service Interface PEB CE PEB Untagged FD FD ETH C-MAC ETH-m C-MAC + S-TAG #& ETH-m C-MAC + S-TAG & ETH-m C-MAC + S-TAG ETH-m C-MAC + S-TAG S-Component S-Component CNP PNP PNP PNP # S-TAG based on port & S-TAG can be translated from CNP to PNP

Q-in-Q / PB / IEEE 802.1ad / Stacked VLANs S-Tagged Service Interface Note no PEB CE PB (*PB) CE FD FD ETH-m C-MAC + S-TAG ETH-m C-MAC + S-TAG & ETH-m C-MAC + S-TAG & ETH-m C-MAC + S-TAG ETH-m C-MAC + S-TAG S-Component S-Component CNP PNP PNP PNP & S-TAG can be translated from CNP to PNP

PB ONF Model Extension Put in package org.onf.cim.bridge.pb

Link Aggregation / IEEE 802.1AX ETH-LAG ETYn … ETYn_CI

Link Aggregation ONF Model Extension Put in package org.onf.cim.linkAgg

ITU-T G.8052

LACP ONF Model Extension Put in package org.onf.cim.linkAgg.lacp

Layering of Technology Extensions Core Model Technology 1 Technology 2 Technology 3

SFP Example From “Amaral, Luis & Troska, Jan & Jimenez Pacheco, Alberto & Dris, Stefanos & Ricci, Daniel & Sigaud, Christophe & Vasey, Francois. (2019). Evaluation of Multi-Gbps Optical Transceivers for Use in Future HEP Experiments. ” https://www.researchgate.net/publication/228717535_Evaluation_of_Multi-Gbps_Optical_Transceivers_for_Use_in_Future_HEP_Experiments

SFP providing ETH PHY to 1Gb/s Signal SFP providing ETH PHY to 1Gb/s ETH 100BASE-FX … 1000BASE-SX ETY PHY = Physical Layer Device MDI = Medium Dependent Interface https://en.wikipedia.org/wiki/Gigabit_Ethernet

SFP+ providing ETH PHY to 10Gb/s Signal SFP+ providing ETH PHY to 10Gb/s ETH 10GBASE-SR … ETY PHY = Physical Layer Device PCS = Physical Coding Sublayer PMA = Physical Medium Attachment PMD = Physical Medium Dependent MDI = Medium Dependent Interface MII = Media independent Interface https://en.wikipedia.org/wiki/10_Gigabit_Ethernet

QSFP providing ETH PHY >10Gb/s to 200Gb/s 100GBASE-SR10 … 200GBASE-DR4 4 lanes of 2 media shown

IPV4 and IPV6 IP IP n n IP can be also on Q-in-Q, mac-in-mac … C-TAG n C-MAC ETH ETY ETH PHY

L3 VLAN Interface (SVI) IP n n ETH-m C-MAC + C-TAG n C-TAG ETH C-MAC ETY OpenConfig IF_ROUTED_VLAN L3 / Vlan SVI Interface (1 per VLAN) Access Port

TCP and UDP TCP n UDP n IP IP

Wireless Transport Phy Radio Path Radio Section Digital / Baseband Modulator / Demodulator RF Transmitter / Receiver Circulator Analogue / RF Waveguide Antenna

Wireless Phy – Hot standby or Frequency Diversity Radio Path Radio Section Digital / Baseband Modulator / Demodulator RF Transmitter / Receiver Circulator PHY Analogue / RF Waveguide PHY Antenna

Wireless Phy – Space Diversity May be 2Tx  2Rx or 1Tx  2Rx Radio Path Radio Section Digital / Baseband Modulator / Demodulator RF Transmitter / Receiver Circulator PHY Analogue / RF Waveguide PHY Antenna

Wireless Phy – Space Diversity 1Tx  2Rx Show the radio path as a FC ? In this case a one to many ! - Need to separate media from signal I think this needs a single more complex LTP like optical – with non traditional LP

Wireless LP - Symbols Receiver with Power Monitor Splitter Rx Wireless LP - Symbols Receiver Receiver with Power Monitor Splitter Symmetric attenuation cir Circulator Tx Transmitter Switch Transmitter with modulator Antenna

Wireless LP – No protection Radio Path Radio Section Digital / Baseband Modulator / Demodulator RF Transmitter / Receiver Circulator LTP boundaries subject to confirmation cir Analogue / RF Waveguide Antenna

Wireless LP – Hot standby Main Protection Transmitter and Receiver protection. No radio path protection. LTP boundaries subject to confirmation Or receive side could be a combiner rather than a switch cir

Wireless LP –Frequency Diversity (or Polarisation) Transmitter and Receiver protection. No radio path protection. LTP boundaries subject to confirmation cir

Wireless LP – Space Diversity (Same as 2 * No Protection) Transmitter and Receiver protection. Radio path protection. LTP boundaries subject to confirmation cir cir

Wireless LP – Space Diversity 1Tx  2Rx LTP boundaries subject to confirmation No Transmitter protection. Receiver protection. Radio path protection. cir

Other hybrids of the previous slides may also be possible Hybrid Diversity / Combined Diversity

Wireless Model : Point – Point Microwave transport ETH or OTN bitstream ETH Radio Path Repeater Radio Section PHY 1+1 Optical SFP