Subject: RE: モヘ?: RE: [Sip] one question on the authentication forthird-party registration

From: "Paul Pepper" <[email-masked]>
Date: Thu, 15 Dec 2005 10:12:39 -0000

Citel's product allows 3rd party registration for the very reason that
Paul gives, i.e. in shared line configurations. It works well for us.
The ID http://www.ietf.org/internet-drafts/draft-anil-sipping-bla-02.txt
defines a shared line mechanism and describes the use of third party
registration with respect to their use. I would expect organisations
that support this draft to also support third party registration.

Paul.

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On 
> Behalf Of Paul Kyzivat
> Sent: Thursday, December 15, 2005 5:06 AM
> To: Cullen Jennings
> Cc: [email-masked]
> Subject: Re: モヘ?: RE: [Sip] one question on the 
> authentication forthird-party registration
> 
> 
> I'm not aware of any. But I've been discussing use cases for it for 
> years. One is for a boss/secretary arrangement, where the 
> secretary can 
> register for the boss' AOR, but doesn't need the boss' own 
> credentials 
> to do it.
> 
> Somebody has to be first. Go for it!
> 
> 	Paul
> 
> Cullen Jennings wrote:
> > Has anyone build a proxy that allows the configuration of a 
> policy that says
> > Bob is allowed to register for Alice's AOR?
> > 
> > 
> > 
> > On 12/14/05 8:28 AM, "Paul Kyzivat" <[email-masked]> wrote:
> > 
> > 
> >>This should be considered a two step process:
> >>
> >>1) the requestor is authenticated. The From header
> >>    may or may not have anything to do with this.
> >>    The end result of this is that the registrar
> >>    should know "this is Bob requesting to register".
> >>
> >>2) the request is authorized. The question to be
> >>    answered is: "is Bob permitted to register using
> >>    Alice's AOR?" A simple answer to this might be:
> >>    "NO - only alice may register for Alice." A more
> >>    flexible registrar may have an ACL for each AOR
> >>    specifying who may register to it. It might say
> >>    "both Alice and Bob may register for Alice".
> >>
> >>Both of these steps are driven by policy in the registrar, and not
> >>specified by the sip standards. (An authentication 
> *mechanism* - digest
> >>- is specified. But it doesn't say anything about *who* can 
> successfully
> >>authenticate, nor does it say whether this has anything to 
> do with the
> >>contents of the From header.)
> >>
> >>Paul
> >>
> >>Dale R. Worley wrote:
> >>
> >>>On Wed, 2005-12-14 at 09:44 +0900, Mahesh Govind wrote:
> >>>
> >>>
> >>>>If the protocol is not providing a fool proof mechanism  
> for third party
> >>>>registrations , will it lead to hacking ?
> >>>
> >>>
> >>>My point is that the critical factor isn't the protocol, but the
> >>>registrar.  If the registrar does not have sound policies, 
> it can be
> >>>hacked.  If the registrar does not allow third-party 
> registrations, and
> >>>validates all request credentials against the sender name, 
> then it can
> >>>in a sense "depend on the protocol".  Otherwise, the registrar's
> >>>policies are crucial.
> >>>
> >>>Dale
> >>>
> >>>
> >>>
> >>>_______________________________________________
> >>>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> >>>This list is for NEW development of the core SIP Protocol
> >>>Use [email-masked] for questions on current sip
> >>>Use [email-masked] for new developments on the application of sip
> >>>
> >>
> >>_______________________________________________
> >>Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> >>This list is for NEW development of the core SIP Protocol
> >>Use [email-masked] for questions on current sip
> >>Use [email-masked] for new developments on the application of sip
> > 
> > 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email-masked] for questions on current sip
> Use [email-masked] for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip