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

Henrik Levkowetz <henrik@levkowetz.com> Thu, 15 January 2009 20:12 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 8A14A3A68C7; Thu, 15 Jan 2009 12:12:48 -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 CD7053A68C7 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 12:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level:
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 mUGCKf0HkfPo for <mext@core3.amsl.com>; Thu, 15 Jan 2009 12:12:45 -0800 (PST)
Received: from av12-1-sn2.hy.skanova.net (av12-1-sn2.hy.skanova.net [81.228.8.185]) by core3.amsl.com (Postfix) with ESMTP id 83BF13A68B6 for <mext@ietf.org>; Thu, 15 Jan 2009 12:12:45 -0800 (PST)
Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502) id 8AA7D3801F; Thu, 15 Jan 2009 21:12:29 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP id 7038337FF5; Thu, 15 Jan 2009 21:12:29 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 4C6EA37E49; Thu, 15 Jan 2009 21:12:28 +0100 (CET)
Received: from localhost ([127.0.0.1]:42656 helo=chardonnay.local) by shiraz.levkowetz.com with esmtp (Exim 4.69) (envelope-from <henrik@levkowetz.com>) id 1LNYZn-0008L7-J6; Thu, 15 Jan 2009 21:12:27 +0100
Message-ID: <496F98AA.7030601@levkowetz.com>
Date: Thu, 15 Jan 2009 21:12:26 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay@wichorus.com>
References: <C594245E.B121%hesham@elevatemobile.com> <1696498986EFEC4D9153717DA325CB7202E5DEBA@vaebe104.NOE.Nokia.com> <DE33046582DF324092F2A982824D6B030525D193@mse15be2.mse15.exchange.ms>
In-Reply-To: <DE33046582DF324092F2A982824D6B030525D193@mse15be2.mse15.exchange.ms>
X-Enigmail-Version: 0.95.7
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vijay@wichorus.com, Pasi.Eronen@nokia.com, hesham@elevatemobile.com, mext@ietf.org, jari.arkko@piuha.net, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false
Cc: Jari Arkko <jari.arkko@piuha.net>, mext@ietf.org, Pasi.Eronen@nokia.com
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

Hi,

On 2009-01-15 19:32 Vijay Devarapalli said the following:
> 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. Anytime you have
> a UDP header with IPv4/IPv6/GRE header following it, you need the TLV
> header. At that time, there were folks arguing for using GRE
> encapsulation with MIPv6 also. PMIPv6 IPv4 support was not the only
> scenario for the TLV header. We are overturning that consensus now.
> Maybe folks who were arguing for the TLV header with DS-MIPv6, are
> either busy/not looked at this thread yet/or not on the MEXT mailing
> list/etc.. :)
> 
> Moving the TLV header into a separate document at this point would
> impact draft-ietf-netlmm-pmip6-ipv4-support. I don't think the TLV
> header document can be standardized fast enough for
> draft-ietf-netlmm-pmip6-ipv4-support to advance. One option would be to
> move the TLV header and the text that describes how to negotiate it, to
> either draft-ietf-netlmm-pmip6-ipv4-support or
> draft-ietf-netlmm-grekey-option. 
> 
> My suggestion would be to leave the TLV header in the DS-MIPv6 document.
> Have some text that says the following. If UDP encapsulation is used
> with DS-MIPv6 port, there could be IPv4, IPv6, GRE or some other header
> that might follow the UDP header. If there is anything other than the
> IPv4 or IPv6 header, the TLV header would be required. The use of GRE or
> some other protocol after the TLV header is not specified and is out of
> scope in the DS-MIPv6 document.

That would work for me.  I'd very much like to see the TLV header itself
kept; the reason is that if something else (GRE or whatever) than an IP
header follows the UDP header, there isn't a clear and obvious way of
dynamically distinguishing *what* that something else is, unless the
TLV header is there.  Ripping it out completely would leave the
specification less ready for extension than otherwise, which would be
unfortunate if we already know that there are needs for extension.

One thing in the -05 and -06 drafts which surprised me when looking at
them now was the value assignments for the TLV type field -- I'd expected
the use of already-defined protocol numbers here, in a similar manner to
what's in Section 3.3 of RFC 3519, rather than a new registry.  But there
are maybe things I've forgotten from our earlier discussion which makes
a new type number space necessary.


	Henrik



> 
> Vijay 
> 
> 
>> -----Original Message-----
>> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On 
>> Behalf Of Pasi.Eronen@nokia.com
>> Sent: Thursday, January 15, 2009 3:54 AM
>> To: hesham@elevatemobile.com; mext@ietf.org
>> Subject: Re: [MEXT] GRE support in DSMIPv6 - AD review
>>
>> Hesham,
>>
>> I would strongly suggest moving the whole TLV header text to the
>> separate GRE document.
>>
>> 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.
>>
>> 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
> 

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