Re: [Mip4] Does MIP support RegReq authentication without having to do timekeeping?

Ahmad Muhanna <> Thu, 14 March 2013 18:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0E81121F8DA8 for <>; Thu, 14 Mar 2013 11:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id s+JuM4-MDP3Z for <>; Thu, 14 Mar 2013 11:44:38 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id B5E7121F8D17 for <>; Thu, 14 Mar 2013 11:44:37 -0700 (PDT)
Received: from ([]) (using TLSv1) by ([]) with SMTP ID DSNKUUIZtL10+/; Thu, 14 Mar 2013 11:40:53 PDT
Received: from ([fe80::a1f1:7708:4a71:9fee]) by ([fe80::a1f1:7708:4a71:9fee%11]) with mapi id 14.01.0438.000; Thu, 14 Mar 2013 13:44:35 -0500
From: Ahmad Muhanna <>
To: Alexandru Petrescu <>, Mobile IPv4 Mailing List <>
Thread-Topic: [Mip4] Does MIP support RegReq authentication without having to do timekeeping?
Thread-Index: AQHOINhsTBPzIQFtNkS6cO9qzV4P1pilhFTw
Date: Thu, 14 Mar 2013 18:44:34 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Mip4] Does MIP support RegReq authentication without having to do timekeeping?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobility for IPv4 <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Mar 2013 18:44:39 -0000

Hi Alex,

As far as I recall, RFC2002 and all updates afterwards, allow the use of nonce.
Basically like a challenge.

>From implementation prospective; I would allow both to coexist as follows:
1. Both HA and MR uses timestamp as normal and no issue there.
2. When the MR fails or start NOT to have a valid time, the MR should have remembered the last RRP ID which is based on timestamp and use that for Re-Registration.
3. At the HA, it should check timestamp first, if it passes then timestamp continues to work; if it fails, the HA should check the Re-Registration ID against the last ID that was sent in the last RRP, if it is the same, the HA should allow the RRP to go through.

I Hope this helps!


Best Regards,

-----Original Message-----
From: [] On Behalf Of Alexandru Petrescu
Sent: Thursday, March 14, 2013 12:21 PM
To: Mobile IPv4 Mailing List
Subject: [Mip4] Does MIP support RegReq authentication without having to do timekeeping?

MIP4 participants,

I would like to learn whether Mobile IPv4 spec supports an authentication scheme for RegReq/RegRep which does not rely on timekeeping.

Let me explain why.

We use a Mobile Router in a moving network that gets connected to the Home Agent.  The Mobile Router's power supply may be turned off (its battery dies out after an extended period of inactivity, like in a vehicle).  At that point the MR looses its time.

When it finally wakes up, it has to perform a Registration Req/Rep with the HA, without assuming that its time is correct.  Or, the MIP4 regreq/regrep HA implementation that we use seems to rely on having the right time, otherwise the registration fails.

Under these conditions, is it possible to use an auth mechanism which does not rely on timekeeping?


Mip4 mailing list:
    Web interface:
     Charter page:
Supplemental site: