[MIPSHOP-MIH-DT] Still [Transport] issues
<Gabor.Bajko@nokia.com> Tue, 04 September 2007 09:45 UTC
Return-path: <mipshop-mih-dt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISUyZ-0004VA-MZ; Tue, 04 Sep 2007 05:45:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISUyY-0004Qu-I8 for mipshop-mih-dt@ietf.org; Tue, 04 Sep 2007 05:45:38 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ISUyX-0002Zk-U8 for mipshop-mih-dt@ietf.org; Tue, 04 Sep 2007 05:45:38 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l849jATQ014592; Tue, 4 Sep 2007 12:45:35 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Sep 2007 12:45:31 +0300
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Sep 2007 04:45:29 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 04 Sep 2007 04:45:28 -0500
Message-ID: <E5E76343C87BB34ABC6C3FDF3B312727016FB307@daebe103.NOE.Nokia.com>
In-Reply-To: <46D6E642.1030703@netlab.nec.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Still [Transport] issues
Thread-Index: AcfrHPln8FqKbWJBQWy60Gm9f9XJpADuZriQ
References: <46D6E642.1030703@netlab.nec.de>
From: Gabor.Bajko@nokia.com
To: telemaco.melia@netlab.nec.de, mipshop-mih-dt@ietf.org
X-OriginalArrivalTime: 04 Sep 2007 09:45:29.0578 (UTC) FILETIME=[542AB4A0:01C7EED8]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc:
Subject: [MIPSHOP-MIH-DT] Still [Transport] issues
X-BeenThere: mipshop-mih-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIPSHOP Media Independent Handover Design Team List <mipshop-mih-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/mipshop-mih-dt>
List-Post: <mailto:mipshop-mih-dt@ietf.org>
List-Help: <mailto:mipshop-mih-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt>, <mailto:mipshop-mih-dt-request@ietf.org?subject=subscribe>
Errors-To: mipshop-mih-dt-bounces@ietf.org
Hi, I am still wondering, if the transport we have chosen are the right ones. I understand that ES and CS are rather small messages, and having UDP carrying them would be good enough. The problem is, that these two types of messages fall under a "push" model, where the network would unsolicitedly send these messages over udp. If there are to be middlebozes in between, those will cause problems. Current NATs do not have a well specified timeout period but it seems that 30 sec is quite ofter used. IS on the other had is more like a pull model, so no major problems for the middleboxes. If MIH would have applic layer fragmentation, then I'd say udp would certainly fit better here than tcp. We could say that any choice is as good (or as bad) as the other one, it mainly depends on the deployment scenario which we still do no know. I was just trying to point out that avoiding udp fragmentation must not be the only consideration to be taken into account. Hopefully we can spend a few minutes on these issues on the conf call. - gabor -----Original Message----- From: ext Telemaco Melia [mailto:telemaco.melia@netlab.nec.de] Sent: Thursday, August 30, 2007 8:46 AM To: mipshop-mih-dt@ietf.org Subject: [MIPSHOP-MIH-DT] Current status Dear all, I have been reading the input Gabor provided with the IDs draft-bajko-mos-dhcp-options-00 and draft-bajko-mos-dns-discovery-00. Thanks Gabor for the work. Here my comments: o draft-bajko-mos-dhcp-options-00 -1 terminology section should be aligned with the PS doc -2 introduction section: I do not think it is required, I would prefer to refer to the solution doc and move the text there if you want. -3 discussion on co-located MoS: move it to the solution document when we talk about the transport o draft-bajko-mos-dns-discovery-00 - same as before for 1 and 2 - refer to the solution document when you discuss on the selection of the transport During the nect AC we should then discuss the open points noted in the draft. I also would like to receive from Nada an update of the current status and see what text we can included in the first version of the document. As for the time of the AC I would propose to have it at 14:00 CET on Tuesday September 4th. Would be fine with everybody? Please le me know Telemac _______________________________________________ MIPSHOP-MIH-DT mailing list MIPSHOP-MIH-DT@ietf.org https://www1.ietf.org/mailman/listinfo/mipshop-mih-dt
- [MIPSHOP-MIH-DT] Current status Telemaco Melia
- RE: [MIPSHOP-MIH-DT] Current status Zuniga, Juan Carlos
- Re: [MIPSHOP-MIH-DT] Current status Nada Golmie
- RE: [MIPSHOP-MIH-DT] Current status Gabor Bajko
- Re: [MIPSHOP-MIH-DT] Current status Telemaco Melia
- RE: [MIPSHOP-MIH-DT] Current status Zuniga, Juan Carlos
- [MIPSHOP-MIH-DT] Still [Transport] issues Gabor.Bajko
- RE: [MIPSHOP-MIH-DT] Current status Sam Xia
- RE: [MIPSHOP-MIH-DT] Still [Transport] issues Sam Xia
- RE: [MIPSHOP-MIH-DT] Still [Transport] issues Zuniga, Juan Carlos
- RE: [MIPSHOP-MIH-DT]: Next telecon Sam Xia
- RE: [MIPSHOP-MIH-DT] Still [Transport] issues Gabor.Bajko
- [MIPSHOP-MIH-DT] Re: Still [Transport] issues Telemaco Melia
- Re: [MIPSHOP-MIH-DT] Current status Subir Das
- [MIPSHOP-MIH-DT]: Next telecon Subir Das
- RE: [MIPSHOP-MIH-DT]: Next telecon Sam Xia
- Re: [MIPSHOP-MIH-DT]: Next telecon Subir Das
- Re: [MIPSHOP-MIH-DT]: Next telecon Telemaco Melia
- Re: [MIPSHOP-MIH-DT]: Next telecon Subir Das
- RE: [MIPSHOP-MIH-DT]: Next telecon Zuniga, Juan Carlos
- Re: [MIPSHOP-MIH-DT]: Next telecon Subir Das