Re: [MEXT] Comments about draft-gundavelli-mext-dsmip-ipv4-overlap

Sri Gundavelli <sgundave@cisco.com> Mon, 27 June 2011 23:06 UTC

Return-Path: <sgundave@cisco.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C679E1F0C45 for <mext@ietfa.amsl.com>; Mon, 27 Jun 2011 16:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.532
X-Spam-Level:
X-Spam-Status: No, score=-8.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ooX63gHg7YD for <mext@ietfa.amsl.com>; Mon, 27 Jun 2011 16:06:14 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2809221F8556 for <mext@ietf.org>; Mon, 27 Jun 2011 16:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=1215; q=dns/txt; s=iport; t=1309215974; x=1310425574; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=7ZSQboV+vvtJ3zhv9CpzVvwmxhbxWW/fQ+rrF6XBjNk=; b=d2cPzBuS93rRqkdMVcxEaqgTr3PXAhI9AnjpnGPm3WbeJBmVNuBMKdNe 56yU/IRFotpLI1WPI89qHwHbzALNqdcuJKh/24EGtcJvikt8DwUMoarSm ufnUU4tr9Vu14exa+wf3sWl/NaPWmgjysQG/VLMVaWZukJ6zzxNzm6XGP A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0HADoMCU6rRDoG/2dsb2JhbABSpzUCd4h0oiWeJoYwBIcsileEd4cyhBI
X-IronPort-AV: E=Sophos;i="4.65,434,1304294400"; d="scan'208";a="348460154"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 27 Jun 2011 23:05:57 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5RN5vE2007386; Mon, 27 Jun 2011 23:05:57 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Jun 2011 16:05:56 -0700
Received: from 128.107.112.115 ([128.107.112.115]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Mon, 27 Jun 2011 23:05:56 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Mon, 27 Jun 2011 16:05:55 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Romain KUNTZ <rkuntz@us.toyota-itc.com>, <mext@ietf.org>
Message-ID: <CA2E5AE3.1F0E1%sgundave@cisco.com>
Thread-Topic: [MEXT] Comments about draft-gundavelli-mext-dsmip-ipv4-overlap
Thread-Index: Acw1HsSQqjdhNvMLXkm6oBfrL/5HCQ==
In-Reply-To: <85A5D9F6-8186-4A41-BB1C-068FB781E28E@us.toyota-itc.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2011 23:05:56.0929 (UTC) FILETIME=[C5B6E310:01CC351E]
Subject: Re: [MEXT] Comments about draft-gundavelli-mext-dsmip-ipv4-overlap
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 27 Jun 2011 23:06:15 -0000

Hi Romain,

Thanks for the review.

I think we missed the prefix part, we can add some considerations around
that.

Will all fix the below issues.

Regards
Sri



On 6/27/11 3:55 PM, "Romain KUNTZ" <rkuntz@us.toyota-itc.com> wrote:

> Hi Sri,
> 
> I came through draft-gundavelli-mext-dsmip-ipv4-overlap, and was wondering
> whether it would make sense to take also prefix overlap into consideration.
> DSMIPv6 allows the assignment of a whole IPv4 prefix through the use of the P
> flag in the IPv4 Home Address option, which could make prefix overlap likely
> to occur. It may be worth mentioning in the document.
> 
> A few other minor comments:
> - section 3.2, there is an unrelated reference to [RFC3775]
> - section 4.1.1, I would add that the "context identifier field" comes from
> the GRE Key Header (and cite RFC5845)
> - section 4.1.2: s/"with the home address option"/"with the IPv4 home address
> option"
> - I would move section 5 to the beginning of section 4. That would makes
> section 4.1.2 more clear.
> 
> Regards,
> Romain
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext