[MEXT] Clarifications required on BRI sequence number [draft-muhanna-mext-binding-revocation-02]

Kowsalya Subramanian <kowsalya@cisco.com> Fri, 30 January 2009 04:21 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id DA6773A6928; Thu, 29 Jan 2009 20:21:54 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id BBE773A6851 for <mext@core3.amsl.com>; Thu, 29 Jan 2009 20:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id BjQwOZ3MjiUQ for <mext@core3.amsl.com>; Thu, 29 Jan 2009 20:21:52 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com []) by core3.amsl.com (Postfix) with ESMTP id BA4173A6928 for <mext@ietf.org>; Thu, 29 Jan 2009 20:21:52 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.37,348,1231113600"; d="scan'208,217"; a="135506764"
Received: from sj-dkim-4.cisco.com ([]) by sj-iport-1.cisco.com with ESMTP; 30 Jan 2009 04:21:34 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com []) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n0U4LY1P020327 for <mext@ietf.org>; Thu, 29 Jan 2009 20:21:34 -0800
Received: from sj-webmail-3.cisco.com (sj-webmail-3.cisco.com []) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n0U4LYXK015345 for <mext@ietf.org>; Fri, 30 Jan 2009 04:21:34 GMT
Received: from sj-webmail-3.cisco.com (localhost.localdomain []) by sj-webmail-3.cisco.com (8.13.1/8.13.1) with ESMTP id n0U4LY0d009170 for <mext@ietf.org>; Thu, 29 Jan 2009 20:21:34 -0800
Received: from sj-webmail-3 (root@localhost) by sj-webmail-3.cisco.com (8.13.1/8.13.1/Submit) with ESMTP id n0U4LYak009169 for <mext@ietf.org>; Thu, 29 Jan 2009 20:21:34 -0800
Received: from kowsalyawxp ( []) by sj-webmail-3 (Scalix SMTP Relay via ESMTP; Thu, 29 Jan 2009 20:21:33 -0800 (PST)
Date: Fri, 30 Jan 2009 09:51:31 +0530
From: Kowsalya Subramanian <kowsalya@cisco.com>
To: <mext@ietf.org>
Message-ID: <006801c98292$3ba47700$3a8b4d0a@cisco.com>
x-scalix-Hops: 1
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcmCkjqnQIi09wzwReueGggZwiVXxw==
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3469; t=1233289294; x=1234153294; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kowsalya@cisco.com; z=From:=20Kowsalya=20Subramanian=20<kowsalya@cisco.com> |Subject:=20Clarifications=20required=20on=20BRI=20sequence =20number=20[draft-muhanna-mext-binding-revocation-02] |Sender:=20; bh=D4dB6mOujVbLaXuBadVNBdHY0ZmJ/ivASNXL5mdXe60=; b=KsIgupnUwHnvUa55A9ZRGddKbl+fi+3v7QcOg66d3PaIlrXdrEvwwx9mhP Rq+RYDOppr0vUmopO1XdFEOE6jFNFDvF8xDL7AaHWZRMaXzVxIjNqsCHiDhx XWSd32tYa3;
Authentication-Results: sj-dkim-4; header.From=kowsalya@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Subject: [MEXT] Clarifications required on BRI sequence number [draft-muhanna-mext-binding-revocation-02]
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: multipart/mixed; boundary="===============1297549792=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

In the draft, there is text mentioning that the initiator of the BRI message
MUST choose a monotonically increasing sequence number. 
Lets consider a case where the BCE has 3 HNPs bound to it. If the LMA sends
a BRI with seq number 5 for {MN-ID, HNP1} and then wants to send a BRI for
{MN-ID, HNP2}. Should it wait till it gets a BRA for the previous BRI that
it sent? If LMA need not wait for the BRA, then it is possible that MAG
receives BRI 5, 6 out of order. In which case, what should the MAG do,
should it ignore BRI 5 as it has already got BRI 6.
In other words, is the sequence number in BRI indicates some form of
versioning for the deletion or is it just to match only BRA and identify BRI
re-transmissions. If it is the latter, why should it be monotonically
increasing, it can just be unique.
Am I missing something here?
MEXT mailing list