Changes between Version 131 and Version 132 of GAPI_AM_API_DRAFT

Timestamp:

04/27/15 11:22:42 (9 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_DRAFT

@@ -445 +445 @@
 Experimenters want to be able to offer services on GENI for other slices, or to connect multiple slices together. This is termed 'cross slice stitching'; connecting 2 slices at layer 2. As background, note that GENI has the notion of a 'shared VLAN'. This is a VLAN that gets a name and that is marked public, allowing anyone to connect to it. At InstaGENI, there is a `PerformOperationalAction` to convert a newly allocated LAN into a shared VLAN. This topic was discussed at [wiki:GEC21Agenda/DeveloperRoundtable#Cross-SliceStitching1 GEC21], and again at [wiki:GEC22Agenda/DeveloperRoundtable#CrossSliceStitching1 GEC22].
 
-'''Proposal''': Add to the existing POA `geni_sharelan` a new option `restricted` with default value `false` (old behavior). When true, the created shared VLAN requires a new credential when requesting a connection to this new Shared VLAN.
+'''Proposal''': Add to the existing POA `geni_sharelan` a new option `geni_sharelan_restricted` with default value `false` (old behavior). When true, the created shared VLAN requires a new credential when requesting a connection to this new Shared VLAN.
 The POA method will return in this case an entry `geni_credential` that is a GENI SFA credential with owner <user calling the method> and target <sliver  of the shared VLAN, or the shared VLAN in some way; contents are not specified but should be sufficient for the aggregate to authorize the call>.