AW: [802.21] AW: [802.21] Ad hoc telecons
Hi Subir and all,
sorry for the confusion. I feel this is the place where
the misunderstanding is coming and we are going in a circle.
To get it clarified, I have raised these points.
Let me put some points here:
Draft v2, page 92, line 15-16:
"The Media Independent Handover protocol defines frame formats
for exchanging messages between peer MIH Function entites."
Thus, within 802.21 we are defining a MIH frame which
consists of MIH Header and MIH Payload (IS/CS/ES).
Draft v2, page 93, line 34-35:
"The standard describes the MIH packet format, message formats,
and the procedures for MIH message exchange to facilitate
handover in media independent manner."
Defining or selecting a L4/L3 Protocol to transport MIH frame can
be carried out within IETF with 802.21 members participating
in the meetings.
Do you mean with "IS-Protocol" that we take 'ONLY' the payload of
Media Independent Information Service (MIIS) and let IETF to
define/select packet format, port, message exchange(query/response)
and (IP-)transport? This is what I want to get clarified.
I welcome your comments and am open for clarifications.
Thanks,
Kalyan
-----Ursprüngliche Nachricht-----
Von: Subir Das [mailto:subir@research.telcordia.com]
Gesendet: Dienstag, 11. Oktober 2005 20:26
An: Koora Kalyan Com Bocholt
Cc: STDS-802-21@LISTSERV.IEEE.ORG
Betreff: Re: [802.21] AW: [802.21] Ad hoc telecons
Kalyan,
Thanks for the clarification. However, I am little bit confused with your
Protocol and Transport examples.
My understanding is that 802.21 needs to either work with IETF for defining
the IS protocol or choose an existing protocol to support the IS
query/response mechanism. Also if we don't define the protocol
why do we care about transport?
Thanks,
-Subir
Koora Kalyan Com Bocholt wrote:
>Hello All,
>
>just a comment from my side to make couple of things
>clear from our todays telcon. (Or it can also be interpreted as
>clarification needed)
>
>To my understanding, we are getting confused with the terms Protocol,
>Transport and IS content. That could also be a point were we got some
>misunderstanding while speaking about couple of things like IS-Protocol
>w.r.t. discovery.
>
>
>Protocol: set of rules that governs the communications
>between two MIH entities. For IETF it could be L4 Protocol
>(like TCP/UDP) And from my understanding, it is out of scope
>of 802.21 and is IETF scope.
>
>
>Transport: How this protocol is carried between two MIH entities. For
>IETF it could be L3 mechanism like IP. It can also be L2 mechanism. It
>could also be a PPP mechanism (don't know where it is discussed). I
>think this is the place where 802.21 can work together with IETF.
>
>
>IS content/packet: It is the information which is embedded
>in the 'Protocol' and 'transported' between two MIH entities.
>This should be the strict scope of 802.21 and not IETF.
>
>Please correct me, if I am wrong. This may clarify some of
>our points from previous discussion.
>
>Thank you.
>Kalyan
>
>-----Ursprüngliche Nachricht-----
>Von: Stefano M. Faccin [mailto:stefano.faccin@NOKIA.COM]
>Gesendet: Dienstag, 11. Oktober 2005 01:13
>An: STDS-802-21@listserv.ieee.org
>Betreff: Re: [802.21] Ad hoc telecons
>
>
>Colleagues,
>please find enclosed a brief document for discussion on the IS
>reference model and higher layer requirements. Ajay, can you please
>assign it a number and upload it to the 802.21 directory? Thanks,
>Stefano
>
>
>-----Original Message-----
>From: ext Subir Das [mailto:subir@RESEARCH.TELCORDIA.COM]
>Sent: Monday, October 10, 2005 11:43
>To: STDS-802-21@LISTSERV.IEEE.ORG
>Subject: [802.21] Ad hoc telecons
>
>
>
>Our next higher layer requirements telecon is tomorrow.
>Given that there are lot of discussions going on both in .21 mailing
>list and mipshop mailing list regarding this subject, it is important
>that we finish our requirements quickly. In fact, this the good
>time for us to bring the requirements to IETF since mipshop WG is
>discussing their new Charter. Just to remind the people that we had
>discussed the higher layer requirements in Orange County meeting
>(21-05-0348-01-0000-Req_Higher_layer_IS.doc) and for
>further details pl. refer to the meeting minutes
>
>Here is the agenda and telecon details:
>
>Agenda:
>-- IETF requirements -- 1:30 mins
>-- How to proceed (e.g, Mipshop Charter) -- 30 mins
>
>
>Date and Time: October 11, 2005, 9 AM - 11 AM
>
>
>
># of Ports: 20
>
>
>
>PIN: 1913
>
>
>
>Dial-in number: 732-336-6000
>
>
>
>Regards,
>
>-Subir