diff --git a/additional-info/inter-cluster.md b/additional-info/inter-cluster.md
new file mode 100644
index 0000000000000000000000000000000000000000..159a79bcfcad7a04b28042a10044b9b6132e0ba4
--- /dev/null
+++ b/additional-info/inter-cluster.md
@@ -0,0 +1,96 @@
+
+
+
+Ejemplo de network inter:
+
+```yaml
+apiVersion: "k8s.cni.cncf.io/v1"
+kind: NetworkAttachmentDefinition
+metadata:
+ name: sample-inter-network
+spec:
+ config: '{
+ "cniVersion": "0.3.0",
+ "type": "l2sm",
+ "device": "l2sm-vNet",
+ "kind": {
+ "inter": {
+ "provider": {
+ "name": "<idco-name>",
+ "domain": "<domain-name>"
+ },
+ "accessList": ["<public-key-1>","<public-key-2>",...,"<public-key-N>"]
+ ]
+ }
+ }
+ }'
+```
+Hay un NED conectado al L2S-M switch del nodo master con 10 interfaces veth (como el NED es hostNetwork, nos podemos permitir crear las interfaces y conectarlas directamente -> Necesario que l2sm-switch se despliegue más tarde).
+
+Se crea esta red en cada clúster usando el L2S-M k8s Client. Es necesario para esto:
+ - Que cada cluster tenga previamente un cluster role para poder dar permisos de crear network attachment definitions.
+
+Se crea un network con el mismo nombre dentro del host. Operador avisa al idco de que se ha conectado a la interfaz, se dice cual es el veth empleado. El idco anota, pero no añade aún.
+
+Se crea un secret dentro del cluster con la firma de la public key.
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+ name: sample-one-authorization-key
+type: Opaque
+data:
+ public-key.pem: <firma>
+```
+
+Se attachea al pod, en el campo de spec. QuedarÃa asÃ:
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: mypod
+ annotations:
+ k8s.v1.cni.cncf.io/networks: "sample-inter-network"
+spec:
+ containers:
+ - name: ping
+ image: busybox
+ volumes:
+ - name: authorization-key-volume
+ secret:
+ secretName: sample-one-authorization-key
+```
+
+
+
+
+Si alguien quiere unirse a la red, attachea al pod, utilizando
+
+intercluster:
+ owner de la red en cada cluster crea la red con:
+ provider (idco concreto): campo de nombre y campo de dominio
+ nombre
+ accessList (diferente en cada cluster): se guarda clave pública de cada usuario. (el usuario tiene su clave privada guardada en su pc por ej)
+ clave: tiene identificador, hash, una firma digital.
+ timestamp
+
+ IDCO implementar:
+ cuando hay un request, ver si la clave está bien firmada.
+ guardar la de redes:
+ RED:
+ Cluster1
+ AccessList
+ Cluster2
+ AccessList
+
+
+ 1. Se crea red inter
+ 2 se pide al idco que red intra corresponde, (ahi se haria la utorizacion)
+ 3 se guarda el mappeo de red inter a intra, y se juntan esos pares desde el operador
+ 4 cuando alguien despliega, se usa la red intra
+
+ de momento security parameters, dejarlo en abierto.
+ hacer un dibujillo.
+1.
\ No newline at end of file
diff --git a/examples/inter-cluster/inter-network.yaml b/examples/inter-cluster/inter-network.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..2bb64d3cf7eba1f11e84166989313858e7975ac2
--- /dev/null
+++ b/examples/inter-cluster/inter-network.yaml
@@ -0,0 +1,20 @@
+apiVersion: "k8s.cni.cncf.io/v1"
+kind: NetworkAttachmentDefinition
+metadata:
+ name: sample-inter-network
+spec:
+ config: '{
+ "cniVersion": "0.3.0",
+ "type": "l2sm",
+ "device": "l2sm-vNet",
+ "kind": {
+ "inter": {
+ "provider": {
+ "name": "<idco-name>",
+ "domain": "<domain-name>"
+ },
+ "accessList": ["<public-key-1>","<public-key-2>",...,"<public-key-N>"]
+ ]
+ }
+ }
+ }'
diff --git a/examples/ping-pong/vlink-pingpong.md b/examples/ping-pong/vlink-pingpong.md
new file mode 100644
index 0000000000000000000000000000000000000000..745b03299b680d19e4544c88ecf7fa652056ce22
--- /dev/null
+++ b/examples/ping-pong/vlink-pingpong.md
@@ -0,0 +1,131 @@
+# Vlink 'ping-pong' example
+
+## Introduction
+
+This document provides a guide for L2S-M users. It focuses on creating a virtual link (`vlink`) network and managing traffic flows between pods across different nodes using L2S-M components.
+
+## Prerequisites
+- A Kubernetes cluster
+- Multus CNI installed
+- L2S-M and all of its components deployed
+
+## Overview of Components
+- **L2S-M Operator**: A Kubernetes operator that listens for Kubernetes events and manages network configurations programmatically. It interacts with the L2S-M Controller and uses a database to store network configurations and state.
+- **L2S-M Controller**: An SDN controller based on ONOS, leveraging OpenFlow 1.3 to communicate with L2S-M Switches and manage network flows.
+- **L2S-M Switch**: Pods that facilitate traffic flows as per the L2S-M Controller's instructions, ensuring isolated and direct connectivity between specific pods.
+
+
+## Creating a Vlink Network
+
+The first step involves creating a `vlink` network, named "network-sample", using the NetworkAttachmentDefinition CRD from Multus. This network facilitates direct, isolated communication between pods across different nodes, through custom paths.
+
+
+```yaml
+apiVersion: "k8s.cni.cncf.io/v1"
+kind: NetworkAttachmentDefinition
+metadata:
+ name: network-sample
+spec:
+ config: '{
+ "cniVersion": "0.3.0",
+ "type": "l2sm",
+ "device": "l2sm-vNet",
+ "kind": {
+ "vlink": {
+ "overlay-parameters": {
+ "overlay-paths": [
+ {
+ "name": "first-path",
+ "FromEndpoint": "node-a",
+ "ToEndpoint": "node-e",
+ "path": ["node-c", "node-d"],
+ "capabilities": {
+ "bandwidthBits": "20M",
+ "latencyNanos": "1e6"
+ }
+ },
+ {
+ "name": "second-path",
+ "fromEndpoint": "node-e",
+ "toEndpoint": "node-a",
+ "path": ["node-d","node-b"],
+ "capabilities": {
+ "bandwidthBits": "20M",
+ "latencyNanos": "8e5"
+ }
+ }
+ ]
+ }
+ }
+ }
+}'
+```
+
+### Process Overview
+
+1. **Vlink Creation**: Deploy the `network-sample` YAML configuration to define the vlink network.
+2. **L2SM Operator Activation**: Upon recognizing the new network configuration, the L2SM operator initiates, contacting the L2SM controller. This process includes saving the network path information for future use.
+3. **L2SM Controller**: The controller is informed about the new network but does not initiate traffic flow immediately. It waits for pods to be connected to the network.
+
+## Deploying Pods with Network Annotations
+
+Deployment involves creating pods with specific annotations to connect them to the `network-sample` network. This section explains how PodA and PodB are deployed and managed within the network.
+
+### Deploying pod 'ping'
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: ping
+ labels:
+ app: ping-pong
+ annotations:
+ k8s.v1.cni.cncf.io/networks: '[
+ { "name": "network-sample",
+ "ips": ["192.168.1.2/24"]
+ }]'
+spec:
+ containers:
+ - name: router
+ command: ["/bin/ash", "-c", "trap : TERM INT; sleep infinity & wait"]
+ image: alpine:latest
+ securityContext:
+ capabilities:
+ add: ["NET_ADMIN"]
+ nodeName: NodeA
+```
+
+- **Pod Configuration**: Pod 'ping' is defined with the `network-sample` annotation and an "ips" argument specifying its IP address. If no IP is specified, the connection defaults to layer 2.
+- **Connection to L2SM-Switch**: Pod 'ping' is attached via Multus to an L2S.M component known as the l2sm-switch, controlled by the L2S-M controller. This grants 'ping' two network interfaces: the default (provided by Flannel or Calico) and the new vlink interface.
+
+
+### Deploying PodB
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+ name: pong
+ labels:
+ app: ping-pong
+ annotations:
+ k8s.v1.cni.cncf.io/networks: '[
+ { "name": "network-sample",
+ "ips": ["192.168.1.3/24"]
+ }]'
+spec:
+ containers:
+ - name: router
+ command: ["/bin/ash", "-c", "trap : TERM INT; sleep infinity & wait"]
+ image: alpine:latest
+ securityContext:
+ capabilities:
+ add: ["NET_ADMIN"]
+ nodeName: NodeE
+```
+
+- **Node Placement**: Pod 'pong' is created on NodeE with the `network-sample` network annotation but uses a different IP address than pod 'ping'.
+- **Network Connectivity**: The L2SM controller then establishes the necessary intents and flows, ensuring traffic between 'ping' and 'pong' traverses the predefined nodes. This setup guarantees direct, isolated connectivity between the two pods.
+
+