RE: 'monotonic increasing'

"Gray, Eric" <Eric.Gray@marconi.com> Wed, 22 February 2006 23:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC346-0006Aw-5b; Wed, 22 Feb 2006 18:06:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FC344-0006Ab-RX for ietf@ietf.org; Wed, 22 Feb 2006 18:06:32 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC344-0000Vv-H5 for ietf@ietf.org; Wed, 22 Feb 2006 18:06:32 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id k1MN6TgL001613; Wed, 22 Feb 2006 18:06:29 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA26985; Wed, 22 Feb 2006 18:06:28 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2657.72) id <FG7R4TCY>; Wed, 22 Feb 2006 18:06:27 -0500
Message-ID: <313680C9A886D511A06000204840E1CF0DAC1720@whq-msgusr-02.pit.comms.marconi.com>
From: "Gray, Eric" <Eric.Gray@marconi.com>
To: "'Tom.Petch'" <sisyphus@dial.pipex.com>
Date: Wed, 22 Feb 2006 18:06:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
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>
Errors-To: ietf-bounces@ietf.org

Tom,

	I'm sorry to disagree, but I feel that the term "monotonic" has
a much better defined meaning than most terms in general (including -
for example - the term "term").

	There are definitely applications for the phrase "monotonically
increasing" where the terminology is exactly correct and very hard to
"word-smith" around.

	There are also cases in which the appropriate phrase might have
been "strictly monotonically increasing", and for one reason or another
the word "strictly" was omitted.  In such cases, it either was clear
what was meant at the time, or it has become clear in the mean time.

	I really do not see why we need to get quite so retentive about
terminology when we have the ability to ask questions about anything
we don't understand completely.  Nor do I believe that there is any
way that we could avoid the need to ask questions strictly as a result
of using perfect terminology (or phraseology).

--
Eric

--> -----Original Message-----
--> From: Tom.Petch [mailto:sisyphus@dial.pipex.com] 
--> Sent: Wednesday, February 22, 2006 3:50 PM
--> To: ietf; Frank Ellermann
--> Subject: Re: 'monotonic increasing'
--> 
--> ----- Original Message -----
--> From: "Frank Ellermann" <nobody@xyzzy.claranet.de>
--> To: <ietf@ietf.org>
--> Sent: Tuesday, February 21, 2006 3:57 PM
--> Subject: Re: 'monotonic increasing'
--> 
--> > Marshall Eubanks wrote:
--> >
--> > > a RFC-2119 type RFC to define mathematical terms ?
--> >
--> > Maybe more like some glossaries (Internet, security,
--> > I18N, ...), informational RFCs.  But I think that's
--> > unnecessary.  There are online math. dictionaries,
--> > authors can provide references for unlear terms, or
--> > say what they mean.
--> >
--> > > Otherwise this thread is unlikely to do much to
--> > > change the situation.
--> >
--> > It highlights why "clear" terms in RFC are good,
--> > defined by reference or inline.  In some groups
--> > saying 'header' instead of 'header field', 'byte'
--> > instead of 'octet', or 'charset' instead of IIRC
--> > 'encoded character repertoire' is enough to start
--> > a thread.  And 'monotonic increasing' instead of
--> > 'strictly (monotonic) increasing' is apparently a
--> > similar issue.
--> >                       Bye, Frank
--> >
--> 
--> What I see from this thread is that there are two common 
--> interpretations to
--> the phrase 'monotonic increasing', either a sequence in 
--> which each number is
--> greater than or equal to its predecessor, or one in which 
--> each number is
--> strictly greater than its predecessor, with the former 
--> meaning having somewhat
--> the greater support (at least amongst those with access to 
--> text books): which,
--> of itself, makes it a risky term to use in a specification.
--> 
--> I still think that it is sometimes used in RFC and I-D in a
--> third sense, of a sequence of integers increasing by one 
--> each time, not a
--> meaning anyone has supported. But only the editor can know 
--> what is really
--> intended.
--> 
--> So, the next time I see it used, perhaps in a Last Call of 
--> a pkix, kink or secsh
--> I-D, I will seek further clarification.
--> 
--> 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