[MIPSHOP-MIH-DT] Re: Still [Transport] issues
Telemaco Melia <telemaco.melia@netlab.nec.de> Tue, 04 September 2007 14:09 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 1ISZ5e-0007L4-JW; Tue, 04 Sep 2007 10:09:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ISZ5d-0007Ks-Mm for mipshop-mih-dt@ietf.org; Tue, 04 Sep 2007 10:09:13 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ISZ5d-0001xs-2A for mipshop-mih-dt@ietf.org; Tue, 04 Sep 2007 10:09:13 -0400
Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 2BA272800035C; Tue, 4 Sep 2007 16:09:16 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ciFTmD0vL+Ie; Tue, 4 Sep 2007 16:09:16 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 19C7C280037E1; Tue, 4 Sep 2007 16:09:06 +0200 (CEST)
Received: from [127.0.0.1] ([10.1.1.217]) by mx1.office over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 4 Sep 2007 16:09:02 +0200
Message-ID: <46DD66FD.8080509@netlab.nec.de>
Date: Tue, 04 Sep 2007 16:09:01 +0200
From: Telemaco Melia <telemaco.melia@netlab.nec.de>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Gabor.Bajko@nokia.com
References: <46D6E642.1030703@netlab.nec.de> <E5E76343C87BB34ABC6C3FDF3B312727016FB307@daebe103.NOE.Nokia.com>
In-Reply-To: <E5E76343C87BB34ABC6C3FDF3B312727016FB307@daebe103.NOE.Nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
X-OriginalArrivalTime: 04 Sep 2007 14:09:02.0004 (UTC) FILETIME=[251B6F40:01C7EEFD]
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mipshop-mih-dt@ietf.org
Subject: [MIPSHOP-MIH-DT] Re: 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 all, Let's go through these issues during the AC and assign action points to update the document accordingly. tele Gabor.Bajko@nokia.com wrote: > 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 > -- Dr. Telemaco Melia telemaco.melia@netlab.nec.de Senior Research Staff Member Tel: +49 (0) 6221 4342- 142 NEC Europe Ltd. NEC Laboratories Europe Network Division Kurfürsten-Anlage 36 69115 Heidelberg GERMANY NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 _______________________________________________ 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