IETF Logo Mail Archive

Re: [MEXT] GRE support in DSMIPv6 - AD review

Hesham Soliman <hesham@elevatemobile.com> Fri, 16 January 2009 23:57 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: monami6-archive@megatron.ietf.org
Delivered-To: ietfarch-monami6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42C3C3A689D; Fri, 16 Jan 2009 15:57:07 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C0E63A689D for <mext@core3.amsl.com>; Fri, 16 Jan 2009 15:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level:
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6v1TkZFH-Ej1 for <mext@core3.amsl.com>; Fri, 16 Jan 2009 15:57:05 -0800 (PST)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 936F03A6768 for <mext@ietf.org>; Fri, 16 Jan 2009 15:57:04 -0800 (PST)
Received: from [124.190.106.160] (helo=[192.168.0.187]) by smtp-2.servers.netregistry.net protocol: esmtpa (Exim 4.63 #1 (Debian)) id 1LNyYI-0007AZ-Fs; Sat, 17 Jan 2009 10:56:38 +1100
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Sat, 17 Jan 2009 10:56:30 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: Behcet Sarikaya <sarikaya@ieee.org>, Vijay Devarapalli <vijay@wichorus.com>, Pasi.Eronen@nokia.com, mext@ietf.org
Message-ID: <C59769DE.B1DA%hesham@elevatemobile.com>
Thread-Topic: [MEXT] GRE support in DSMIPv6 - AD review
Thread-Index: Acl4Ng0X3joRG3lYgEOmRZ1GAGCiYg==
In-Reply-To: <703169.3551.qm@web111408.mail.gq1.yahoo.com>
Mime-version: 1.0
Cc: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [MEXT] GRE support in DSMIPv6 - AD review
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org


> At that time, there were folks arguing for using GRE
>> encapsulation with MIPv6 also.
> [behcet] I couldn't understand why MN would need to support GRE. Can someone
> explain the use case?

=> It was done for NETLMM. Technically and practically speaking it will
never be used by the MN. And there is no reason for doing so. Whenever GRE
is used it's used within the network not from the host.

Hesham

>  
> Thanks,
>  
> Behcet
> 
> 
>> Hi Pasi, Hesham,
>> 
>> The TLV header was specified in the DS-MIPv6 document after rather a
>> long and acrimonious debate on the former MIP6 mailing list. There were
>> atleast two consensus calls that were run at that time.
> 
> => I don't realy want to get into that, we all know there was no concensus
> and we had to teleconference to come up with the existing method
> 
> Anytime you have
>> a UDP header with IPv4/IPv6/GRE header following it, you need the TLV
>> header. 
> 
> 


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email