Use Cases for Data Center Network Virtualization Overlay Networks

Dunbar, Linda; Isaac, Aldrin; Manral, Vishwas; Toy, Mehmet; Yong, Lucy

doi:10.17487/rfc8151

“…• 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%

“…When a user wants to transfer data across networks, the data is passed from the highest layer through intermediate layers to the lowest layer, with each layer adding additional information. 6 The lowest layer sends the accumulated data through the physical network; the data is then passed up through the layers to its destination. Essentially, the data produced by a layer is encapsulated in a larger container by the layer below it.…”

Section: The Need For Network Layer Securitymentioning

confidence: 99%

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%

“…Common algorithms that are used to generate and verify digital signatures include RSA, the Digital Signature Algorithm (DSA), and the Elliptic Curve Digital Signature Algorithm (ECDSA). 6 NIST-approved digital 754 signature algorithms are specified in [29]. 755 3 Triple DES is deprecated and is expected to be disallowed in the near future.…”

Section: Peer Authenticationmentioning

confidence: 99%

See 1 more Smart Citation

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