[MEXT] A comment on draft-ietf-mext-binding-revocation-00

Sandesh <sksodhi@gmail.com> Mon, 04 August 2008 08:01 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 0EF6C3A68C6; Mon, 4 Aug 2008 01:01:21 -0700 (PDT)
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 2DC4B3A68C6 for <mext@core3.amsl.com>; Mon, 4 Aug 2008 01:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.727
X-Spam-Level:
X-Spam-Status: No, score=-1.727 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6]
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 feS7JE9XLico for <mext@core3.amsl.com>; Mon, 4 Aug 2008 01:01:19 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by core3.amsl.com (Postfix) with ESMTP id 5E13F3A6896 for <mext@ietf.org>; Mon, 4 Aug 2008 01:01:19 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1644363rvf.49 for <mext@ietf.org>; Mon, 04 Aug 2008 01:01:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=hB2VTeUxAMeGUwmWIFbDyM5+6flPA01zk005UBDt8AA=; b=nTRD9dZOn35djX4FTGEBx1euMaPRxs/uWZwYHiAouE4eXiI9fJlTWRRQxwNgSKbh3S /ddl1d+a9tVYWxl3ZLJ4Fdr1loIe0c1jKEBcubJ+2/tgWjO1h0HfeO5tAtuuxiH6DwHe bM9fKAYorBeZefsZ5j+shoS31IFch6ym3jM2w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=iyCbzRERuIMqi2TK753xmSO5BJXLpP+r35kQPAH4aGcF2zMeLyLf1WdpB5m2QRS3CI F6pbFNpp71GPA83Gwe1DS3ExStgnlk+78Tx91Rp6swa1Pr3yB8H/G8cMud+Pt165fkdY dJaVovMs4b9zgMrV/VR/o8hmwBdYRaB8RLwYE=
Received: by 10.141.129.14 with SMTP id g14mr7399878rvn.50.1217836877248; Mon, 04 Aug 2008 01:01:17 -0700 (PDT)
Received: by 10.141.141.10 with HTTP; Mon, 4 Aug 2008 01:01:17 -0700 (PDT)
Message-ID: <e75f55e20808040101y10555164i187b73049d6ce74b@mail.gmail.com>
Date: Mon, 04 Aug 2008 13:31:17 +0530
From: Sandesh <sksodhi@gmail.com>
To: mext@ietf.org
MIME-Version: 1.0
Subject: [MEXT] A comment on draft-ietf-mext-binding-revocation-00
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="===============0880665298=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Hi All,

IMO following case is possible with PMIPv6 protocol
defined in http://tools.ietf.org/html/draft-ietf-mext-binding-revocation-00
and http://tools.ietf.org/html/draft-ietf-netlmm-proxymip6-18

lt = lifetime
eth0 is the interface og MAG to the LAN in
which MN1 is present. MAG has another
interface eth1 through which it is connected to LMA.

MN1 ---- eth0 MAG eth1 -------LMA


            MAG                LMA
             |                  |
             |                  |
             |                  |
 eth0 down   |                  |
             |\ BRI(G)          |
 eth0 up     | \                |
(MN1 attaches)|  \     PBU(lt!=0)|
             |----------------->|
             |   \      +-------|
             |    \    /        |
             |     +----------->|
             |       /  +-------|
             | BRA  /  /        |
             |<----/--+         |
             |    /             |
             |   /              |
             |<-+               |
             | PBA              |
(BUL entry for MN1)           (no BCE MN1)

Reason -
1. As per these drafts BRI and PBU has their own
  (independent) sequence numbers.
2. BRI/BRA does not have timestamp option.
3. These drafts do not say that PBU cannot be sent
  if MAG has already sent BRI(G) to LMA.
4. In IP network missequencing of packets is possible.

Thanks and Regards,
Sandesh
_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext