Re: [Mipshop] draft-xia-fmip--multicast-00 comments

Thomas C Schmidt <schmidt@fhtw-berlin.de> Tue, 07 November 2006 23:23 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhaI7-0003L6-VB; Tue, 07 Nov 2006 18:23:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhaI6-00038k-Dn for mipshop@ietf.org; Tue, 07 Nov 2006 18:23:38 -0500
Received: from mail1.rz.fhtw-berlin.de ([141.45.5.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhaI4-0006nT-Sl for mipshop@ietf.org; Tue, 07 Nov 2006 18:23:38 -0500
Received: from dhcp68-194.ietf67.org ([130.129.68.194]) by mail1.rz.fhtw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.42 (FreeBSD)) id 1GhaI2-000GUC-PJ; Wed, 08 Nov 2006 00:23:36 +0100
Message-ID: <4551162B.4030702@fhtw-berlin.de>
Date: Wed, 08 Nov 2006 00:26:35 +0100
From: Thomas C Schmidt <schmidt@fhtw-berlin.de>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mipshop] draft-xia-fmip--multicast-00 comments
References: <20061107225901.15468.qmail@web60315.mail.yahoo.com>
In-Reply-To: <20061107225901.15468.qmail@web60315.mail.yahoo.com>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: schmidt@fhtw-berlin.de
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Errors-To: mipshop-bounces@ietf.org

Dear all,

there was also the suggestion of just adding multicast data forwarding 
to FMIPv6 ... this seems to be a reasonable compromise, as it also 
accounts for supporting multicast in access networks without mcast 
routing support.

We actually would like to complement this by proposing an equivalent 
support to HMIPv6. Based on our previous draft 
draft-schmidt-waehlisch-mhmipv6-04.txt we could submit a corresponding 
proposal.

Regards,

thomas

Behcet Sarikaya wrote:
> Dear all,
>   Some people suggested transferring QoS context and possibly other 
> state as well. As far as I know QoS context transfer issue had been 
> brought app. five years ago, no activitity ever since. One possible 
> reason is that QoS context transfer is better handled in Layer 2. In 
> fact all cellular systems handle this, with specific standards.
>   If there is desire to revive it, I suggest bringing it with a draft, 
> then we can discuss?
> 
>   Regarding the comment that the use of a context transfer protocol 
> would be better, I disagree,consider  the complexity of adding CxTP to 
> FMIPv6.
> 
>  
> Regards,
> 
> Behcet
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Mipshop mailing list
> Mipshop@ietf.org
> https://www1.ietf.org/mailman/listinfo/mipshop

_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop