10 | | __''GENIStitch.S5.a: Develop high-level architecture for extending GENI stitching for a range of connection/transport types and L2 broadcast domains. Pursue a detailed architecture/design for specific cases of pure !OpenFlow and GRE-tunneled connections. Present enhanced stitching architecture and design at GEC19. Deliver draft architecture and design document to the GENI Project Manager one week prior to GEC19.''__[[BR]] |
11 | | |
12 | | ''Status:''[[BR]] |
13 | | We have updated the architecture and design document for GENI stitching to reflect the comments and inputs from the previous version. A summary of the comments and interest areas that we noted from the email reviews of the previous version of this document are as follows: |
14 | | |
15 | | * A priority for the next couple of GECs is to make stitching more reliable and feature rich |
16 | | * Evaluate further the concepts for GENI Stitching Exchange Points and the Stitching as a Service |
17 | | * Help push stitching support for AL2S AM |
18 | | * Help push support and implementation for VLAN negotiation |
19 | | * Define and implement features to make SCS more automated/monitored. |
20 | | |
21 | | We have updated the GENI Multi-Technology and Multi-Point Layer-2 Stitching Architecture and Design document to reflect these comments and also included some other updates. |
22 | | |
23 | | We have generated the following document: |
24 | | |
25 | | * GENI Multi-Technology and Multi-Point Layer-2 Stitching Architecture and Design, version 4 |
26 | | |
27 | | It is available on the MAX GENI Wiki at this location: |
28 | | |
29 | | * wiki.maxgigapop.net/twiki/bin/view/GENI/Milestone-genistitch-s5b |
30 | | ===> GENI Enhanced Stitching Architecture and Design |
31 | | or direct via: |
32 | | * wiki.maxgigapop.net/twiki/pub/GENI/Milestone-genistitch-s5b/geni-stitch-enhancements-architecture-v4.pdf |
33 | | |
34 | | This document provides a vision for how GENI Stitching can be enhanced and covers the topics as noted below. Based on comments to the previous version of this document, as noted above, and discussions at GEC20, we are planning to focus on the more practical and immediate needs for SCS and stitching. A summary of these immediate focus areas is provided in a new section “Stitching and SCS Near Term Focus Areas”. This new section is the only change to this document as compared to the previous version. |
35 | | |
36 | | This document provide a vision for how GENI Stitching can be enhanced and covers the following topics: |
37 | | * Multi-Technology Multi-Layer Stitching |
38 | | * Stitching with Layer-3 and Layer-2 Tunnels |
39 | | * VXLAN and NVGRE Stitching |
40 | | * !OpenFlow Stitching |
41 | | * Support for Arbitrary Layers |
42 | | * Multi-Point Layer-2 Stitching |
43 | | * Model and RSpec Schema |
44 | | * MP-L2 Stitching Functions |
45 | | * General Stitching Requests and SCS Extension |
46 | | * Advanced Stitching Architecture Considerations |
47 | | * GENI Stitching Exchange Points |
48 | | * Stitching and SCS Near Term Focus Areas |
49 | | |
50 | | |
51 | | We were not able to demonstrate multi-point stitched topologies at GEC20. However, we hope to be able to do so across AL2S by GEC21. This will depend on Internet2 for implementation and testing support. |
52 | | |
53 | | We continued working with Internet2 on their implementation of AL2S based stitching. This included defining the proper formats for AL2S Advertisement and Request Rspec, and describing how they should be constructed and processed. Internet2 AL2S stitching was working in a prototype fashion for GEC20. This included the ability to stitch between two sites directly connected to AL2S as well as for a path where one site is connected to Internet2 ION. One issue noted that will require further fixes by Internet2 is addition of an ability to process more then one stitched path per Request RSpec |
54 | | |