[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MORE email threads
Friends,
I think the threads coming from the email discussions can be summarised as
follows:
1: Definitions need homing (e.g. Session Mobility)
2: Are requirements actually backed by operator DEMAND
3: Is accounting within the scope of the IETF
4: How many of the requirements are applicable to layer 3 rather than layer 2
5: IP in the RAN for the IETF should focus upon IP Service and not
infrastructure
6: Some requirements based upon an "ideal" need justification
7: There is an under estimation of the challenge of a mobile aware Internet
8: Classification of requirements requires further thought
9: Differentiation between mobile and wireless [some even suggest it should be
parameterised upon different transmission characteristics!] (e.g. some require a
deeper and more focused approach to wireless)
10: Reordering of requirements against current IETF WGs
11: Requirements come in 4 categories: a) Some requirements have solution from
IETF (e.g. VoIP), b) some show that some protocols need work (e.g. caching
registration,... c) some requirements are not clear (e.g. why layer 3 paging is
need) and d) some requirements that are too shallow
12: Need to dig deeper into what is meant by interoperability
13: Many areas identified that need work in IETF WGs
14: Motivation of BoF
15: Mobility v Nomadic
16: Inter-Technology Hand-off
17: ID need a "better" focus
18: Lot of requirements outside the scope of mobility and roaming
19: Privacy needs enhancing in particular how you charge for content without
snooping
20: Charging methods
21: What drives each requirement
22: Software Quality Measurements
23: remove any solutions from the ID
24: Need for all IETF protocols to be intrinsic support for mobility not new
protocols
25: Requirements for management (remote) of distributed network elements
(including terminals) missing
Have I missed any?
Regards
Paul
*******************************************************************************
Important. This E-mail is intended for the above named person and may be
confidential and/or legally privileged. If this has come to you in error you
must take no action based on it, nor must you copy or show it to anyone; please
inform the sender immediately.
*******************************************************************************