Which two options best describe the purpose of session ID and cookie field in a L2TPv3 packet?
A.
The session ID is a 32-bit locally significant field used to identify the call on the destination or
egress tunnel endport. The session ID will be negotiated by the control connection or statically
defined if using the L2TP v3 data plane only
B.
The cookie is a variable length(with a maximum of eight bytes),word-aligned optional field. The
control connection can negotiate this as an additional level of guarantee beyond the regular
session ID lookup to make sure that a data message has been directed to the correct session or
that any recently reused session ID will not be misdirected.
C.
The cookie is a 32-bit locally significant field used to identify the call on the destination or
egress tunnel endpoint. The cookie will be negotiated by the control connection or statically
defined if using the L2TPv3 data plane only
D.
The session ID is a variable length(with a maximum of eight bytes),word-aligned optional field.
The control connection can negotiate this as an additional level of guarantee beyond the regular
cookie lookup to make sure that a data message has been directed to the correct session or that
any recently reused cookie will not be misdirected.