IETF Logo Mail Archive

[Dime] Issue#32 status

"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Wed, 19 February 2014 15:34 UTC

Return-Path: <ulrich.wiehe@nsn.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0C71A032A for <dime@ietfa.amsl.com>; Wed, 19 Feb 2014 07:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hgzp1vN_mdF2 for <dime@ietfa.amsl.com>; Wed, 19 Feb 2014 07:34:05 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF0B1A032C for <dime@ietf.org>; Wed, 19 Feb 2014 07:34:04 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id s1JFY02s017379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dime@ietf.org>; Wed, 19 Feb 2014 16:34:00 +0100
Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id s1JFY06q024755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Wed, 19 Feb 2014 16:34:00 +0100
Received: from DEMUHTC009.nsn-intra.net (10.159.42.40) by DEMUHTC001.nsn-intra.net (10.159.42.32) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 19 Feb 2014 16:33:59 +0100
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.242]) by DEMUHTC009.nsn-intra.net ([10.159.42.40]) with mapi id 14.03.0123.003; Wed, 19 Feb 2014 16:33:59 +0100
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: Issue#32 status
Thread-Index: Ac8tiAGtvQe9mwQAS968RUS8ackr7w==
Date: Wed, 19 Feb 2014 15:33:58 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D9000668151B3D63@DEMUMBX014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.126]
Content-Type: multipart/alternative; boundary="_000_5BCBA1FC2B7F0B4C9D935572D9000668151B3D63DEMUMBX014nsnin_"
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2481
X-purgate-ID: 151667::1392824040-00003660-1BFEE95F/0-0/0-0
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/OlPzVwvhhFKPEoUfInWIVwvREyE
Subject: [Dime] Issue#32 status
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 15:34:07 -0000

#32: Sequence-Number Time-Stamp values within OC-OLR

I understand that we agreed the following principles:

Sequence-Number is of type Time, however the value need not correspond to the point in time of generation.

When generated, a new sequence number must be  greater than any sequence number previously generated by the same node (including over a reboot of that node)

When received, a sequence number is used to detect outdates/replays/freshness.

Sequence numbers of expired OLRs MUST NOT be remembered by reacting nodes.


I did not understand the requirement for globally uniqueness as introduced by Jouni.
Can Jouni please explain.

Ulrich

v2.23.0 | Report a Bug | By Email