Hi, the draft states:
user The username. It is encoded in [UTF-8]. It is optional in this packet, depending upon the class of authentication. The old expired draft from 1997 states: user The username. It is optional in this packet. Somehow, an explicit encoding requirement made it into the new draft. It's good to be explicit when designing a protocol; but when it comes to documenting deployed reality it's important to be sure that this really *is* the deployed reality. Are you sure / how sure are you that deployed reality agrees with this change of wording? Greetings, Stefan Winter Am 20.04.2016 um 21:49 schrieb Warren Kumari: > Hi there all, > > The authors of draft-ietf-opsawg-tacacs have updated the document and > would like some review. > > As a reminder, this document is supposed to describe how TACACS > currently works. > We will then publish a new document which improves the security of TACACS. > > I'd really appreciate it if people could review the current document > (Link for easy > clicking: https://datatracker.ietf.org/doc/draft-ietf-opsawg-tacacs/) > and provide feedback to the list by Friday April 29th. > > W _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
