RE: [Sip] Re: Callerprefs: Mobility tag

"Mary Barnes" <mbarnes@nortelnetworks.com> Wed, 23 April 2003 13:34 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17678 for <sip-archive@odin.ietf.org>; Wed, 23 Apr 2003 09:34:07 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3NDkA925759 for sip-archive@odin.ietf.org; Wed, 23 Apr 2003 09:46:10 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NDjJ825699; Wed, 23 Apr 2003 09:45:22 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NDh3825575 for <sip@optimus.ietf.org>; Wed, 23 Apr 2003 09:43:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17557 for <sip@ietf.org>; Wed, 23 Apr 2003 09:30:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198KMj-0003kU-00 for sip@ietf.org; Wed, 23 Apr 2003 09:32:49 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx with esmtp (Exim 4.12) id 198KMj-0003jE-00 for sip@ietf.org; Wed, 23 Apr 2003 09:32:49 -0400
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3NDVcR29169; Wed, 23 Apr 2003 08:31:38 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id <HNP4YFA3>; Wed, 23 Apr 2003 08:31:38 -0500
Message-ID: <1B54FA3A2709D51195C800508BF9386A09DABCEC@zrc2c000.us.nortel.com>
From: Mary Barnes <mbarnes@nortelnetworks.com>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>, 'Henning Schulzrinne' <hgs@cs.columbia.edu>, Paul Kyzivat <pkyzivat@cisco.com>
Cc: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, "'sip@ietf.org'" <sip@ietf.org>
Subject: RE: [Sip] Re: Callerprefs: Mobility tag
Date: Wed, 23 Apr 2003 08:31:38 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>

I think there is still some value in just keeping it at "Fixed" and "Mobile"
(per my initial reaction that the "or somewhere in between" needed to be
deleted).  My original posting had been to perhaps expand, but I've been
thinking about that further and clearly there is no compelling reason.  

I think it is still useful for the specific context whereby I as a caller
don't want my calls to go to people's mobiles (even if they do want them to)
OR I only want to go to their mobile or fixed contacts.  Given the current
24/7 reachability empowered by SIP, I think this is useful functionality.  I
also think this is useful given that it's difficult to attach a "personal"
vs. "business" association to mobiles, since most folks use them for both.
Now, this is all predicated on folks registering their contacts with these
tags, but I know that for our system we have implemented the "mobile" tag
and do find it useful. 

Mary.

-----Original Message-----
From: Drage, Keith (Keith) [mailto:drage@lucent.com]
Sent: Wednesday, April 23, 2003 5:33 AM
To: 'Henning Schulzrinne'; Paul Kyzivat
Cc: Barnes, Mary [NGC:B602:EXCH]; Jonathan Rosenberg; 'sip@ietf.org'
Subject: RE: [Sip] Re: Callerprefs: Mobility tag


I think I agree with Paul on this one.

Unless someone comes up with a single set of semantics of what it means, it
should go away.

What makes it useless is that the explanation below gives two, possibly
mutually incompatible, semantics for the same parameter.

I would also point out that the charging characteristics (in Europe) for
mobile and fixed line calls are so completely different that it is difficult
to conclude on the basis of a single call whether one is cheaper or not.
Yes, roaming will maked the roaming user (who could either be calling or
called) incur call charges, but the roaming user makes a personal choice to
turn their phone on when they are roaming. And the bulk of subscribers
making lots of calls are not roaming.

Keith

Keith Drage
Lucent Technologies
Tel: +44 1793 776249
Email: drage@lucent.com 

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: 23 April 2003 02:51
> To: Paul Kyzivat
> Cc: Mary Barnes; Jonathan Rosenberg; 'sip@ietf.org'
> Subject: [Sip] Re: Callerprefs: Mobility tag
> 
> 
> I think this is useful. Yes, having something like "don't call if it 
> costs extra" or "don't call if the person is in a car or 
> meeting" would 
> be better, but until everybody uses RPIDS, 'no mobile phone' 
> is a pretty 
> good approximation and actually implementable. (In European 
> countries, 
> the *caller* pays more for mobile calls, so this is a real 
> concern. And 
> mobile is indeed the distinction that matters, not something else.)
> 
> Paul Kyzivat wrote:
> 
> > I've always had trouble with the semantics of this feature. All the 
> > examples I can think of for using it really depend of coincidental 
> > association between mobility and other features.
> > 
> > For instance, *why* would I prefer to call someone on their 
> fixed phone 
> > rather than their mobile phone?
> > 
> > - because use of the mobile phone is expensive?
> > 
> > - because I know the fixed phone is in a particular location
> >   and I only want to reach them if they are there.
> > 
> > Neither of these are really directly related to the fixed 
> nature of the 
> > phone.
> > 
> > I think I asked Jonathan about this and he felt it should be kept 
> > because it had been around for a long time and we didn't have 
> > justification for removing it. Personally I think it could 
> just go away.
> > 
> >     Paul
> > 
> > Mary Barnes wrote:
> > 
> >> In section 9.9, the mobility tag is described as 
> "indicates whether the
> >> device is fixed, wireless or somewhere in-between", 
> however, there is no
> >> definition for the somewhere in-between. 
> >> So, my initial reaction would be to reword this as 
> "indicates whether the
> >> device is fixed or wireless", but then I got to thinking 
> about what could
> >> have been meant by some in-between and I think there might be some 
> >> value in
> >> defining some of those now. 
> >> One term I had considered was "nomadic" as the 
> "in-between".  But, then I
> >> also got to thinking that perhaps "WiFi" is a good example of the
> >> "in-between".  The usefulness of these really depends upon how they
> >> would/could be used.  The one example I saw in the 
> usecases draft was 
> >> around
> >> wanting to contact someone only on their mobile phone.  
> The inverse of 
> >> this
> >> could be that you absolutely don't want to contact them on 
> their mobile
> >> phone, but would want to contact them on anything else or 
> perhaps only if
> >> they're "fixed" or "WiFi". "Nomadic" might be useful for scenarios 
> >> whereby
> >> one's network connectivity is via tunneling, thus it's 
> indicative not 
> >> being
> >> reachable at the "fixed" device (eg. the hard SIP client), 
> but you are
> >> available on your soft SIP client working from home.   I 
> haven't thought
> >> this all the way through, but I do think additional terms could be 
> >> extremely
> >> useful.
> >>
> >> Mary H. Barnes
> >> mbarnes@nortelnetworks.com
> >>
> >>
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org 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 sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip