IETF Logo Mail Archive

[netlmm] DNAv6/SEND and timestamp synchronization problems

Julien Laganier <julien.IETF@laposte.net> Tue, 11 September 2007 14:20 UTC

Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IV6b5-0002eI-45; Tue, 11 Sep 2007 10:20:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IV6b3-0002e3-Ab for netlmm@ietf.org; Tue, 11 Sep 2007 10:20:09 -0400
Received: from hu-out-0506.google.com ([72.14.214.237]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IV6b2-000484-3N for netlmm@ietf.org; Tue, 11 Sep 2007 10:20:09 -0400
Received: by hu-out-0506.google.com with SMTP id 31so592265huc for <netlmm@ietf.org>; Tue, 11 Sep 2007 07:20:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; bh=4D7Nw6pgfV0sX1qi7k9IB/er4Ohv7eeNuRD+k9xqg/U=; b=SJAFN1iVW3jm7wTpqGwNKIOzcuYKlbiOk7/mcgQd2JctnLarprrQFj6frO3mNs/+IpKbuRAdhusFUeEhl3m8CT7k0ZXgVQ279ZdyjaAThfc7/qE4/1S/ilvUnT8o2SbeoAvWBsremG1ZhF1kTaum2F+D3yHl3QU2G9OYrhUHhY4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=qfaKQmm0b4ZBEKrKZocxEXnspeQgPTl7zIUjdzItBfd7VfnkldAlU9u3XHMi2WwkGAA5xlx+RC6fte6Yq69PjqlFm6hYT7iPvF8WwfQY7be1sPIxF0Qvha2wN4VjmZGSoizcplxgqB5PUo8lM/i7BjnWOUVTyAncL1H8MlFguXY=
Received: by 10.67.28.4 with SMTP id f4mr737725ugj.1189520406998; Tue, 11 Sep 2007 07:20:06 -0700 (PDT)
Received: from klee.local ( [212.119.9.178]) by mx.google.com with ESMTPS id o30sm1140850ugd.2007.09.11.07.20.04 (version=SSLv3 cipher=OTHER); Tue, 11 Sep 2007 07:20:06 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: netlmm@ietf.org
Date: Tue, 11 Sep 2007 16:20:02 +0200
User-Agent: KMail/1.9.6
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200709111620.02475.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [netlmm] DNAv6/SEND and timestamp synchronization problems
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

Folks,

It has been discussed on the mailing list that synchronizing time across 
different MAGs to allow reordering of pBUs might be a problem. While 
thinking about the issue I got the idea to leverage on SEND to solve 
that issue.

When the MN uses DNAv6 for movement detection along with SEND to secure 
ND signaling (which includes DNAv6), all ND messages sent by the MN 
will contain a timestamp representing the local time on the MN. Thus, 
all MAGs to which a given MN attached to have access to a single per-MN 
timestamp source.

Using pBU timestamps from that source will avoid issues with time 
synchronization of different MAGs since timestamps are synchronized at 
the source.

Thoughts?

--julien

_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www1.ietf.org/mailman/listinfo/netlmm

v2.23.0 | Report a Bug | By Email