Re: 'monotonic increasing'

Elwyn Davies <elwynd@dial.pipex.com> Fri, 17 February 2006 19:17 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FAB6K-0005R7-1n; Fri, 17 Feb 2006 14:17:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FAB6I-0005Qv-BU for ietf@megatron.ietf.org; Fri, 17 Feb 2006 14:17:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23238 for <ietf@ietf.org>; Fri, 17 Feb 2006 14:15:18 -0500 (EST)
Received: from a.painless.aaisp.net.uk ([81.187.81.51] helo=smtp.aaisp.net.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FABKj-0002kl-6v for ietf@ietf.org; Fri, 17 Feb 2006 14:32:01 -0500
Received: from 247.254.187.81.in-addr.arpa ([81.187.254.247] helo=[127.0.0.1]) by smtp.aaisp.net.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1FAB6C-00058W-UQ; Fri, 17 Feb 2006 19:17:01 +0000
Message-ID: <43F621B7.3090207@dial.pipex.com>
Date: Fri, 17 Feb 2006 19:19:19 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Tom.Petch" <sisyphus@dial.pipex.com>
References: <200601301716.JAA16888@gra.isi.edu> <002501c628af$62188600$0601a8c0@pc6> <014601c633dd$82948bc0$0601a8c0@pc6>
In-Reply-To: <014601c633dd$82948bc0$0601a8c0@pc6>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
Subject: Re: 'monotonic increasing'
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Hi.

Tom.Petch wrote:
> The phrase 'monotonic increasing' seems to be a Humpty-Dumpty one, used with a
> different sense within RFC to that which I see defined elsewhere; and this
> could lead to a reduction in security.
>
> Elsewhere - dictionaries, encyclopaedia, text books -  I see it
> defined so that when applied to a sequence of numbers, then each number is not
> less than its predecessor, so that
> 1 1 1 1 1 1 1 1 1 1
> 1 1 2 3 5 8 13
> 1 2.71828 3.14159 4.18 42
> are all monotonic increasing sequences whereas
> 1 2 3 4 5 6 7 9 8 10
> is not.
>   
On the definition of monotonic increasing: I just checked my memory with 
my copy of Apostol (Mathematical Analysis, vintage 1968 or so) and 
monotonic increasing implies element (n+1) greater than or equal to 
element n for all n.  'Strictly monotonic increasing' implies greater 
than.  On line 
http://www-history.mcs.st-and.ac.uk/~john/analysis/Lectures/L8.html 
confirms this.
> Within RFC, mostly those related to security or network management, the context
> of its use implies, in addition, one or more of
> a) each number in the sequence is different (as in number used once)
> b) each number is an integer
> c) each number is one greater than its predecessor (as in message sequencing) .
>
> Most likely, an implementation that conforms to the rest of the world definition
> would interwork with one that conforms to the RFC one, but with some loss of
> security, since numbers that are intended to be used only once could be reused.
>
> Q1) Can anyone point me to an authoritative source that endorses the RFC usage?
>
> Q2) Even so, since the  rest of the world usage seems to be so widely defined,
> should we change our terminology, eg specifying seqences to be strictly
> increasing when that is what is needed?
>
>   
I just did a full text search of all the RFCs using the zvon repository 
which covers up to RFC3999.  the fragment 'monotonic' (including 
'monotonically') appears in RFCs 1323, 1379, 1644, 1889, 2326, 2681, 
3571 and 3550.  All these cases (either about timestamps or TCP sequence 
numbers)  appear to use monotonically increasing in line with the 
mathematical definition although it is possible that a couple of them 
(e.g., RFC3571, s4) ought to use strictly monotonic, although the usage 
is clear from the additional words.

In many cases the phraseology is explicitly used because the sequence 
(of tiimestamps used, for example)  does not have every possible integer 
represented.

Do you have a concrete example of your problem?

Regards,
Elwyn
>  Tom Petch
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>   

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