Now 6202 visitors
Today:0 Yesterday:0
Total: 152293 212S 50P 4R
2026-10-20, Week 43
Member Login
TACT Journal Homepage
Call for Paper
Committee
Find My Paper
Author Homepage
Statistics & History
Welcome Message
Paper Procedure
FAQ
Paper Archives
Outstanding Papers
Program & Proceedings
Presentation Platform
Hotel & Travel Info
Photo Gallery
Scheduler Login
Seminar
Archives Login
Sponsors




















IEEE/ICACT20260257 Question.4
Questioner: abdelhadi.belfadel@irt-systemx.fr    2026-02-10 ¿ÀÈÄ 4:26:19
IEEE/ICACT20260257 Answer.4
Answer by Auhor hhl9438@chungbuk.ac.kr   2026-02-10 ¿ÀÈÄ 4:26:19
RESTCONF and the control plane rely on TCP/IP, did you observe any significant latency overhead during the path reconfiguration phase that might impact the strict requirements of URLLC services? To be transparent, our research focused on functional validation, so we did not perform quantitative latency measurements of RESTCONF operations. The purpose of our PoC was to demonstrate that the complete cycle of fault detection, path reconfiguration, and restoration operates automatically without manual intervention. We acknowledge that RESTCONF over TCP/IP may introduce overhead for strict URLLC sub-millisecond requirements. However, we mitigated control plane latency by using pre-calculated backup paths, eliminating real-time path computation overhead. Quantitative latency analysis is planned as future work.

Select Voice