RE: : ISSUE: SIP application policy considered unmanageable
"Nelson, David" <[email protected]> Tue, 18 Oct 2005 11:10:15 -0400
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <2A5E4540D4D5934D9A1E7E0B0FDB2D69010325F9@MAANDMBX2.ets.enterasys.com> |
Miguel Garcia writes... > Is it crap? Probably, time will say. Will it be used? Probably not, time > will say. Does it bring a configuration nightmare, due to the required > synchronization between the server and the client? Yes. Can we improve > this nightmare? I don't know how, perhaps removing the generation of > nonces in the client... But if someone has a better proposal, I am able > to listen to. I think "compatilibity with RADIUS" is the driver here. The RADEXT WG was advised that 3PPG2 has already deployed the mode of nonce generation in the client, and requested that feature remain in the RADIUS Digest Authentication specification. This statement was made at the RADEXT WG session at IETF-63. Therefore, I would presume that the feature is in current use. Whether it will be deprecated in future releases or deployments is an open question, of course.