RE: [802.21] Higher Layer requirements for IETF: conference calls details
Fellow 802.21 colleagues,
in the recent months the 802.21 group has been having contacts and discussions with several other SDOs. In many occasions there has been the need to clarify what "MIH" actually means. In addition, several parties in 802.21 have become aware of the fact that some scenarios that 802.21 did not target initially can indeed be enabled through 802.21 services. A clear example of this is IP multi-homing and scenarios where at time t0 a mutli-mode terminal with multiple access cards (e.g. 3GPP, .11, .16) has multiple communications over a single IP connection (e.g. data and VoIP) over access A1, and thanks to MIES at time t1 the terminal has a subset of the communications still over A1 but has switched the remaining subset to a different IP connection (or same, depending on the scenarios) over access A2. This scenario is typically not referred to as handoff/handover, but can still be enabled by 802.21 services. Another example is the use of MIIS before any connections with any acces!
s technologies are selected, and MIIS is used to helpt he terminal in network selection. This scenario can also hardly be referred to as handoff/handover.
Due to these reasons, I came to the conclusion that perhaps we may want to stretch us a little bit and rename the group. Currently, the MIH name is strongly connected to handoff. Adopting a name such as Media Independent Mobility Enablers (MIME) or Media Independent Mobility Services (MIMS) may change the name enogh to make it match the actual set of scenarios that 802.21 already enables, while maintaining a strong tie with the current name.
I have been discussing this with some of the 802.21 members present at the San Francisco meeting, and I received positive feedback on the idea. I apologize if I did not get around to talk to all of you. I welcome your feedback/comments, but at the same time I would like to avoid flooding the 802.21 mailing lsit with this issue, since the priority is not very high and much more important discussions need to take place over the list int he next weeks.
BR,
Stefano
________________________________
From: owner-stds-802-21@ieee.org on behalf of ext Stefano M. Faccin
Sent: Fri 7/22/2005 10:25 AM
To: STDS-802-21@listserv.ieee.org
Subject: Re: [802.21] Higher Layer requirements for IETF: conference calls details
Hi,
since last night I received several requests to change the time for the conference on July 26. Though I guess we all understand that no time will work for all the people due to the timezones, It seems in this case July 26 at 21:00 ET really does not work for many. I would like to reschedule this meeting for July 26 9:00 ET. Please let me knwo who has problems with that, and depending on the numbers of replies I will either leave it at 21:00 ET or move it to 9:00 ET.
Thanks for your patience!
Stefano
________________________________
From: Faccin Stefano (Nokia-NRC/Dallas)
Sent: Thu 7/21/2005 7:43 PM
To: STDS-802-21@listserv.ieee.org
Subject: [802.21] Higher Layer requirements for IETF: conference calls details
Hello,
please find enclosed the details for the two conference calls for the ad-hoc discussion on "802.21 Higher layer requirements for IETF."
--------------------------------------------------------------------------------------------------
NOKIA VOICE CONFERENCE
delivered by Elisa
Date: 26.07.2005 at 21:00 ET- 23:00 ET
Conference numbers:
Europe: +358 7180 71870
USA: +1 972 894 6500
Asia: +65 6732 2582
Number of participants: 20
Conference ID: 43662, PIN: 8022155
Please note: you need to have a phone that can generate DTMF tones.
--------------------------------------------------------------------------------------------------
NOKIA VOICE CONFERENCE
delivered by Elisa
Date: 28.07.2005 at 21:00 ET- 23:00 ET
Conference numbers:
Europe: +358 7180 71870
USA: +1 972 894 6500
Asia: +65 6732 2582
Number of participants: 20
Conference ID: 60618, PIN: 8022155
Please note: you need to have a phone that can generate DTMF tones.
--------------------------------------------------------------------------------------------------
BR,
Stefano