re:Sequence numbers in SPKM

"carlisle (c.m.) adams" <cadams@bnr.ca> Tue, 07 May 1996 18:36 UTC

X400-Received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 7 May 1996 13:53:43 -0400
X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 7 May 1996 13:52:36 -0400
X400-Received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 7 May 1996 13:52:00 -0400
Date: Tue, 07 May 1996 13:52:00 -0400
X400-Originator: /dd.id=1651623/g=carlisle/i=cm/s=adams/@bnr.ca
X400-Mts-Identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; bcars520.b.232:07.04.96.17.52.36]
X400-Content-Type: P2-1984 (2)
Content-Identifier: re:Sequence n...
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "carlisle (c.m.) adams" <cadams@bnr.ca>
Message-Id: <"21309 Tue May 7 13:52:49 1996"@bnr.ca>
To: dennis.glatting@cybersafe.com
Cc: cat-ietf@mit.edu
Subject: re:Sequence numbers in SPKM

Hi Dennis,

In message "Sequence numbers in SPKM", dennis.glatting@Cybersafe.com 
writes:

>
>The following is a text fragment from section 3.2.1.2 of
>draft-ietf-cat-spkmgss-06.txt.
>
>> Sequence number field: The sequence number field is
>> formed from the  sender's four-byte sequence number and a
>> Boolean direction-indicator  (FALSE - sender is the
>> context initiator, TRUE - sender is the  context
>> acceptor).  After constructing a gss_sign/getMIC() or
>> gss_seal/wrap() token, the sender's seq. number is
>> incremented by 1.
>>
>
>Sequence numbers, i.e., SeqNum, are declared as INTEGER
>in the ASN.1 syntax. This text fragment states that the
>sender's sequence number is four bytes. Is a sequence
>number's range 0..2147483647 or 0..4294967295?
>
>
>-dpg

Sorry for the delay in responding but I've been away for the
past week.  The sequence number uses the full four bytes (there
is no need to have a sign bit in the integer since there are no
negative sequence numbers), so wrap-around occurs after 4294967295.

Carlisle.

re:Sequence numbers in SPKM carlisle (c.m.) adams