RE: Plan for moving forward

["Dan Wing" <dwing@xxxxxxxxx>]

> > One of the applications I recently 
> > came across  
> > has the Caller having the Callee authenticate first and within the  
> > resulting secure channel use a legacy method to authenticate itself.
> 
> Well, before the Montreal BOF would have been the place and time to  
> bring up that requirement. Luckily, I think you are pretty safe in  
> that this requirement is supported by the solution we are on. SIP  
> allows an INVITE to have and offer and also allows INVITES 
> without an  
> offer where the UAS sends the offer. I think this will meet your  
> requirement.

I don't think flipping who sends the offer is sufficient -- DTLS-SRTP,
as the several documents are now, uses a=fingerprint to authenticate
both endpoints.  What Lakshminath is looking for is a way for one side
to declare that they don't want their certificate used as the 
authentication mechanism, but rather wants something else used (a
password or something; 'legacy method' encompasses a lot of stuff).

-d