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

Sri Gundavelli <sgundave@cisco.com> Thu, 15 January 2009 16:56 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 CC38728C250; Thu, 15 Jan 2009 08:56:54 -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 0900228C262 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 08:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level:
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 zb1pZu+n3sK5 for <mext@core3.amsl.com>; Thu, 15 Jan 2009 08:56:52 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 17E8128C250 for <mext@ietf.org>; Thu, 15 Jan 2009 08:56:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,270,1231113600"; d="scan'208";a="230534512"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 15 Jan 2009 16:56:37 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0FGubFC014344; Thu, 15 Jan 2009 08:56:37 -0800
Received: from irp-view13.cisco.com (irp-view13.cisco.com [171.70.120.60]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0FGubrA027620; Thu, 15 Jan 2009 16:56:37 GMT
Date: Thu, 15 Jan 2009 08:56:37 -0800
From: Sri Gundavelli <sgundave@cisco.com>
To: Pasi.Eronen@nokia.com
In-Reply-To: <1696498986EFEC4D9153717DA325CB7202E5DEBA@vaebe104.NOE.Nokia.com>
Message-ID: <Pine.GSO.4.63.0901150838490.10109@irp-view13.cisco.com>
References: <C594245E.B121%hesham@elevatemobile.com> <1696498986EFEC4D9153717DA325CB7202E5DEBA@vaebe104.NOE.Nokia.com>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2603; t=1232038597; x=1232902597; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20Sri=20Gundavelli=20<sgundave@cisco.com> |Subject:=20Re=3A=20[MEXT]=20GRE=20support=20in=20DSMIPv6=2 0-=20AD=20review |Sender:=20; bh=qcFogZ3x69SqR/Chhu9+Gv06qwxI7zzWQW+iy6A/3yg=; b=re4oHtmfDwUBYFh0M/MvdAFp+rmdDZu6E5r+TJ57NIoroV89TnZG0CeTsf vw/gvtM9WTbuUHWO079QVj7OCFXBVJ+MYUZeO8MkCWtTUSBpIpE2uIBhpxUA p+VXzllpc1zbb0ZF8tm3PRSce3wYd7Acxh/x3drDfr4qAWrRdLTFg=;
Authentication-Results: sj-dkim-1; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Hi Pasi,

The specified GRE type value in the TLV header identifies the
payload that follows. Wondering, what more needs to be specified.
As the GRE format is specified in the respective specification,
here the purpose of TLV is only payload classification, with a
reference to that spec. Will a clarification help ?

The GRE key exchange draft in NETLMM is about defining an option
for GRE key exchange. It does not focus on the transport. Its only
deals with the key negotiation. The IPv4 support document in NETLMM
also does not focus on GRE transport, it falls back to the DSMIP spec
with normative reference.

So, if this is about a simple clarification, probably it can be fixed
here ? Also, there were long discussion threads on this topic a year
back.


Regards
Sri


On Thu, 15 Jan 2009, Pasi.Eronen@nokia.com wrote:

> 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