Transaction-Id: Used by Client To Group The Message - Options: Contains The Identification of Client/server
Transaction-Id: Used by Client To Group The Message - Options: Contains The Identification of Client/server
Transaction-Id: Used by Client To Group The Message - Options: Contains The Identification of Client/server
1993, in RFC, 1531 and later in 1997 modified into RFC, 2131 (Odom 2012; Dye 2010, 8790). The basic
functionality of a DHCP is to provide automatic managed configuration of a particular network to the IP
clients. In IPv6 world new and extended DHCPv6 has been
28 introduced, as described in RFC, 3315. In addition, DHCP is an unreliable protocol and use the UPD port
for receiving the message. The IPv6 client uses UDP port 546 for listening, while in IPv6 server as well as
relay agents uses UDP port 547 for listening. (Davies 2012, 210215; DromsBound
VolzLemon PerkinsCarney 2003.)
As defined by Droms et al (2003) the message format between the DHCP server/client messages is shown
below:
0123 01234567890123456789012345678901 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | msg-type | transaction-id | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+ || . options . . (variable) . || +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+