Re: Final SPKM draft...

Jan Luehe <luehe@caribe-85.eng.sun.com> Tue, 09 January 1996 18:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12796; 9 Jan 96 13:55 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12792; 9 Jan 96 13:55 EST
Received: from pad-thai.cam.ov.com by CNRI.Reston.VA.US id aa10537; 9 Jan 96 13:55 EST
Received: from MIT.EDU by pad-thai.cam.ov.com (8.6.12/) with SMTP id <NAA01146@pad-thai.cam.ov.com>; Tue, 9 Jan 1996 13:12:56 -0500
Received: from mercury.Sun.COM by MIT.EDU with SMTP id AA13317; Tue, 9 Jan 96 13:09:45 EST
Received: from Eng.Sun.COM by mercury.Sun.COM (Sun.COM) id KAA09659; Tue, 9 Jan 1996 10:03:49 -0800
Received: from caribe.eng.sun.com (caribe-85.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA23418; Tue, 9 Jan 1996 10:03:46 -0800
Received: from mosel.eng.sun.com by caribe.eng.sun.com (5.x/SMI-SVR4) id AA10068; Tue, 9 Jan 1996 10:03:12 -0800
Received: by mosel.eng.sun.com (SMI-8.6/SMI-SVR4) id KAA18237; Tue, 9 Jan 1996 10:05:25 -0800
Date: Tue, 09 Jan 1996 10:05:25 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jan Luehe <luehe@caribe-85.eng.sun.com>
Message-Id: <199601091805.KAA18237@mosel.eng.sun.com>
To: cat-ietf@mit.edu
Subject: Re: Final SPKM draft...
Cc: cadams@bnr.ca
X-Sun-Charset: US-ASCII

Hi there,


the ASN.1 type defintion of REP_TI_TOKEN in the new SPKM draft 
(draft-ietf-cat-spkmgss-05.txt) contains one ambiguity regarding
the 2 DNs (src_name and targ_name), one of which is OPTIONAL
(src_name). The current definiton puts the OPTIONAL name first,
which causes an ambiguity, since an ASN.1 parser cannot determine
if the first Name it encounters is src_name or targ_name:



   REP_TI_TOKEN ::= SEQUENCE {

		...

           src_name         Name OPTIONAL,
           targ_name        Name,

		...
           }



The correct definition should put the OPTIONAL name last:


   REP_TI_TOKEN ::= SEQUENCE {

		...

           targ_name        Name,
           src_name         Name OPTIONAL,

		...
           }


This corresponds to the order found in REQ_TOKEN and REP_IT_TOKEN.



Jan Luehe