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

["Elwell, John" <john.elwell at siemens-enterprise.com>]

OK, understood.

John 

> -----Original Message-----
> From: Winterbottom, James [mailto:James.Winterbottom at andrew.com] 
> Sent: 02 April 2009 08:57
> To: Elwell, John; James M. Polk; ecrit at ietf.org
> Subject: RE: [Ecrit] Use of SIPPING config framework for 
> configuring location
> 
> There is no such thing as "HELD URI" in that sense John, it 
> is HTTPS. If you direct a HELD request at the URI though you 
> will get the HELD semantics if it is a LIS at the other end.
> 
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell at siemens-enterprise.com]
> Sent: Thu 4/2/2009 2:09 AM
> To: James M. Polk; Winterbottom, James; ecrit at ietf.org
> Subject: RE: [Ecrit] Use of SIPPING config framework for 
> configuring  location
>  
> Yes, I was also wondering whether a LIS URI had to be a HELD URI, or
> whether it could just be an HTTP(S) URI, for example?
> 
> John 
> 
> > -----Original Message-----
> > From: James M. Polk [mailto:jmpolk at cisco.com] 
> > Sent: 02 April 2009 08:06
> > To: Elwell, John; Winterbottom, James; ecrit at ietf.org
> > Subject: Re: [Ecrit] Use of SIPPING config framework for 
> > configuring location
> > 
> > John
> > 
> > Or, you can use SIP and not have to implement HELD. HELD 
> doesn't need 
> > to go into every device, and I'd be surprised that it ends up in 
> > every device. Some devices may end up only supporting SIP, 
> and using 
> > the Geolocation header is a fine way of getting either a 
> location URI 
> > or a PIDF-LO.
> > 
> > James
> > 
> > At 01:56 AM 4/2/2009, Elwell, John wrote:
> > >James,
> > >
> > >Thanks. That sounds like a good suggestion. We will give it
> > >consideration.
> > >
> > >John
> > >
> > >
> > > > -----Original Message-----
> > > > From: Winterbottom, James [mailto:James.Winterbottom at andrew.com]
> > > > Sent: 02 April 2009 07:34
> > > > To: Elwell, John; ecrit at ietf.org
> > > > Subject: RE: [Ecrit] Use of SIPPING config framework for
> > > > configuring location
> > > >
> > > > John,
> > > >
> > > > If you have to do something in the SIPPING framework then 
> > it would be
> > > > far better to provide a LIS URI and then do a HELD look up as
> > > > per Phone
> > > > BCP or framework. This would mean what you are providing is
> > > > another LIS
> > > > discovery technique rather than yet another LCP.
> > > >
> > > > Cheers
> > > > James
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: ecrit-bounces at ietf.org 
> > [mailto:ecrit-bounces at ietf.org] On Behalf
> > > > Of Elwell, John
> > > > Sent: Thursday, 2 April 2009 5:07 PM
> > > > To: ecrit at ietf.org
> > > > Subject: [Ecrit] Use of SIPPING config framework for configuring
> > > > location
> > > >
> > > > 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
> > > >
> > > > --------------------------------------------------------------
> > > > ----------------------------------
> > > > 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]
> > > >
> > > >
> > >_______________________________________________
> > >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]
> 
>