Matches in UGent Biblio for { <https://biblio.ugent.be/publication/3260137#aggregation> ?p ?o. }
Showing items 1 to 35 of
35
with 100 items per page.
- aggregation classification "P1".
- aggregation creator person.
- aggregation creator person.
- aggregation creator person.
- aggregation creator person.
- aggregation creator person.
- aggregation date "2013".
- aggregation format "application/pdf".
- aggregation hasFormat 3260137.bibtex.
- aggregation hasFormat 3260137.csv.
- aggregation hasFormat 3260137.dc.
- aggregation hasFormat 3260137.didl.
- aggregation hasFormat 3260137.doc.
- aggregation hasFormat 3260137.json.
- aggregation hasFormat 3260137.mets.
- aggregation hasFormat 3260137.mods.
- aggregation hasFormat 3260137.rdf.
- aggregation hasFormat 3260137.ris.
- aggregation hasFormat 3260137.txt.
- aggregation hasFormat 3260137.xls.
- aggregation hasFormat 3260137.yaml.
- aggregation isPartOf urn:isbn:9781479900497.
- aggregation language "eng".
- aggregation publisher "IEEE".
- aggregation rights "I have transferred the copyright for this publication to the publisher".
- aggregation subject "Technology and Engineering".
- aggregation title "Fast failure recovery for in-band OpenFlow networks".
- aggregation abstract "In OpenFlow, control and data plane are decoupled from switches/routers. Direct programming of routers/switches is realised from one or more servers (so called controllers). In the case of an in-band OpenFlow network, the control traffic (traffic to or from the controllers) is sent on the same channel used to transport data traffic. Therefore, when a failure occurs along the data traffic path, both control and data traffic can be affected. This paper explains how failure recovery can be deployed in such a network. To achieve carrier-grade quality, the network should be able to recover from the failure within 50 ms. We apply two well-known recovery mechanisms -restoration and protection-for the control and the data traffic, and run extensive emulation experiments. The emulation results show that restoration does not allow to recover within 50 ms. Moreover, the restoration of the control traffic delays the restoration of the data traffic. The emulation results also show that protection for both control and data traffic can meet the carrier-grade recovery requirement, even in a large-scale network serving many flows.".
- aggregation authorList BK199205.
- aggregation endPage "59".
- aggregation startPage "52".
- aggregation aggregates 3260139.
- aggregation aggregates 3260146.
- aggregation isDescribedBy 3260137.
- aggregation similarTo LU-3260137.