[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: BOF Speakers Needed



It might be interesting/valuable to map the requirements document into these
catagories - i'm certainly not qualified to do it but this would certainly
help understand the scope of work for the mobile internet

Richard Robinson 
Sprint PCS 
15405 College Boulevard 
Lenexa, Kansas 66219 
913.890.4242 (fax 4100) 
MS - KSLNXZ0201 
rrobin01@sprintspectrum.com 

 

-----Original Message-----
From: David Lindert [mailto:dlindert@cisco.com]
Sent: Tuesday, July 17, 2001 3:43 PM
To: more@psg.com
Cc: David Lindert
Subject: RE: BOF Speakers Needed


Dana,

Read your comments and I think you hit a lot of very good points.

I think I could break down your comments into four categories. 

* those that there already exists capable IETF protocols (example: use of
Mobile IP, SIP and HTTP  to support mobility management)

* those that there are IETF protocols that need work in order to support
wireless but appear to be going in the right direction (examples: caching
registration, or the work on QoS for wireless, or maintaining context during
hand-offs)

* those where the requirements are not clear, and where a question exists as
to why a certain IETF protocol would or would not provide a viable solution
to the underlying problem. (examples: why is layer 3 paging needed when
layer 2 does the job, or why can't a gateway that converts IS-41/GSM Map to
radius not work, or why does the terminal need authentication if the user is
already authenticated).

* those where the requirements are not clear at all. (example: what is a
session, or several cases where its not clear how the legacy telephone
supports a feature, and should we care if it is only a legacy telephone
requirement).

I think areas that might be raised as issues in the BoF would be those in
the second and third, which raise questions that need comment, discussions
that might lead to creating a working group to address. Of course the first
category might generate some comment from operators and the traditional
vendors.

Thanks,
Dave...