Security Management in Next Generation Networks

Savita Shiwani, Prof. G.N. Purohit, Teena Sharma

Abstract


Speaking in terms of authentication and data encryption, the original design of IPv4 totally lacks security mechanisms. The security option in IPv4 header fields only exists as a means of compartmenting the data carried in the datagram. Furthermore, the “security” that it provides is effective only so long as the receivers of IP traffic obey the standard. Applications can provide the means of ensuring data confidentiality, integrity, and authenticity. Part of the problem with depending on applications is that there is no standard, and the methods of securing data vary from application to application. In this paper IPsec architecture is discussed along with the various modes in which it operates for next generation networks.

Keywords


IPv4, IPv6, Security, IPsec, Tunnel mode, Transport mode

References


http://tools.ietf.org/html/rfc2460

http://tools.ietf.org/html/rfc4861

http://tools.ietf.org/html/rfc4862

http://tools.ietf.org/html/rfc4443

http://tools.ietf.org/html/rfc4291

http://tools.ietf.org/html/rfc4301

William Stallings, “IP Security”, The Internet Protocol Journal - Volume 3, No. 1

"RFC4301: Security Architecture for the Internet Protocol". Network Working Group of the IETF. December 2005. p. 4.

Thayer, R.; Doraswamy, N.; Glenn, R. (November 1998). IP Security Document Roadmap. IETF. RFC 2411.

Hoffman, P. (December 2005). Cryptographic Suites for IPsec. IETF. RFC 4308.

Kent, S.; Atkinson, R. (November 1998). IP Authentication Header. IETF. RFC 2402.

Kent, S. (December 2005). IP Authentication Header. IETF. RFC 4302.

The Internet Key Exchange (IKE), RFC 2409.


Full Text: PDF

Refbacks

  • There are currently no refbacks.




 


All Rights Reserved © 2012 IJARCSEE


Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License.