[MEXT] Issue #7 - 3775bis

"Vijay Devarapalli" <vijay@wichorus.com> Thu, 05 March 2009 00:00 UTC

Return-Path: <vijay@wichorus.com>
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 6C4263A6A40 for <mext@core3.amsl.com>; Wed, 4 Mar 2009 16:00:19 -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 TxfItIbhR3lU for <mext@core3.amsl.com>; Wed, 4 Mar 2009 16:00:18 -0800 (PST)
Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 935303A6971 for <mext@ietf.org>; Wed, 4 Mar 2009 16:00:18 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 04 Mar 2009 19:00:44 -0500
Message-ID: <DE33046582DF324092F2A982824D6B03059D9FA5@mse15be2.mse15.exchange.ms>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Issue #7 - 3775bis
Thread-Index: AcmdJW4rhO/nRGXER/WttK/Pq2l6NA==
From: Vijay Devarapalli <vijay@wichorus.com>
To: mext <mext@ietf.org>, "Charles E. Perkins" <charliep@wichorus.com>
Subject: [MEXT] Issue #7 - 3775bis
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/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: Thu, 05 Mar 2009 00:00:19 -0000

On issue #7 (http://tools.ietf.org/wg/mext/trac/ticket/7),
draft-ietf-mip6-nemo-v4traversal has already been updated to say 

   When the home agent receives the encapsulated binding update, it
   compares the IPv4 address of the source address field in the IPv4
   header with the IPv4 address included in the IPv4 care-of address
   option.  If the two addresses match, no NAT device was in the path.

So this fixes part of the issue.

Regarding the text in section 9.5.1 in RFC 3775, based on the earlier
discussions, we should replace the following

   o  If the Lifetime specified in the Binding Update is zero or the
      specified care-of address matches the home address for the
      binding, then this is a request to delete the cached binding for
      the home address. 

with

   o  If the Lifetime specified in the Binding Update is zero, then 
      this is a request to delete the cached binding for the home 
      address. 

Vijay