Subject: iSNS: Application for port-number

From: Joshua Tseng <[email-masked]>
Date: Fri, 17 Aug 2001 16:46:17 -0700

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Friday, August 17, 2001 4:42 PM
To: [email-masked]; [email-masked]
Subject: Application for port-number

Application for System (Well-Known) Port Number
    
Name :
Josh Tseng
    
E-mail :
[email-masked]
        
Protocol Number :
TCP & UDP
    
Message Formats :
Tag-Length-Value (T-L-V)

Message Types :  
Request, reply, interrupt
    
Message opcodes :
   Register Dev Attr Req     RegDevAttr    0x0001
   Dev Attr Query Request    DevAttrQry    0x0002
   Dev Get Next Request      DevGetNext    0x0003
   Deregister Dev Request    DeregDev      0x0004
   SCN Register Request      SCNReg        0x0005
   SCN Deregister Request    SCNDereg      0x0006
   SCN Event                 SCNEvent      0x0007
   State Change Notification SCN           0x0008
   DD Register               DDReg         0x0009
   DD Deregister             DDDereg       0x000A
   DDS Register              DDSReg        0x000B
   DDS Deregister            DDSDereg      0x000C
   Entity Status Inquiry     ESI           0x000D
   Name Service Heartbeat    Heartbeat     0x000E

   Register Dev Attr Rsp     RegDevRsp     0x8001
   Dev Attr Query Rsp        DevAttrQryRsp 0x8002
   Dev Get Next Rsp          DevGetNextRsp 0x8003
   Deregister Dev Rsp        DeregDevRsp   0x8004
   SCN Register Rsp          SCNRegRsp     0x8005
   SCN Deregister Rsp        SCNDeregRsp   0x8006
   SCN Event Rsp             SCNEventRsp   0x8007
   SCN Response              SCNRsp        0x8008
   DD Register Rsp           DDRegRsp      0x8009
   DD Deregister Rsp         DDDeregRsp    0x800A
   DDS Register Rsp          DDSRegRsp     0x800B
   DDS Deregister Rsp        DDSDeregRsp   0x800C
   Entity Stat Inquiry Rsp   ESIRsp        0x800D

Message Sequences :
Client sends request, server sends response.  Server may asynchronously send
interrupt to client
    
Protocol functions :
Protocol for managing iSCSI devices and iFCP gateways

Broadcast or Multicast used ?
yes
    
How and what for Broadcast or Multicast is used (if used):
Multicast is optional, and may be used by clients for discovering location
of iSNS server, monitoring its status, and fail-over to a new server if
necessary.
                
Description :
http://www.ietf.org/internet-drafts/draft-ietf-ips-isns-04.txt
    
Name of the port :
iSNS Server Port

Short name of the port :
iSNS