1. IETF RFC 4120, "The Kerberos Network Authentication Service (V5)":
Section 1.3, "Tickets": This section explicitly states, "Each ticket has a limited lifetime." This directly refutes option B.
Section 5.3.1, "Ticket": The formal definition of a ticket includes the endtime field, which specifies the expiration time, and the caddr field, which contains the client's network address, refuting the claims in options B and D.
2. MIT Kerberos Documentation, "Kerberos V5 System Administrator's Guide":
Chapter 2, "How Kerberos Works": The documentation explains, "The TGT has a lifetime (typically about ten hours). When it expires, you must re-authenticate to the KDC to get a new one." This confirms the finite lifetime of the TGT. It also mentions, "The ticket is stored in a local credentials cache," which validates option C.
3. Neuman, B. C., & Ts'o, T. (1994). Kerberos: An Authentication Service for Computer Networks. IEEE Communications Magazine, 32(9), 33-38. https://doi.org/10.1109/35.312841:
Section "Tickets and Authenticators" (p. 34): The paper, authored by the creators of Kerberos, describes tickets containing a lifetime and a client network address. This foundational document confirms that finite lifetimes and client address binding are integral to the protocol's design.