Re: [Ecrit] Use of SIPPING config framework for configuring location

["Dawson, Martin" <Martin.Dawson at andrew.com>]

That's right...

Typically - given a LIS has more utility than just SIP/VoIP - it's the
kind of infrastructure that the SIP server would want to take advantage
of. That's whether it's by value, by reference, or by trusted TPQ and as
opposed to the SIP server trying to take on some part of the role of the
LIS or, even, the discovery mechanism.

This topic may fall into the "just because you can do it, should you?"
category.

Cheers,
Martin

-----Original Message-----
From: ecrit-bounces at ietf.org [mailto:ecrit-bounces at ietf.org] On Behalf
Of Brian Rosen
Sent: Friday, 3 April 2009 6:39 AM
To: 'Elwell, John'; 'Marc Linsner'; ecrit at ietf.org
Subject: Re: [Ecrit] Use of SIPPING config framework for configuring
location

I think you could configure location if you were really sure you knew
what
the location was.  That, in general, is difficult, but possible in
enterprise.  It means that the the config server has to be able to
figure
out where the phone is plugged into the Ethernet infrastructure/WiFi/...
Often a tough thing to get into the SIP configuration server.  I do
think
that providing a local LIS is not a bad idea, although again, if, say,
the
phone was in a home office you DO NOT want to tell it that the LIS it
should
use is in HQ.

Brian

-----Original Message-----
From: ecrit-bounces at ietf.org [mailto:ecrit-bounces at ietf.org] On Behalf
Of
Elwell, John
Sent: Thursday, April 02, 2009 3:15 PM
To: Marc Linsner; ecrit at ietf.org
Subject: Re: [Ecrit] Use of SIPPING config framework for configuring
location

Marc, 

> -----Original Message-----
> From: Marc Linsner [mailto:mlinsner at cisco.com] 
> Sent: 02 April 2009 13:51
> To: Elwell, John; ecrit at ietf.org
> Subject: Re: [Ecrit] Use of SIPPING config framework for 
> configuring location
> 
> John,
> 
> 1) You probably should propose this idea to GeoPriv.  
> Regardless of impact
> to ECRIT Framework and PhoneBCP, GeoPriv should vet the 
> privacy and security
> impact.
[JRE] Thanks. Done.

> 
> 2) I'm curious what you believe would be the relationship 
> between SIP and
> the access network such that SIP would even know how/where to 
> determine the
> UA location information?  SIP by itself has no idea of 
> geographic location,
> nor visibility to the layers that do know.
[JRE] I know in some proprietary enterprise solutions the configuration
server has access to location information, e.g., from LAN switches. I
guess in that case the configuration server could behave as a LIS.

John


> 
> Thanks,
> 
> -Marc-
> 
> 
> 
> 
> On 4/2/09 2:07 AM, "Elwell, John" <john.elwell at siemens-enterprise.com>
> wrote:
> 
> > We had a SIPPING WG ad hoc meeting during IETF 74, in which the SIP
> > Forum UA-config work was presented. It aims to provide a 
> simple profile
> > of the SIPPING configuration framework and datasets.
> > 
> > The question arose whether the configuration data obtained 
> from the SIP
> > configuration server should have the possibility to contain the
> > geographic location of the SIP UA. Effectively this would make it
> > another LCP. Does this sound reasonable? Can this be done 
> without impact
> > on the ECRIT framework and Phone BCP?
> > 
> > John
> > 
> > _______________________________________________
> > Ecrit mailing list
> > Ecrit at ietf.org
> > https://www.ietf.org/mailman/listinfo/ecrit
> 
> 
> 
_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit

_______________________________________________
Ecrit mailing list
Ecrit at ietf.org
https://www.ietf.org/mailman/listinfo/ecrit

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]