Segment Routing Architecture

Previdi, Stefano; Shakir, Rob; Filsfils, Clarence; Decraene, Bruno; Ginsberg, Les; Litkowski, Stephane

doi:10.17487/rfc8402

“…• Segment Routing [5] • Data Center Network Virtualization Overlay (NVO3) Networks [6] • Generic Network Virtualization Encapsulation (GENEVE) [7] • Smart Grid [8] • Constrained Application Protocol (CoAP)…”

Section: As Of the Date Of Publication And Following Call(s) For The mentioning

confidence: 99%

“…This provides administrators an opportunity to evaluate the impact of the IPsec solution and resolve issues prior to enterprise-wide deployment. 5. Manage the Solution -Maintain the IPsec components and resolve operational issues; repeat the planning and implementation process when significant changes need to be incorporated into the solution.…”

Section: As Of the Date Of Publication And Following Call(s) For The mentioning

confidence: 99%

See 1 more Smart Citation

Guide to IPsec VPNs

Barker¹,

Dang²,

Frankel³

et al. 2020

View full text Add to dashboard Cite

This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.

show abstract

“…In 183 practice, the terms "IPsec VPN," "IKEv2 VPN," "Cisco IPsec," "IPsec XAUTH," and 184 "L2TP/IPsec" all refer to IPsec-based VPN connections. Some examples of technologies and 185 protocols that use IKE and/or IPsec are: 186 • Ethernet VPN (EVPN) and Virtual eXtensible Local Area Network (VXLAN) [4] • Software-Defined Networking (SDN) and Software-Defined Wide Area Network (SDWAN) • Segment Routing [5] • Data Center Network Virtualization Overlay (NVO3) Networks [6] • Generic Network Virtualization Encapsulation (GENEVE) [7] • Smart Grid [8] • Constrained Application Protocol (CoAP) • Low-Power Wireless Personal Area Network (6LowPAN) [9] • Routing protocol protection [10] such as Border Gateway Protocol (BGP)/BGP Monitoring Protocol (BMP) [11] and Open Shortest Path First (OSPFv3) [12] VPNs protect communications carried over public networks such as the Internet as well as private networks such as fiber networks or Multi-Protocol Label Switching (MPLS) networks. A VPN can provide several types of data protection, including confidentiality, integrity, data origin authentication, replay protection, and access control.…”

Section: Executive Summarymentioning

confidence: 99%

“…Chaining (AES-XCBC), 5 AES-Cipher-Based Message Authentication Code (AES-CMAC) [27], and AES-Galois Message Authentication Code (AES-GMAC) [28] 2.…”

Section: Integritymentioning

confidence: 99%

Guide to IPsec VPNs

2019

Preprint

1

0

View full text Add to dashboard Cite

This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.

show abstract

SRv6‐based Time‐Sensitive Networks (TSN) with low‐overhead rerouting

Kumar

¹

,

Katsalis

²

,

Papadimitriou

³

et al. 2022

Int J Network Mgmt

3

0

View full text Add to dashboard Cite

Time-Sensitive Networks (TSN) aims at providing a solid underpinning for the support of application connectivity demands across a wide spectrum of use cases and operational environments, such as industrial automation and automotive networks. However, handling network updates in TSN entails additional challenges, stemming from the need to perform both flow rerouting and TSN schedule reconfiguration. To address this issue, we propose a softwaredefined network (SDN)-based approach for low-overhead TSN network updates, exploiting segment routing over IPv6 (SRv6) for path control. To this end, we introduce the concept of TSN subgraphs in order to quickly reschedule the flows traversing the problematic area and propose a TSN-aware routing heuristic to minimize the convergence time. We further describe the control plane implementation and its integration into Mininet, which empowers us to conduct a wide range of performance tests. Our evaluation results indicate that our approach yields faster recovery and reduces significantly the number of required reconfigurations upon failures, at the expense of a small SRv6 encoding/decoding overhead.

show abstract

Segment Routing Architecture

Cited by 171 publications

References 1 publication

Guide to IPsec VPNs

Guide to IPsec VPNs

Guide to IPsec VPNs

SRv6‐based Time‐Sensitive Networks (TSN) with low‐overhead rerouting

Contact Info

Product

Resources

About