[Mobopts] Re: Comments and reference for section 6.19 of draft-irtf-mobopts-ro-enhancements-01.txt

Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es> Thu, 06 October 2005 18:35 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENaaT-0001lG-BO; Thu, 06 Oct 2005 14:35:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENaaR-0001l5-RG for mobopts@megatron.ietf.org; Thu, 06 Oct 2005 14:35:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21517 for <mobopts@irtf.org>; Thu, 6 Oct 2005 14:35:19 -0400 (EDT)
Received: from smtp03.uc3m.es ([163.117.136.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENajX-0004nQ-78 for mobopts@irtf.org; Thu, 06 Oct 2005 14:44:48 -0400
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 84A8082022; Thu, 6 Oct 2005 20:35:10 +0200 (CEST)
Received: from [192.168.0.14] (wlan-ap.netlab.nec.de [195.37.70.130]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 0A80A8204A; Thu, 6 Oct 2005 20:35:10 +0200 (CEST)
From: Carlos Jesús Bernardos Cano <cjbc@it.uc3m.es>
To: Christian Vogt <chvogt@tm.uka.de>
In-Reply-To: <43453380.9090201@tm.uka.de>
References: <1123166941.21156.10.camel@acorde> <43453380.9090201@tm.uka.de>
Organization: UC3M
Date: Thu, 06 Oct 2005 20:35:37 +0200
Message-Id: <1128623737.6452.11.camel@acorde>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
X-Spam-Score: 2.4 (++)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: MOBOPTS <mobopts@irtf.org>
Subject: [Mobopts] Re: Comments and reference for section 6.19 of draft-irtf-mobopts-ro-enhancements-01.txt
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>, <mailto:mobopts-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1989177428=="
Sender: mobopts-bounces@irtf.org
Errors-To: mobopts-bounces@irtf.org

Hi Christian,

El jue, 06-10-2005 a las 16:24 +0200, Christian Vogt escribió:
> Hi Carlos.
> 
> > I have one question about Section 6.19. It says: "It is relatively
> > straightforward to optimize bidirectional tunneling for moving
> > networks [39] by using a single home agent and a single tunnel
> > between the mobile router and that home agent". RFC3963 does not
> > specify any kind of RO (the use of the bidirectional tunnel is no
> > optimal), so I think you mean "It is relatively straightforward to
> > support network mobility [39] by using a single home agent and a
> > single bidirectional tunnel between the mobile router and that home
> > agent". Did I miss/missunderstand something?
> 
> You are correct.  I changed it.
> 
> I also added references to RO solutions.
> 
> I am not so sure whether draft-irtf-mobopts-ro-enhancements-01.txt
> should get too deep into the problem space of mobile networks.  This is
> not its scope.  Given that the draft includes references to the RO
> problem statement as well as to proposed RO solution, interested readers
> may look up more detailed information in those documents.

	OK, completely agree.

	Kind Regards,

	Carlos J.

> 
> Thanks for the comments.
> 
> - Christian
> 
> --
> Christian Vogt, Institute of Telematics, University of Karlsruhe
> www.tm.uka.de/~chvogt/pubkey/
> 
> 
> 
> Carlos Jesús Bernardos Cano wrote:
> > Hi Christian,
> >
> > I have one question about Section 6.19. It says: "It is relatively
> > straightforward to optimize bidirectional tunneling for moving
> > networks [39] by using a single home agent and a single tunnel
> > between the mobile router and that home agent". RFC3963 does not
> > specify any kind of RO (the use of the bidirectional tunnel is no
> > optimal), so I think you mean "It is relatively straightforward to
> > support network mobility [39] by using a single home agent and a
> > single bidirectional tunnel between the mobile router and that home
> > agent". Did I miss/missunderstand something?
> >
> > I think that draft-bernardos-nemo-miron-00.txt could be referenced in
> >  your draft when you describe the RO for NEMO consisting in the MR
> > performing the MIPv6 signalling on behalf of the nodes of the NEMO.
> > The approach described in the draft exactly consists on that.
> >
> > IMHO, some text could also be added about the NEMO-specific RO
> > problem of nesting (mobile networks that attach to another mobile
> > network). Do you think is appropriate? I think that could be also
> > useful to add a reference to
> > draft-ietf-nemo-ro-problem-statement-00.txt. What do you think?
> >
> > Kind Regards,
> >
> > Carlos J.
> >
-- 
Carlos Jesús Bernardos Cano     http://www.netcoms.net
GPG FP: BFF1 7C7A 6AA7 BCE3 885A  4DF1 ED0C 5952 BF89 B974

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts