Re: [MIPSHOP-MIH-DT] draft-melia-mipshop-mstp-solution-01a.txt

Hi Gabor,

Gabor.Bajko@nokia.com wrote:
> A few issues:
>
> Change the proposed sentence: "The MN SHOULD discover the server's
> preferred transport mechanism to use in each service as defined in
> [I-D.bajko-mos-dns-discovery]." to:
>
> "The MN MAY use the procedures defined in [I-D.bajko-mos-dns-discovery]
> to discover additional transport protocols supported by the server."
>
>   
That's fine.
> The sentence "Additionally, instead of retransmitting an unacknowledged
> message, the MIH may choose to update the information and transmit a new
> message." is out of context. We should talk about transport issues, and
> not MIH level decisions. I would prefer NOT to add that sentence into
> the draft.
>
>   
I agree with you. However, this is only pointing out that letting the 
MIH handle retransmissions has the additional benefit of not having to
retransmit the same information. It can be part of the trade-off 
analysis discussion.

-Nada
> - gabor 
>
> -----Original Message-----
> From: ext Nada Golmie [mailto:nada.golmie@nist.gov] 
> Sent: Thursday, November 15, 2007 10:13 AM
> To: Telemaco Melia
> Cc: Zuniga, Juan Carlos; mipshop-mih-dt@ietf.org
> Subject: Re: [MIPSHOP-MIH-DT] draft-melia-mipshop-mstp-solution-01a.txt
>
> Hello All,
>
> Juan-Carlos and I worked on this last paragraph in section 6. We believe
> that section 6 is OK with the following change: 
>
> 1) Replace this paragraph:
>
> It is mandatory the use of UDP and TCP as default transport
>    mechanisms implemented in the server side.  The MN SHOULD discover
>    server transport options.  The MN can choose one of the mandated
>    transport protocols.  It is optional the use of SCTP both for server
>    side and MN side.
>
>
> with this one:
>
> The server side MUST support both UDP and TCP for MIH transport, and the
> MN MAY support either UDP or TCP. 
> Additionally, the server and MN MAY support additional transport
> mechanisms.
> The MN SHOULD discover the server's preferred transport mechanism to use
> in each service as defined in [I-D.bajko-mos-dns-discovery].
>
>
>
> 2) Add the following sentence at the end of last paragraph of section
> 6.3:
>
> Additionally, instead of retransmitting an unacknowledged message, the
> MIH may choose to update the information and transmit a new message.
>
>
>
> 3) Add the following reference to the end of first sentence of section
> 6:
>
> Once the Mobility Services have been discovered, MIH peers MAY
>    exchange information over TCP, UDP or any other transport supported
>    by both the server and client, as described in [I-D.draft-rahman-
> mipshop-mih-transport].
>
> 4) Add the following reference
>
> [I-D.draft-rahman-mipshop-mih-transport]Rahman, A., Olvera-Hernandez,
> U., Zuniga, JC., Wafta, M., and Kim, H.W., "Transport of Media
> Independent Handover Messages Over IP,"
> draft-rahmanmipshop-mih-transport-03 (work in progress), July 2007.
>
> Any comments?
>
> -Nada and Juan-Carlos
>
>
> _______________________________________________
> MIPSHOP-MIH-DT mailing list
> MIPSHOP-MIH-DT@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt
>   

_______________________________________________
MIPSHOP-MIH-DT mailing list
MIPSHOP-MIH-DT@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt