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

George Tsirtsis <tsirtsis@googlemail.com> Thu, 15 January 2009 13:37 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6075828C200; Thu, 15 Jan 2009 05:37:58 -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 2B08428C133 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 05:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 FHKBRpKZMpyX for <mext@core3.amsl.com>; Thu, 15 Jan 2009 05:37:55 -0800 (PST)
Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id 5B5573A690B for <mext@ietf.org>; Thu, 15 Jan 2009 05:37:55 -0800 (PST)
Received: by bwz14 with SMTP id 14so3379201bwz.13 for <mext@ietf.org>; Thu, 15 Jan 2009 05:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WJN4jJDCG0VjNrP5giwD6YMsFd4fcSR4i7cLHGIDzd8=; b=lg8org+q+B9UPL5HhKSSBHBht8Xou2QtrGwJLp5ikQbyVIcpyJuQPf6ggD6gq1bs06 TJLmUH+vvghrVcge8DrZ0lapPBXV06YR/KCJ2brr24IdSghCTEwCN9dE0MPPgYyKxYTx CJWvcD8HNlXYzOetQ8wxUF9JTNMLwS8W9cglc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hqrOy5/Lox9fuJDUjWgRGZ01V0KqeRHEROs2CMLs7vXhsDYrjwCGl2HMKv0E8X9lyu AoZedNmMEmKm+J9VRE0Sr2g8Gx+me7xrgldWg6p75KdtI+WXy4sJYwTzSvrNa33adPDr 7dBhMltCfehDLGkpYiIWfoWtprVgqb2Kiq6OE=
MIME-Version: 1.0
Received: by 10.223.111.211 with SMTP id t19mr1605480fap.64.1232026659471; Thu, 15 Jan 2009 05:37:39 -0800 (PST)
In-Reply-To: <C5958455.B154%hesham@elevatemobile.com>
References: <1696498986EFEC4D9153717DA325CB7202E5DEBA@vaebe104.NOE.Nokia.com> <C5958455.B154%hesham@elevatemobile.com>
Date: Thu, 15 Jan 2009 13:37:39 +0000
Message-ID: <d3886a520901150537y770919b1q2c9492b1efda9df7@mail.gmail.com>
From: George Tsirtsis <tsirtsis@googlemail.com>
To: Hesham Soliman <hesham@elevatemobile.com>
Cc: Pasi.Eronen@nokia.com, 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

I think what Pasi suggests makes sense and will make things easier for
whoever defines GRE support.

Not assigning a number for the TLV essentially means that the TLV
header for GRE is undefined and thus nothing needs to be said about
it. The whole thing can then be defined in a different spec as needed.

Regards
George

On Thu, Jan 15, 2009 at 1:24 PM, 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