RE: [802.21] Ad hoc telecon for Dec 13th
On the first point, slide 3 shows the same. MIH discovery is agreed to
be at the transport level and the MIH capability discovery is defined in
MIH protocol. So, they indicated in two steps. I made one box to
indicate that this a "setup" state before moving to "active".
The second point is interesting and I agree with you on this. Do you see
that we do this negotiation as part of registration or after
registration? I think we can do this during registration procedure
because during registration the supported set of commands and events may
change on either side based on their relationsip. We also have
capability discovery to say what services and what events/commands are
supported on the other end before registration. But we need to revisit
that to improve some parts of it.
>From: ext Olvera-Hernandez, Ulises
>Sent: Tuesday, December 13, 2005 7:31 AM
>To: Sreemanthula Srinivas (Nokia-NRC/Dallas);
>Subject: RE: [802.21] Ad hoc telecon for Dec 13th
>Thanks for taking the lead on this area.
>I won't be able to attend the conference, but I have a couple of
>1) The slides indicate that the registration process occurs
>after the discovery procedure. Do you include the Capability
>Discovery procedure in this statement? Knowing the capability
>in prior to registration might reduce unnecessary siganalling.
>2) The registration procedure also indicates that services
>might not be provided without an active session. However both
>peers might need to agree on what services can be acceptable.
>E.g., a UE might register for ES but in order to accept
>commands from the remote peer in the network a negotiation
>process might need to take place so that both peers agree on
>the level service that should be provided (E.g., the UE might
>not accept all commands coming from the network).
>From: Srinivas Sreemanthula [mailto:Srinivas.Sreemanthula@NOKIA.COM]
>Sent: Monday, December 12, 2005 11:24 PM
>Subject: Re: [802.21] Ad hoc telecon for Dec 13th
>Here is the slideset that is built on top of last meeting and
>some email discussions. We can use these topics for open
>discussions and draw some conclusions.
>>From: ext Srinivas Sreemanthula
>>Sent: Monday, December 12, 2005 3:09 PM
>>Subject: Re: [802.21] Ad hoc telecon for Dec 13th
>>Here is telecon bridge info for Dec 13th 9am-11am EST about
>>L3 ES/CS requirements. An agenda will follow soon.
>> US Phone Number: 972-894-6500
>> EU Phone Number: +358 7180 71870
>> Conference ID: 37494, PIN: 561988
>> Type of reservation: Single reservation: 13.12.2005
>> (GMT-06:00) Central Time (US & Canada) Number of
>>participants: 20 Instructions language: English
>> From: ext Ajay Rajkumar [mailto:email@example.com]
>> Sent: Friday, November 25, 2005 7:22 AM
>> To: STDSfirstname.lastname@example.org
>> Subject: [802.21] Ad hoc telecons for the next
>> 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
>> *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 Rajkumar
>> Chair, IEEE 802.21 WG