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

Romain KUNTZ <rkuntz@us.toyota-itc.com> Mon, 27 June 2011 22:55 UTC

Return-Path: <rkuntz@us.toyota-itc.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 AA9CE21F8508 for <mext@ietfa.amsl.com>; Mon, 27 Jun 2011 15:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 c08s2f05lMMc for <mext@ietfa.amsl.com>; Mon, 27 Jun 2011 15:55:08 -0700 (PDT)
Received: from na3sys009aog116.obsmtp.com (na3sys009aog116.obsmtp.com [74.125.149.240]) by ietfa.amsl.com (Postfix) with SMTP id 9273621F8507 for <mext@ietf.org>; Mon, 27 Jun 2011 15:55:07 -0700 (PDT)
Received: from mail-pz0-f47.google.com ([209.85.210.47]) (using TLSv1) by na3sys009aob116.postini.com ([74.125.148.12]) with SMTP ID DSNKTgkKS9gbohTbPOULK3PEElicnWLjngPM@postini.com; Mon, 27 Jun 2011 15:55:08 PDT
Received: by mail-pz0-f47.google.com with SMTP id 36so3417021pzk.20 for <mext@ietf.org>; Mon, 27 Jun 2011 15:55:07 -0700 (PDT)
Received: by 10.68.20.68 with SMTP id l4mr3382355pbe.290.1309215307092; Mon, 27 Jun 2011 15:55:07 -0700 (PDT)
Received: from ben-lt3.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id u6sm4626619pbh.48.2011.06.27.15.55.05 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Jun 2011 15:55:06 -0700 (PDT)
From: Romain KUNTZ <rkuntz@us.toyota-itc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Jun 2011 15:55:04 -0700
Message-Id: <85A5D9F6-8186-4A41-BB1C-068FB781E28E@us.toyota-itc.com>
To: mext@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [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 22:55:09 -0000

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