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

Hesham Soliman <hesham@elevatemobile.com> Wed, 21 January 2009 04:04 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 4C49B3A6A33; Tue, 20 Jan 2009 20:04:39 -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 2436C3A6A33 for <mext@core3.amsl.com>; Tue, 20 Jan 2009 20:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level:
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599]
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 Qp5cXW5WYVls for <mext@core3.amsl.com>; Tue, 20 Jan 2009 20:04:37 -0800 (PST)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 319E53A6A1C for <mext@ietf.org>; Tue, 20 Jan 2009 20:04:36 -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 1LPUK0-0002fS-A6; Wed, 21 Jan 2009 15:04:08 +1100
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Wed, 21 Jan 2009 15:04:01 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: Sri Gundavelli <sgundave@cisco.com>
Message-ID: <C59CE9E1.B300%hesham@elevatemobile.com>
Thread-Topic: [MEXT] GRE support in DSMIPv6 - AD review
Thread-Index: Acl7fUqhKt2xTxPoYUe0GEBr6YBGbw==
In-Reply-To: <Pine.GSO.4.63.0901201859381.8008@irp-view13.cisco.com>
Mime-version: 1.0
Cc: mext@ietf.org
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org On 21/01/09 2:05 PM, "Sri Gundavelli" <sgundave@cisco.com> wrote:

> 
> 
> On Tue, 20 Jan 2009, Hesham Soliman wrote:
> 
>>> 
>>> The issue would be that this spec needs to understand the payload
>>> qualifier, else we cant add themm later.
>> 
>> => It's not true though. You can add the exact same thing that we have in
>> the draft now but specify it in a more complete manner and it will be
>> backward compatible and interoperable. The negotiation bit in the BU would
>> have to be included in the new draft of course.
>> 
> 
> Leaving the TLV header alone in this draft will provide the
> necessary frame work.

=> You're not answering the comment I mentioned above Sri.

  Else, defining outside and mapping the
> pre-allocated v4/v6 types, will appear more like a hack. Since,
> Pasi's comment was more specific to GRE, not sure if it was
> about the TLV alone,

=> Let's not talk about hacks....Pasi strongly suggested that we remove the
TLV completely and do it for PMIPv6. I think there is enough people who
already agree with that and I don't see a reason for us to debate this
endlessly. This draft is long overdue. So, it's best to include this in a
specific PMIP draft.


as there is much text required for TLV
> nego, or for describing the TLV format, thats already there in
> the draft.

=> Right, you can easily copy and paste it.

Hesham

> 
> Sri
> 
> 


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