Changes between Version 79 and Version 80 of ORCABEN

Timestamp:

10/22/09 15:28:38 (15 years ago)

Author:

hmussman@bbn.com

Comment:

--

ORCABEN

@@ -71 +71 @@
 
 
+We do not use NDL in the demo to provide the broker or site authority with
+resource accounting information – this is a Spiral 2 enhancement. [[BR]]
+
+In this demo the
+NDL request describing a desired BEN connection is passed from the Slice Manager
+directly to the BEN Transit Authority as part of the redeem procedure. The Slice
+Manager first acquires a VLAN tag ticket from the VLAN broker and attaches the
+NDL to this ticket before passing it to the BEN Transit Authority. The BEN Transit
+Authority then validates the ticket and uses the NDL description of the request to
+compute the cross‐layer path across BEN. 
+
+In the BEN Transit
+Authority, NDL is also used in the form of the
+BEN catalogue. This NDL
+catalogue is pre‐loaded into the Jena ontology engine at the start of the demo.  The BEN Transit Authority relies on the contents of the catalogue to
+compute the cross‐layer path (i.e. which network elements need to be configured)
+and provide handler/drivers with necessary configuration information. [[BR]]
+
+Because the contents of the ontology is dynamically updated during the demo, the
+BEN Transit Authority path computation algorithm is intelligent enough to take
+advantage of the existing links whenever possible (existing links are added to the
+ontology as the demo progresses). For example, in the case of two slices, the first
+slice across BEN establishes a fiber connection between respective fiber switches
+and a DWDM connection between Infinera DTNs. The second slice, aware of the
+existence of these links based on the contents of the ontology, does not require any
+fiber switch or Infinera configuration steps and simply configures another VLAN in
+the 6509 over the existing DWDM connection.