RE: [802.21] Ad hoc telecon for Nov 29th
Junghoon,
>- Higher Layer Requirements for the MIH Function to "function properly"
>(things that will involve higher layers but that do not deal
>with the MIH
>protocol itself: discovery, capabilities...)
>
>=> I am not sure how the MIH Capability Discovery related stuff can be
>classified to the Higher Layer Requirements. Isn't definitely
>within the
>scope of MIH protocol itself? Please take a look at Section
>8.4.1 & 8.5.1 of
>the current spec., D3. It's already defined here. Please let's do not
>consume our energy by re-inventing the wheel on what is
>already defined.
I believe that nothing in the draft is cast in stone until the draft is released as approved. That is normal IEEE process. If there are parties that believe something in the draft may not be 100% ok, I do not see why we should not keep the discussion open.
>Could anyone kindly let me know where this gab in understanding the MIH
>Capability Discovery stuff comes from? Am I miss-understanding
>or missing
>something here?
I believe the misunderstanding is not so much on what is or not in the draft, but what is the of the draft content on higher layer requirements. I do not believe it is realistic for any form of L3 transport to have the discovery of MIH functions (e.g. even just their IP addressed) built in the MIH protocol. That is the equivalent of telling IETF that for the MIH specific purposes we are not using any of the proven existing discovery solutions designed in IETF and we're introducing a new one. I doubt that would fly in IETF. As for capabilities discovery, that can definitely be built in the protocol.
>
>Thanks,
>-Junghoon
>
>So, maybe we should separate the requirements in two
>categories as follows:
>
>Proposition:
>
>1/ The actual MIH Protocol requirements: Transport, Security,
>Reliabilty,
>Time Constraint/QoS Requirements..
>2/ The "other" MIH ES/CS Function requirements: Discovery,
>Capabilities...
>
>
>
>Regards,
>
>
>Mathieu
>
>-----Message d'origine-----
>De : Srinivas Sreemanthula [mailto:Srinivas.Sreemanthula@NOKIA.COM]
>Envoyé : mardi 29 novembre 2005 16:43
>À : STDS-802-21@listserv.ieee.org
>Objet : Re: [802.21] Ad hoc telecon for Nov 29th
>
>The timely delivery of ES/CS messages have been noted. This
>constitutes to
>the delay aspect. Do you have other any others on your mind?
>
>Regards,
>Srini
>
>>-----Original Message-----
>>From: ext Reijo Salminen [mailto:reijo.salminen@seesta.com]
>>Sent: Tuesday, November 29, 2005 3:33 AM
>>To: Sreemanthula Srinivas (Nokia-NRC/Dallas)
>>Cc: Sreemanthula Srinivas (Nokia-NRC/Dallas);
>>stds-802-21@listserv.ieee.org
>>Subject: RE: [802.21] Ad hoc telecon for Nov 29th
>>
>>Hello, 802.21
>>
>>Any ideas how the QoS issues will be addressed in this
>context? It was
>>not mentioned in the slides. Is it out of scope?
>>
>>Best Regards, Reijo Salminen
>>
>>
>>> Hello all,
>>> Here is the related slideset we can start off with.
>>>
>>> Regards,
>>> Srini
>>>
>>>>-----Original Message-----
>>>>From: ext Srinivas Sreemanthula
>>>>[mailto:Srinivas.Sreemanthula@nokia.com]
>>>>Sent: Monday, November 28, 2005 12:26 PM
>>>>To: STDS-802-21@LISTSERV.IEEE.ORG
>>>>Subject: Re: [802.21] Ad hoc telecon for Nov 29th
>>>>
>>>>hello,
>>>>Here is telecon bridge info for Nov 29th about L3 ES/CS
>requirements.
>>>>
>>>>regards,
>>>>Srini
>>>>
>>>>
>>>>US Phone Number: 972-894-6500
>>>>EU Phone Number: +358 7180 71870
>>>>Conference ID: 37162, PIN: 598518
>>>>
>>>>One-time agreement: 29.11.2005 at 08:00 - 10:00
>>>>
>>>>(GMT-06:00) Central Time (US & Canada)
>>>>
>>>>Number of participants: 20
>>>>
>>>>Instructions language: English
>>>>
>>>>
>>>>________________________________
>>>>
>>>> From: ext Ajay Rajkumar [mailto:ajayrajkumar@lucent.com]
>>>> Sent: Friday, November 25, 2005 7:22 AM
>>>> To: STDS-802-21@listserv.ieee.org
>>>> Subject: [802.21] Ad hoc telecons for the next two months
>>>>
>>>>
>>>> *
>>>> Hi everyone,
>>>>
>>>> The external meeting documents server has been updated
>>and synced. At
>>>>the end of the just concluded Vancouver session the working group
>>>>approved a set of telecon for the next two months.
>>>>
>>>> Here is the schedule of these telecons again. Please
>>note that all
>>>>times are from 9-11 am EST, which was acceptable to all and
>seems to
>>>>be most suitable time for all time zones concerned.
>>>>
>>>>
>>>> *
>>>> *IS Higher Layer Transport Requirements
>>>> December 8, 2005
>>>> - January 10, 2006
>>>>
>>>> *ES/CS Higher Layer Transport Discussion
>>>> - November 29, 2005
>>>> - December 13, 2005
>>>> - January 12, 2006
>>>>
>>>> *802.11 Requirements
>>>> - January 5, 2006
>>>> *
>>>> 802.16 Requirements
>>>> -December 15, 2005
>>>>
>>>>
>>>> The telecon bridge number and codes would be announced
>>closer to the
>>>>respective telecon dates.
>>>>
>>>> Best Regards,
>>>> -ajay
>>>>
>>>> Ajay Rajkumar
>>>> Chair, IEEE 802.21 WG
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>