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

Hesham Soliman <hesham@elevatemobile.com> Thu, 15 January 2009 14:07 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 B2F3D3A6925; Thu, 15 Jan 2009 06:07:06 -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 6C3D83A6925 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 06:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level:
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 6gLQBOZhEoQj for <mext@core3.amsl.com>; Thu, 15 Jan 2009 06:07:04 -0800 (PST)
Received: from smtp-2.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 4FB193A6803 for <mext@ietf.org>; Thu, 15 Jan 2009 06:06:59 -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 1LNSrl-00010a-09; Fri, 16 Jan 2009 01:06:37 +1100
User-Agent: Microsoft-Entourage/12.15.0.081119
Date: Fri, 16 Jan 2009 01:06:30 +1100
From: Hesham Soliman <hesham@elevatemobile.com>
To: George Tsirtsis <tsirtsis@googlemail.com>
Message-ID: <C5958E16.B15B%hesham@elevatemobile.com>
Thread-Topic: [MEXT] GRE support in DSMIPv6 - AD review
Thread-Index: Acl3GnaicWevlZ8G0kuvB+gkn/eC6w==
In-Reply-To: <d3886a520901150602w245de957o99674f2f23b6cee7@mail.gmail.com>
Mime-version: 1.0
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

Pasi mentioned in the first paragraph that he " would strongly suggest
moving the whole TLV header text to the separate GRE document."

This is different from keeping the TLV header and removing the assignment of
GRE values. Two very different approaches. It's not clear to me which one
you are asking for.

Hesham


On 16/01/09 1:02 AM, "George Tsirtsis" <tsirtsis@googlemail.com> wrote:

> How are they different? Maybe I am missing something. The only type
> value defined currently on the TLV is for GRE. If you remove the GRE
> value, what is the TLV for?
> 
> George
> 
> On Thu, Jan 15, 2009 at 1:51 PM, Hesham Soliman
> <hesham@elevatemobile.com> wrote:
>> 
>> 
>> 
>> 
>>> I think what Pasi suggests makes sense and will make things easier for
>>> whoever defines GRE support.
>> 
>> => So are you agreeing with removing the TLV completely or with simply
>> removing the assignment of the GRE? They're two different things.
>> 
>> Hesham
>> 
>>> 
>>> 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