[SIPForum-techwg] Feedback on bootstrapping

[Sumanth Channabasappa]

Your concern in valid! We just need to better understand the scenarios
we want to support prior to suggesting specific solutions. For example,
one can say that a consumer who purchases (or downloads) a client will
need to first identify a service provider willing to configure and
provide services. Is that a valid assumption? If so, how does the
consumer figure out who provides services (e.g., will there be a central
non-affiliated registry of service providers)? Or is there an assumption
that the service provider will provide the client and hence the client
already knows where to go, and it just needs to figure out the
authentication credentials? 


- S

-----Original Message-----
From: Henning Schulzrinne [mailto:hgs at cs.columbia.edu] 
Sent: Sunday, September 28, 2008 10:05 AM
To: Sumanth Channabasappa
Cc: techwg at sipforum.org
Subject: Re: [SIPForum-techwg] Feedback on bootstrapping

I'm worried that we'll be focusing too much on PBX-style scenarios,  
rather than consumer scenarios. For a consumer device, DHCP is pretty  
useless since the DHCP domain, in general, won't have anything to do  
with the service provider domain (unless, of course, you believe that  
only your DSL or cable provider should be allowed to provide phone  
service).

Henning

On Sep 28, 2008, at 11:29 AM, Sumanth Channabasappa wrote:

> Henning,
>
> The config framework presents various options and guidelines based on
> known deployments that employ different mechanisms. In this sense it
> addresses the scenarios we know about, but does not provide specific
> solutions. We can use these guidelines and formulate one or more
> bootstrapping solutions for our purposes. For example, clients with  
> UIs
> can rely on user-entered domain and initial credentials. Clients  
> without
> UIs will need other mechanisms to obtain the domain name (e.g., DHCP)
> and rely on say content indirection for initial bootstrapping. (If we
> can agree, perhaps there can be one single mechanism, but this  
> requires
> feedback and discussions.)
>
> Let's discuss on the call tomorrow.
>
> - S