Subject: iFCP: Application for port-number

From: Charles Monia <[email-masked]>
Date: Fri, 17 Aug 2001 15:11:05 -0700

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

Application for System (Well-Known) Port Number
    
Name :
Charles Monia
    
E-mail :
[email-masked]
        
Protocol Number :
TCP & UDP
    
Message Formats :
Mesage formats consist of encapsulated fibre channel frames each containing
a header and frame image as defined in draft-ietf-ips-iFCP-04.txt and
draft-ietf-ips-fcencapsulation.txt.

Message Types :  
Per draft-ietf-ips-iFCP-04.txt, messages consist of:

Requests and replies to start (CBIND) and terminate (UNBIND) an iFCP session

iFCP steady-state session traffic consists of Fibre Channel protocol
transactions carried by the stream of encapsulated fibre channel frames.

Message opcodes :
Op Codes for:
CBIND,
UNBIND

All other traffic contains fibre channel opcodes carried in the encapsulated
fibre channel frames.

Message Sequences :
A CBIND is issued to start an iFCP session.  A session is started when an
accept response is received.  Thereafter, the sending and receivind devices
use iFCP as a transport medium for fibre channel frames.

An UNBIND message is used to gracefully terminate an iFCP session.

Protocol functions :
Internetwork of legacy Fibre Channel devices via a TCP/IP transport.

Broadcast or Multicast used ?
no
    
How and what for Broadcast or Multicast is used (if used):

Description :
http://www.ietf.org/internet-drafts/draft-ietf-ips-ifcp-03.txt
(latest posted version)
http://www.ietf.org/internet-drafts/draft-ietf-ips-ifcp-04.txt
(Submitted but not posted as of 8/17/2001)

Name of the port :
iFCP System Port

Short name of the port :
iFCP-port