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

Basavaraj Patil <basavaraj.patil@nokia.com> Thu, 15 January 2009 17:13 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 4DA7428C272; Thu, 15 Jan 2009 09:13:59 -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 94CF728C273 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 09:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.483
X-Spam-Level:
X-Spam-Status: No, score=-6.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bRkwaRCrRmGk for <mext@core3.amsl.com>; Thu, 15 Jan 2009 09:13:57 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 7342D28C26A for <mext@ietf.org>; Thu, 15 Jan 2009 09:13:57 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0FHDA5i017969; Thu, 15 Jan 2009 19:13:34 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Jan 2009 19:13:26 +0200
Received: from vaebe112.NOE.Nokia.com ([10.160.244.81]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Jan 2009 19:13:26 +0200
Received: from 172.19.60.146 ([172.19.60.146]) by vaebe112.NOE.Nokia.com ([10.160.244.81]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Jan 2009 17:13:25 +0000
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Thu, 15 Jan 2009 11:13:36 -0600
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Hesham Soliman <hesham@elevatemobile.com>, Pasi Eronen <pasi.eronen@nokia.com>, mext@ietf.org
Message-ID: <C594CAE0.20C86%basavaraj.patil@nokia.com>
Thread-Topic: [MEXT] GRE support in DSMIPv6 - AD review
Thread-Index: Acl2Qty8AAnKSyLlR0eCYUg0kSOoIQAxLqsAAANDudYAB/zjfg==
In-Reply-To: <C5958455.B154%hesham@elevatemobile.com>
Mime-version: 1.0
X-OriginalArrivalTime: 15 Jan 2009 17:13:26.0026 (UTC) FILETIME=[93E876A0:01C97734]
X-Nokia-AV: Clean
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

I agree with the recommendation to moving the TLV header to a separate
document (if somene feels there is a need for it at all).

This spec is unneccesarily encumbered with the TLV header details and is
better off without it.

-Raj


On 1/15/09 7:24 AM, "ext Hesham Soliman" <hesham@elevatemobile.com> wrote:

> 
> 
>> I would strongly suggest moving the whole TLV header text to the
>> separate GRE document.
> 
> => Personally, as everyone on the list knows, I was always against including
> this in the draft, I think it's a really bad idea, but obviously it's not my
> decision. So let's see what people say. I do agree with this suggestion.
> 
>> 
>> In particular, if you assign a number for GRE in this document,
>> you either need to describe how it works here, or have a normative
>> reference to the NETLMM spec.
> 
> => My suggestion below was not to assign any numbers in the draft. It was
> simply to have the TLV header unassigned and let someone else request the
> assignment and describe how it's used. My ideal preference is the one above
> (remove it completely) but the suggestion below was a compromise to speed
> things up. 
> 
> Hesham
> 
>> 
>> Best regards,
>> Pasi
>> 
>>> -----Original Message-----
>>> From: ext Hesham Soliman [mailto:hesham@elevatemobile.com]
>>> Sent: 14 January, 2009 14:23
>>> To: mext@ietf.org
>>> Cc: Eronen Pasi (Nokia-NRC/Helsinki)
>>> Subject: GRE support in DSMIPv6 - AD review
>>> 
>>> Folks, 
>>> 
>>> Part of Pasi's review for DSMIPv6 was a comment on the lack of
>>> specification for GRE support in the spec. He said it was vastly
>>> under-specified, no details on the tunnelling, setting of different
>>> parts of the GRE header ...etc.
>>> 
>>> I suggested that we don't explicitly mention GRE in the spec but we
>>> keep the TLV tunnelling format and reserve the numbers for NETLMM to
>>> specify exactly how it will be used in a separate document. I think
>>> you would agree that this is largely driven by NETLMM needs and we
>>> shouldn't specify the details in MEXT. Pasi was ok with that.
>>> 
>>> Please express your opinion on this soon because Pasi's comments are
>>> the last comments for the draft and I want to handle them by Monday
>>> at the latest.
>>> 
>>> Please avoid discussing the merits of GRE....etc, the question is:
>>> 
>>> Are there any objections to removing explicit references to GRE
>>> while reserving the numbers in the TLV header for it to be specified
>>> clearly in NETLMM?
>>> 
>>> Thanks,
>>> 
>>> Hesham
> 
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext

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