RE: : ISSUE, SIP, Duplicate user-name

Hi!

How is

  "Diameter translation agent must copy the contents of Digest-Username
   attribute to Digest-Username AVP and User-Name AVP"

smoother, easier, and more elegant than

  "Diameter translation agent must copy the contents of Digest-Username
   attribute to User-Name AVP"

?

Maybe somebody forgot to inform me that we work at the
Department of Redundancy Department. :)


BR,
Mikko


> -----Original Message-----
> From: Miguel Garcia [mailto:[email protected]]
> Sent: 27 October, 2005 15:31
> To: Aittola Mikko (Nokia-NET/Tampere)
> Cc: [email protected]
> Subject: Re: [AAA-WG]: ISSUE, SIP, Duplicate user-name
> 
> 
> The need to have a duplication is to have a smooth and easy 
> transition 
> from RADIUS to Diameter, because the RADIUS document already 
> specifies 
> Digest-Username.
> 
> Adding an AVP for consistency and smooth transition is 
> considered more 
> elegant than trying to save a few bytes here. As far as I 
> know, we don't 
> have any requirement that puts constraints on the number of bytes 
> transferred.
> 
> /Miguel
> 
> [email protected] wrote:
> 
> > Hi!
> > 
> > I agree with everything you said about the usage of
> > User-Name AVP.
> > 
> > But my issue was: why is there need for the Digest-Username AVP in
> > the Diameter SIP Application? It is enough to have User-Name AVP.
> > 
> > When Digest is used the SIP-server fills User-Name AVP from the
> > username contained in Authorization header.
> > 
> > When Digest is used the SIP-server fills Digest-Username AVP from
> > the username contained in Authorization header.
> > 
> > Why is there need to transport this information once in
> > the SIP-message, but twice in the Diameter message?
> > It is redundant information.
> > 
> > Conclusion: Digest-Username AVP is not needed in
> > Diameter SIP Application. Let's get rid of it.
> > 
> > 
> > BR,
> > Mikko