Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h3353Q424473
	for ips-outgoing; Thu, 3 Apr 2003 00:03:26 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from 380GATE01out.mcdata.com (mcjekyll.mcdata.com [144.49.6.25])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3353M324464
	for <ips@ece.cmu.edu>; Thu, 3 Apr 2003 00:03:22 -0500 (EST)
Received: from 380GATE01.mcdata.com ([172.18.2.56]) by 380GATE01out.mcdata.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 2 Apr 2003 22:03:16 -0700
Received: from snexu01.mcdata.com ([172.24.0.13]) by 380GATE01 with InterScan Messaging Security Suite; Wed, 02 Apr 2003 22:03:16 -0700
Received: by snexu01.mcdata.com with Internet Mail Service (5.5.2653.19)
	id <DRX9BLCN>; Wed, 2 Apr 2003 21:03:15 -0800
Message-ID: <0251888E076E2B45A72536425D4D001461EBA1@snexu01.mcdata.com>
From: Siva Vaddepuri <Siva.Vaddepuri@mcdata.com>
To: "'Joshua Tseng'" <jtseng@NishanSystems.com>,
   Kevin Gibbons
	 <kgibbons@NishanSystems.com>,
   "'ips@ece.cmu.edu'" <ips@ece.cmu.edu>
Cc: "'Black_David@emc.com'" <Black_David@emc.com>
Subject: RE: Clarification regarding iSNS Message Format
Date: Wed, 2 Apr 2003 21:03:13 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 03 Apr 2003 05:03:16.0839 (UTC) FILETIME=[56558770:01C2F99E]
Sender: owner-ips@ece.cmu.edu
Precedence: bulk


Thanks.

Siva
-----Original Message-----
From: Joshua Tseng [mailto:jtseng@NishanSystems.com]
Sent: Wednesday, April 02, 2003 8:51 PM
To: Siva Vaddepuri; Kevin Gibbons; Joshua Tseng; 'ips@ece.cmu.edu'
Cc: 'Black_David@emc.com'
Subject: RE: Clarification regarding iSNS Message Format


Siva,

The authentication block is a MUST for Broadcast/Multicast messages (see
section 7.2) and a SHOULD NOT (see section 5.5) for unicast messages.

Originally there was a flag to indicate the presence of the authentication
block in the iSNS flags.  Somehow it disappeared in revision -05 (that was
in November 2001 and I don't have any record of why it was removed, but my
guess is that it was an accident).  It needs to be put back in.  We should
probably make bit 18, which would indicate "authentication block present".

Thanks for this catch.

Josh

-----Original Message-----
From: Siva Vaddepuri [mailto:Siva.Vaddepuri@MCDATA.com] 
Sent: Wednesday, April 02, 2003 1:50 PM
To: 'Kevin Gibbons'; Joshua Tseng; 'ips@ece.cmu.edu'
Subject: Clarification regarding iSNS Message Format


Hi,

Can anybody clarifiy requirements for Authentication Block in iSNS Message? 
- Is it a MUST for Broadcast/Multicast packets?
- Is it MUST-NOT for Unicast packets?

If Authentication block is optional for unicast packets how do we determine
iSNS Packet boundaries in TCP Session?

iSNS Message
   Byte   MSb                                        LSb 
   Offset 0                   15 16                   31 
          +---------------------+----------------------+ 
        0 |   iSNSP VERSION     |    FUNCTION ID       | 4 Bytes 
          +---------------------+----------------------+ 
        4 |     PDU LENGTH      |       FLAGS          | 4 Bytes 
          +---------------------+----------------------+ 
        8 |   TRANSACTION ID    |    SEQUENCE ID       | 4 Bytes 
          +---------------------+----------------------+ 
       12 |                                            |  
          |                PDU PAYLOAD                 | N Bytes 
          |                    ...                     | 
          +--------------------------------------------+ 
     12+N | AUTHENTICATION BLOCK (Multicast/Broadcast) | L Bytes 
          +--------------------------------------------+ 
                   Total Length = 12 + N + L 


Thanks,
Siva

SPECIAL NOTICE 
All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution of
confidential and privileged information is prohibited. If the reader of this
message is not the intended recipient(s) or the employee or agent
responsible for delivering the message to the intended recipient(s).

You may not distribute or copy the confidential and privileged portion of
this communication to another. Anyone who receives confidential and
privileged information in error should notify us immediately by telephone
and mail the original message to us at the above address and destroy all
copies.
 
To the extent any portion of this communication contains public information,
no such restrictions apply to that information. (gate02)
