datatracker.ietf.org
Sign in
Version 5.3.1, 2014-04-16
Report a bug

Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)
RFC 3822

Document type: RFC - Proposed Standard (July 2004; Errata)
Updated by RFC 7146
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 3822 (Proposed Standard)
Responsible AD: Allison Mankin
Send notices to: <ElizabethRodriguez@ieee.org>, <black_david@emc.com>

Network Working Group                                        D. Peterson
Request for Comments: 3822             Computer Network Technology (CNT)
Category: Standards Track                                      July 2004

           Finding Fibre Channel over TCP/IP (FCIP) Entities
           Using Service Location Protocol version 2 (SLPv2)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document defines the use of Service Location Protocol version 2
   (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities.

1.  Introduction

   This document describes the use of the Service Location Protocol
   version 2 in performing dynamic discovery of participating Fibre
   Channel over TCP/IP (FCIP) Entities.  Implementation guidelines,
   service type templates, and security considerations are specified.

2.  Notation Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  Terminology

   Here are some definitions that may aid readers that are unfamiliar
   with either SLP or FCIP.  Some of these definitions have been
   reproduced from [RFC2608] and [RFC3105].

Peterson                    Standards Track                     [Page 1]
RFC 3822           Finding FCIP Entities Using SLPv2           July 2004

   User Agent (UA)            A process working on the client's behalf
                              to establish contact with some service.
                              The UA retrieves service information from
                              the Service Agents or Directory Agents.

   Service Agent (SA)         A process working on behalf of one or more
                              services to advertise the services and
                              their capabilities.

   Directory Agent (DA)       A process which collects service
                              advertisements.  There can only be one DA
                              present per given host.

   Scope                      A named set of services, typically making
                              up a logical administrative group.

   Service Advertisement      A URL, attributes, and a lifetime
                              (indicating how long the advertisement is
                              valid), providing service access
                              information and capabilities description
                              for a particular service.

   FCIP Entity                The principle FCIP interface point to the
                              IP network.

   FCIP Entity Name           The world wide name of the switch if the
                              FCIP Entity resides in a switch or the
                              world wide node name of the associated
                              Nx_Port.

   FCIP Discovery Domain      The FCIP Discovery Domain specifies which
                              FCIP Entities are allowed to discover each
                              other within the bounds of the scope.

4.  Using SLPv2 for FCIP Service Discovery

   At least two FCIP Entities must be involved in the entity discovery
   process.  The end result is that an FCIP Entity will discover one or
   more peer FCIP Entities.

4.1.  Discovering FCIP Entities using SLPv2

   Figure 1 shows the relationship between FCIP Entities and their
   associated SLPv2 agents.

Peterson                    Standards Track                     [Page 2]
RFC 3822           Finding FCIP Entities Using SLPv2           July 2004

            +--------------------------------------+
            |           FCIP Entity                |
            +----------------------------------+   |
            | FCIP Control and Services Module |   |
            +----------------+                 |   |
            |   SA  |   UA   |                 |   |
            +----------------+-----------------+   |
            |            TCP/UDP/IP            |   |
            +----------------+-----------------+   |
            |            Interface             |   |
            |           192.0.2.10             |   |

[include full document text]