1 / 21

Stitching framework GN2-JRA3

Stitching framework GN2-JRA3. version 0.6 Victor Reijs victor.reijs@heanet.ie. The layers. Each layer (not necessarily OSI layers) has essential items: Layer D+: End User (human/application): e.g. user speed, user max. datagram size.

toril
Télécharger la présentation

Stitching framework GN2-JRA3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Stitching frameworkGN2-JRA3 version 0.6Victor Reijsvictor.reijs@heanet.ie

  2. The layers • Each layer (not necessarily OSI layers) has essential items: • Layer D+: End User (human/application): e.g. user speed, user max. datagram size. • Layer C (~routing): (P)IP layer: e.g. IP Port number, IP address and subnet, DHCP • Layer B (~switching): Ethernet: e.g. VLAN#, MAC addressL2 MPLS VPN: e.g. VC_ID#SDH/SONET: e.g. VCG#, VC-3/VC-4 • Layer A (~physical): interface: e.g. framing, medium (lambda), clock speed • Perhaps others layers could be needed, but the framework should stay the same

  3. Layer D+: The User • The user (a human or application) has expectation about speed and maximum datagram size he/she wants to transport at his/her level. • The user may have more wishes (like error rate, delay, jitter, etc.) but these are for this moment not handled. • Such additonal items should be handled in a comparable way (as simple extension and no framework change) • The Layer D+ layer is only incorporated in the ethernet-ethernet scenario slide (due to laziness;-) This should be added to all other scenarios.

  4. Communication channel between domains (1/2) • There are two parts of the comm. channel: • Management parthandled by e.g. control plane, IDM, phone, e-mailThe management part is for items that are not directly configured in a domain (althought this information could be used indirectly for configuring things, like the grey items) • Configuration parthandled by e.g. DM, CLI, provisoning systemThese are items that are directly being configured in the domain.

  5. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC3 CC1 Ethernet – PIP (sc9) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr IP Addr1/sub1 IP Addr2/sub1 IP Addr3/sub2 IP Addr4/sub2 [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] [VLAN2] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] DHCP XC XC framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  6. Communiation channel between domains (2/2) • In principle there is only one comm. channel between the each domain (and the end systems, e.g. E-A and E-B) • The communication can be between different (BoD) system parts; IDM, DM or technology/provisioing domain • The comm. channels (red lines) are the ones that have to be defined in stitching. The comm. channel of D-x near CC1 and CC3 (or CC4 in slide 9) are the end devices of the (BoD) system. • Also it must be defined how to derive essential technology specific parameters (grey items) and how to calculate the blue items. • Some items are optional ([])

  7. How items are treated • All items start and stop at a certain domain (black filled dot: ): peering points • Some items are used within the domain (black open dot: ) and go to other domains: learning points • These learning points can results in additional items (grey background) specific to a technology/provisioning domain (minimal here is making a cross connect (XC/LSP)) • Some items are not used in a specific domain, but need to be transported by IDM (or DM?) protocol (straight line through domain) to next domain • Some items are important for end-to-end performance, like the maximum datagram size (mds) and the actual data speed (blue background). These need to be compared with user speed and user mds. • Some items can have end-to-end significance (e.g. possibly VLAN# [except when there is a L3 in between], IP Port, etc.) • Some items don’t have to propagate end-to-end, like the VCG# or VC_ID#.

  8. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC3 CC1 Ethernet – PIP (sc9) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr IP Addr1/sub1 IP Addr2/sub1 IP Addr3/sub2 IP Addr4/sub2 [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] [VLAN2] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] DHCP XC XC framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  9. Other dependancies • Some things are not essential for framework: as they are just as solve-able as when using manual procedures • But when automating the following need to be incorporated: • an abstract notation (XML schema) • technology agnostic IDM • path finding issues • IDM-IDM and IDM-DM protocol • implementation issues • incompatible technologies (LAN-WAN PHY 10 GE) • etc. • These things will be defined elsewhere in GN2-JRA3, but stitching will certainly provide input to these. The following slides are only example. I am not an expert on all technologies.So your input is wanted

  10. Scenarios covered in these slides • SDH-SDH (scenario 5a) • SDH-SDH-SDH (scenario 5b) • Ethernet – L2 MPLS VPN (scenario 6) • L2 MPLS VPN – L2 MPLS VPN (scenario 8a: no VC_ID# stitching) • L2 MPLS VPN – L2 MPLS VPN (scenario 8a: VC_ID# stitching) • Ethernet –PIP (scenario 9) • Ethernet –Ethernet (scenario 14a: Q between BoDs) • Ethernet –Ethernet (scenario 14b: QinQ between BoDs) • L2 MPLS VPN – OOO (scenario 15)

  11. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC1 CC3 SDH – SDH (sc5a) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr1 IP Addr1/sub1 IP /sub1Addr4 [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] MAC1 MAC2 MAC3 MAC4 VCG1 VC-3/VC-4 XC XC VCAT/LCAS VCAT/LCAS framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  12. E-A E-B IP IP eth eth D-1 D-2 D-3 phys phys CC1 CC3 CC4 CC2 SDH – SDH – SDH (sc5b) Speed/mds Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Port1 IP Addr1 IP Addr1/sub1 IP /sub1Addr4 [DHCP1] [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] MAC1 MAC2 MAC3 MAC4 VCG1 VCG2 VC-3/VC-4 VC-3/VC-4 XC XC XC VCAT/LCAS VCAT/LCAS VCAT/LCAS framing1 framing2 framing3 framing4 medium1 medium2 medium3 medium4 cl. speed1 cl. speed2 cl. speed3 cl. speed4

  13. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC1 CC3 Ethernet – L2 MPLS VPN (sc6) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] [VLAN1] Q or QinQ [VLAN1] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] LSPx XC framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  14. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC1 CC3 L2 MPLS VPN – L2 MPLS VPN (sc8a)(no VC_ID# stitching) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] [VLAN1] Q or QinQ [VLAN1] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 LSPx LSPy framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  15. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC1 CC3 L2 MPLS VPN – L2 MPLS VPN (sc8b)(VC_ID# stitching) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] [VLAN1] VC_ID1 VC_ID2 [VLAN1] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 LSPx LSPy framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  16. E-A E-B IP IP eth eth D-1 D-2 phys phys CC2 CC3 CC1 Ethernet – PIP (sc9) Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP Addr IP Addr1/sub1 IP Addr2/sub1 IP Addr3/sub2 IP Addr4/sub2 [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] [VLAN2] MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] DHCP XC XC framing1 framing2 framing3 medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  17. D-1 D-2 CC1 CC3 CC2 Ethernet – Ethernet (sc14a)(Q) E-B E-A uspeed uspeed uspeed User User umds umds umds Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP IP IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] Q eth eth MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] [.p] XC XC framing1 framing2 framing3 phys phys medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  18. D-1 D-2 CC1 CC3 CC2 Ethernet – Ethernet (sc14b)(QinQ) E-B E-A uspeed uspeed uspeed User User umds umds umds Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP IP IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] VLAN1 VLAN1 QinQ eth eth MAC1 MAC2 MAC3 MAC4 MAC5 MAC6 [.p] [.p] XC XC framing1 framing2 framing3 phys phys medium1 medium2 medium3 cl. speed1 cl. speed2 cl. speed3

  19. D-1 D-2 CC1 CC3 CC2 L2 MPLS VPN – OOO (sc15) E-B E-A uspeed uspeed uspeed User User umds umds umds Speed/mds Speed/mds IP Port1 IP Port1 IP Port1 IP IP IP Addr1/sub1 IP Addr2/sub1 [DHCP1] [DHCP1] [DHCP1] [VLAN1] [VLAN1] [VLAN1] eth eth MAC1 MAC2 MAC3 MAC6 [.LSPx] XC framing1 framing2 framing2 phys phys cl. speed2 cl. speed2 cl. speed1 medium1 lambda2 lambda2

  20. Stitching jigsaw puzzle

  21. Things to elaborate • Multiplexing/demultiplexing VLANs to different destination • Do VLAN# need to be network unique (or only interface unique)? • How are MAC addresses handled in ethernet networks (each interface unique MAC address or can there be duplications). • More then two domains • Incorporate findings into/from path finding (paths from pathfinder, stitching feasibility check, etc.)

More Related