ISO/IEC 14165-243:2012 情報技術—ファイバーチャネル—パート243：バックボーン3（FC-BB-3） | ページ 6

3.1.1

ぽっちゃり

FC-BB-3_ATM または FC-BB-3_SONET デバイスのいずれかを指します。

3.1.2

B_ポート

FC-BB-3_ATM, FC-BB-3_SONET, または FC-BB-3_IP を実装し、FC スイッチの E_Port に接続するデバイスのブリッジ ポート

3.1.3

B_port_name

識別目的で B_Port (3.1.2 を参照) を識別する name_Identifier (3.1.20 を参照)

注記1名前の形式はFC-SW-4で規定されている。

3.1.4

BSW

バックボーンスイッチの総称

注記 1: FC-SW-4 を参照。

3.1.5

コードワード

シンボルに対応するコードのビットのシーケンス

3.1.6

E_Por

別の E_Port に接続してスイッチ間リンクを作成するファブリック拡張ポート

注記 1: FC-SW-4 を参照。

3.1.7

E_PortName

E_Port (3.1.6 を参照) を識別する Name_Identifier (3.1.20 を参照)

3.1.8

生地名

ファブリックに関連付けられた Name_Identifier (3.1.20 を参照)

注記 1: FC-SW-4 を参照。

3.1.9

F_Port

非ループ N_Port がファブリックに接続されるポート

注記 1:このポートには FL_Port は含まれません。

注記 2: FC-SW-4 および FC-FS-2 を参照。

3.1.10

F_PortName

F_Port (3.1.9 を参照) を識別する Name_Identifier (3.1.20 を参照)

3.1.11

ファブリックの初期化

ファブリックの構成と構築のプロセス

注記 1: FC-SW-4 を参照。

3.1.12

FC-BB-3_ATM

一方の側でファイバ チャネル スイッチド ネットワークと、もう一方の側で ATM ネットワークとインターフェイスする機器を定義するモデル

3.1.13

FC-BB-3_GFPT

GFPT WAN インフラストラクチャ全体で 2 つの非調停ループ FC 物理ポートを相互接続するためのゲートウェイ機能を定義する機器モデル

注記 1:任意速度の WAN トランスポートと、バッファ間フロー制御の距離拡張の両方をサポートします。

3.1.14

FC-BB-3_IP

一方の側でファイバー チャネル スイッチド ネットワークと、もう一方の側で IP ネットワークとインターフェイスする機器を定義するモデル

3.1.15

FC-BB-3_SONET

一方の側でファイバー チャネル スイッチド ネットワークとインターフェイスし、もう一方の側で SONET/SDH ネットワークとインターフェイスする機器を定義するモデル

3.1.16

FC_Port

ポート FC フレームの生成/終了および/または転送、および FC プリミティブ信号とプリミティブ シーケンスの生成/終了

注記 1: FC_Port には、N_Port, F_Port, E_Port, B_Port, VE_Port, および B_Access が含まれます。

3.1.17

ファイバー チャネル バックボーン リンク

2 台の FC-BB-3 デバイス間の通信に使用される Transport Trail または同等のネットワーク チャネル接続

注記1:これには、FC-BBW_ATM, FC-BBW_SONET, FC-BB-3_IP, およびGFPT_WANリンクが含まれます。

注記 2:ファイバ チャネル バックボーン リンクは、場合によっては、複数の物理接続または論理接続で構成される場合があることに注意してください。

3.1.18

一般的なフレーミング手順

CFP

データ (つまり、PDU または 8B/10B エンコード文字) をオクテット同期 (つまり、SONET, SDH, OTN) およびビット同期 (つまり、PDH) ワイド エリア ネットワーク トランスポート インフラストラクチャに適合させるための手順。ITU-T によって指定されています。

注記 1:ワイド エリア ネットワークのトランスポート インフラストラクチャは、ITU-T によって指定されています。

注記 2: ITU-T Rec. G.7041/Y.1303 を参照。

3.1.19

キープアライブのタイムアウト値

K_A_TOV

Link Keep Alive (LKA) ELS が LKA 発行のトリガーとして使用するタイマー

注記1: LKA ELSについてはFC-LSを参照。

3.1.20

name_identifier

60 ビットの値の前に 4 ビットの Network_Address_Authority 識別子を付けた 64 ビットの識別子で、ファイバー チャネル内のエンティティ (N_Port, ノード、F_Port, またはファブリックなど) を識別するために使用されます (FC-FS-2 を参照)

3.1.21

node_mame

ノードに関連付けられた Name_Identifier (3.1.20 を参照) (FC-FS-2 を参照)

3.1.22

N_Port

FC-4 チャネル トラフィックを生成/終了するデバイス ポート

3.1.23

N_PortName

N_Port (3.1.22 を参照) を識別する name_Identifier (3.1.20 を参照)

3.1.24

オーダーセット

FC-FS-2 を参照してください。

3.1.25

傑出した投票条件

BBW が P ビット (5.5.4.7 を参照) を 1 に設定したコマンド メッセージを送信し、F ビット (5.5.4.7 を参照) を 1 に設定した応答メッセージをまだ受信していない状態 (6.3.5 を参照)

3.1.26

シンプルなフロー制御

SFC

ATM/SONET WAN を介して 2 つの FC-BB-3_ATM または FC-BB-3_SONET デバイス間で適用できるフロー制御プロトコル

3.1.27

選択的再送フロー制御

SR フロー制御

ATM/SONET WAN を介して 2 つの FC-BB-3_ATM または FC-BB-3_SONET デバイス間で適用できるスライディング ウィンドウ フロー制御プロトコル

注記SR フロー制御は、フロー制御とエラー回復の両方を提供します。

3.1.28

スイッチ名

スイッチまたはブリッジ デバイスを識別する Name_Identifier (3.1.20 を参照)

注記1名前の形式はFC-FS-2で規定されている。各スイッチおよびブリッジ デバイスは、ファブリック内で一意の Switch_Name を提供します。

3.1.29

WAN インターフェイス

広域ネットワークに接続するインターフェース

注記 1: WAN インターフェースは、物理的 (例えば、ATM, SONET) または論理的 (例えば、GFPT_WAN) である可能性があります。

3.2.1

AAL

ATM Adaptation Layer

collection of standardized protocols that adapt user traffic to 48-octet payloads that may be placed in a cell-formatted stream

Note 1 to entry: The AAL is subdivided into the Convergence Sublayer (CS) and the Segmentation and Reassembly (SAR) sublayer. There are currently four types of AALs (i.e., AAL1, AAL2, AAL3/4, and AAL5) to support the various service categories.

3.2.2

AAL Service Categories

the ATM Forum has defined five Traffic Service Categories supported by the AALs: Constant Bit Rate (CBR), Variable Bit Rate-Real Time (VBR-RT), Variable Bit Rate-Non Real Time (VBR-NRT), Available Bit Rate (ABR), and Unspecified Bit Rate (UBR)

3.2.3

AAL Type 5

AAL5

protocol standard that is used in FC-BB-3_ATM

Note 1 to entry: AAL5 was originally intended for variable bit rate traffic not requiring source-destination timing relation.

Note 2 to entry: AAL5 is now also used with applications that have constant bit rate traffic where source-destination timing relation is important.

3.2.4

ATM

Asynchronous Transfer Mode

Note 1 to entry: Broadband-ISDN standards defined by ITU-T and the ATM Forum.

3.2.5

ATM QoS parameters

set of performance characteristics of the contracted ATM connection

Note 1 to entry: Six ATM QoS parameters are currently defined: Peak-to-peak Cell Delay Variation (CDV), Maximum Cell Transfer Delay (maxCTD), Cell Loss Ratio (CLR), Cell Error Ratio (CER), Severely Errored Cell Block Ratio (SECBR), and Cell Misinsertion Rate (CMR).

3.2.6

ATM Traffic Descriptor

ttraffic characteristics of an ATM connection

Note 1 to entry: A Connection Traffic Descriptor includes a Source Traffic Descriptor, CDV Tolerance (CDVT), and a Conformance definition. A Source Traffic Descriptor is described by the following parameters: Peak Cell Rate (PCR), Sustainable Cell Rate (SCR), Maximum Burst Size (MBS), and a Minimum Cell Rate (MCR).

3.2.7

Cell Loss Priority

CLP

one-bit field in the ATM cell header specifying whether the cell is more (i.e., CLP=1) or less (i.e., CLP=0) likely to be discarded by an ATM network experiencing congestion

3.2.8

Cell Loss Ratio

CLR

QoS parameter that gives the ratio of lost cells to the total number of transmitted cells

3.2.9

Connection Admission Control

CAC

actions taken by the ATM network to accept or reject a connection request based on its QoS and traffic parameter requirements and then route this connection across the network

3.2.10

Convergence Sublayer Protocol Data Unit

PDU used at the Convergence Sublayer (CS) for passing information between the higher layers and the Segmentation and Reassembly (SAR) sublayer that is located below the CS where the cell conversion takes place (see 3.2.1)

3.2.11

GCRA

method applied at the network side of the UNI (see 3.2.19) to test the conformance of an ATM cell to its traffic contract

3.2.12

Operations, Administration, And Maintenance

OAM

management framework defined by the ITU

Note 1 to entry: OAM cells are special purpose ATM cells exchanged between an ATM end-system and an ATM switch and between ATM switches. OAM cells are used for network fault and performance management and analysis.

3.2.13

Permanent Virtual Circuit

PVC

preconfigured logical connection between two ATM devices

3.2.14

Permanent Virtual Connection

PVC

ATM term for a Permanent Virtual Circuit (see 3.2.13) between ATM devices

Note 1 to entry: The terms may be used interchangeably.

3.2.15

Switched Virtual Call

generic term that refers to switched virtual circuits (see 3.2.16) and switched virtual connections (see 3.2.17)

3.2.16

Switched Virtual Circuit

logical ATM connection established via signaling

Note 1 to entry: End systems transmit a UNI 3.1/4.0 signaling request via the Q.2931 Signaling Protocol.

3.2.17

Switched Virtual Connection

SVC

ATM term for Switched Virtual Circuit (see 3.2.16)

3.2.18

Usage Parameter Control

UPC

set of policing mechanisms implemented by the network at the UNI (see 3.2.19) to monitor and control traffic submitted by each end user

3.2.19

User-network Interface

UNI

interface, defined as a set of protocols and traffic characteristics, between the customer premises equipment and the ATM networks

3.2.20

Virtual Channel

one of several logical connections defined within one Virtual Path (see 3.2.23) between two ATM devices

3.2.21

Virtual Channel Connection

VCC

concatenation of Virtual Channel Links

Note 1 to entry: Switching cells within an ATM switch for a given VCC is based on the VPI/VCI (see 3.2.25) value indicated on the cell header.

3.2.22

Virtual Circuit

VC

connection that is set up across the network between a source and a destination where a fixed route is chosen for the entire session and bandwidth and ID dynamically allocated to the user

3.2.23

Virtual Path

VP

logical connection between two ATM devices (e.g., CPEs, switches)

Note 1 to entry: A Virtual Path consists of a set of Virtual Channels (see 3.2.20).

3.2.24

Virtual Path Connection

VPC

concatenation of Virtual Path Links (VPLs)

Note 1 to entry: Switching cells within an ATM switch for a given VPC is based on the VPI value indicated on the cell header.

3.2.25

Virtual Path Identifier/Virtual Channel Identifier

VPI/VCI

combination of two numbers, namely the VPI and the VCI, used to identify a Virtual Connection (VC) and switch cells in an ATM network

3.3.1

Administrative Unit

AU

SDH-specific information structure, consisting of an STS SPE (see 3.3.14) and its associated set of STS pointer/pointer action bytes

3.3.2

Concatenated Synchronous Transport Signal Level N

STS-Nc

STS-N Line layer signal in which the STS Envelope Capacities from the N STS-1s have been combined to carry an STS-Nc Synchronous Payload Envelope (SPE) (see 3.3.14) that is transported not as several separate signals but as a single entity

Note 1 to entry: The equivalent SDH term for an STS-3c SPE is a VC-4.

3.3.3

container

SDH term that is equivalent to the payload capacity of a Synchronous Payload Envelope (SPE) (see 3.3.14)

3.3.4

Operations, Administration, and Maintenance

OAM

management framework defined by the ITU

Note 1 to entry: OAM cells are special purpose ATM cells exchanged between an ATM end-system and an ATM switch and between ATM switches.

Note 2 to entry: OAM cells are used for network fault and performance management and analysis.

3.3.5

Optical Carrier Level N

OC-N

optical signal that results from an optical conversion of an STS-N signal

Note 1 to entry: SDH does not make the distinction between a logical signal (e.g., STS-1 in SONET) and a physical signal (e.g., OC-1 in SONET). The equivalent SDH term for both logical and physical signals is Synchronous Transport Module Level M (STM-M), where M = (N/3). There are equivalent STM-M signals only for values of N = 3, 12, 48, and 192.

3.3.6

Optical Transport Network

OTN

framework of ITU standards for optical signal multiplexing and transport

3.3.7

Path

logical connection between the point at which a standard frame format for the signal at the given rate is assembled, and the point at which the standard frame format for the signal is disassembled

Note 1 to entry: The equivalent SDH term is also Path.

3.3.8

Payload Pointer

pointer that indicates the location of the beginning of the Synchronous Payload Envelope (see 3.3.14)

Note 1 to entry: The equivalent SDH term is pointer.

3.3.9

Plesiochronous Digital Hierarchy

PDH

bit-oriented telecommunications multiplexing and transport protocols (e.g., DS-3, E3)

3.3.10

SONET

acronym for Synchronous Optical NETwork

Note 1 to entry: SONET is a term in general usage, that refers to the rates and formats specified in ANSI T1.105.

3.3.11

STS Path Terminating Equipment

STS PTE

network elements that multiplex/demultiplex the STS payload

Note 1 to entry: STS PTEs may originate, access, modify, or terminate the STS Path Overhead necessary to transport the STS payload, or may perform any combination of these actions.

3.3.12

super-rate signals

signal that has to be carried by a Concatenated Synchronous Transport Signal level Nc (STS-Nc)

Note 1 to entry: There is no equivalent SDH term.

3.3.13

Synchronous Digital Hierarchy

SDH

family of ITU-T standards whose technical contents closely resemble that found for the SONET family of ANSI standards

3.3.14

STS Synchronous Payload Envelope

STS SPE

125-microsecond frame structure composed of STS Path Overhead and bandwidth for payload

Note 1 to entry: The term generically refers to STS-1 SPEs and STS-Nc SPEs. The equivalent SDH term for STS-1 SPE is Virtual Container level 3 (VC-3). The equivalent SDH term for STS-3c SPE is Virtual Container level 4 (VC-4). The equivalent SDH term for STS-Nc SPE (N>3) is Virtual Container level 4-Xc (VC-4-Xc), where X=(N/3).

3.3.15

Synchronous Transport Module Level M

STM-M

transport signals for the Synchronous Digital Hierarchy (SDH) (see 3.3.13)

Note 1 to entry: Defined signals exist at rates of M times 155.52 Mbit/s, where M = 1, 4, 16, or 64 .

Note 2 to entry: These are equivalent to SONET OC-N signals, where N = 3M.

3.3.16

Synchronous Transport Signal Level N

STS-N

signal obtained by byte interleaving N STS-1 signals together

Note 1 to entry: The rate of the STS-N is N times 51.840 Mbit/s.

Note 2 to entry: SDH does not make the distinction between a logical signal (e.g. STS-N in SONET) and a physical signal (e.g. OC-N in SONET).

Note 3 to entry: The equivalent SDH term for both logical and physical signals is Synchronous Transport Module Level M (STM-M), where M = (N/3). There are equivalent STM-M signals only for values of N = 3, 12, 48, and 192.

3.3.17

Tributary Unit

TU

SDH term for SONET Virtual Tributary (see 3.3.19)

3.3.18

Virtual Container

VC

SDH term for either an STS or VT SPE

3.3.19

Virtual Tributary

VT

structure designed for transport and switching of sub-STS-1 payloads

Note 1 to entry:: There are currently four sizes of VT. The equivalent SDH term is Tributary Unit (see 3.3.17).

3.4.1

B_Access

component of the FC Entity (see 3.4.8) that interfaces with the FCIP_LEP (see 3.4.20) component of the FCIP Entity (see 3.4.15) on one side and the B_Port on the other side

3.4.2

B_Access_Name

Name_Identifier (see 3.1.20) of B_Access portal

3.4.3

B_Access Virtual ISL

Virtual ISL (see 3.4.27) that connects two B_Access portals

3.4.4

control and service module

CSM

control component of the FC-BB-3_IP interface that mainly handles connection management

Note 1 to entry: CSM interfaces with the PMM (see 3.4.22).

3.4.5

encapsulated FC frame

SOF/EOF delimited FC frame prefixed with a 28-byte FC frame Encapsulation Header (see RFC 3643)

3.4.6

Encapsulated Frame Receiver Portal

TCP access point through which an encapsulated FC frame (see 3.4.5) is received from the IP network by an FCIP_DE (see 3.4.14)

3.4.7

Encapsulated Frame Transmitter Portal

TCP access point through which an encapsulated FC frame (see 3.4.5) is transmitted to the IP network by the FCIP_DE (see 3.4.14)

3.4.8

FC Entity

principal interface point to the FC switched network on one side and in combination with the FCIP Entity to the IP network on the other side.

Note 1 to entry: It is the data forwarding component of the FC-BB-3_IP interface consisting of VE_Port(s) (see 3.4.24) and/or B_Access (see 3.4.1) portals.

3.4.9

FC Entity Protocol Layer

protocol layer that lies between the Fibre Channel level FC-2 and the FCIP Entity Protocol Layer (see 3.4.16)

Note 1 to entry: Its primary function is to support one or more Virtual E_Ports (see 3.4.24) or B_Access (see 3.4.1) portals and to communicate with the FCIP Entity (see 3.4.8).

3.4.10

FC Receiver Portal

access point through which an FC frame and timestamp enters an FCIP_DE (see 3.4.14) from the VE_Port/ B_Access (see 3.4.24/3.4.1)

3.4.11

FC Transmitter Portal

access point through which an FC frame and timestamp leaves an FCIP_DE (see 3.4.14) to the VE_Port/ B_Access (see 3.4.24/3.4.1)

3.4.12

FC-BB-3_IP device

device defined by the FC-BB-3_IP model

3.4.13

FC-BB-3_IP interface

the point that has interfaces to the FC switched network on one side and the IP network on the other side

Note 1 to entry: FC-BB-3_IP interface consists of a Switching Element, FC/FCIP Entity pair(s), the CSM, and the PMM.

3.4.14

FCIP Data Engine

FCIP_DE

the data forwarding component of the FCIP Entity's (see 3.4.15) FCIP_LEP (see 3.4.20) that handles FC frame encapsulation, de-encapsulation, and transmission of encapsulated frames through a single TCP connection

3.4.15

FCIP Entity

data forwarding component of the FC-BB-3_IP interface consisting of the FCIP_LEP (see 3.4.20) and it is the principal interface point to the IP network on one side and in combination with the FC Entity (see 3.4.8) to the FC switched network on the other side

Note 1 to entry:: Its primary function is formatting, encapsulating, and forwarding encapsulated FC frames (see 3.4.5) across the IP network interface.

3.4.16

FCIP Entity Protocol Layer

protocol layer that lies between the FC Entity (see 3.4.8) layer and the TCP layer

3.4.17

FCIP frame

FCIP term for an encapsulated FC frame (see 3.4.5)

3.4.18

FCIP Link

virtual link that connects an FCIP_LEP (see 3.4.20) in one FC-BB-3_IP device (see 3.4.12) with another

Note 1 to entry: It consists of one or more TCP connections.

3.4.19

FCIP Link Originator and Acceptor

the FC-BB-3_IP FCIP_LEP (see 3.4.20) that originates an FCIP Link is defined as the FCIP Link Originator

Note 1 to entry: The corresponding FCIP_LEP that accepts this link is defined as the FCIP Link Acceptor.

3.4.20

FCIP Link Endpoint

FCIP_LEP

component of an FCIP Entity (see 3.4.15) that contains one or more FCIP_DEs (see 3.4.14)

3.4.21

FCIP Transit Time

FTT

total transit time of an encapsulated Fibre Channel frame in the IP network

3.4.22

Platform Management Module

PMM

management component of the FC-BB-3_IP interface that handles time synchronization, discovery, and security

Note 1 to entry:: It interfaces with the CSM (see 3.4.4).

3.4.23

Request For Comment

RFC

documents put out by the IETF

3.4.24

Virtual E_Port

VE_Port

data forwarding component of the FC Entity (see 3.4.8) that emulates an E_Port (see 3.1.6)

Note 1 to entry:: The term virtual indicates the use of a non Fibre Channel link connecting the VE_Ports. In the case of the FC-BB-3_IP model, a VE_Port interfaces with the FCIP_LEP component (see 3.4.20) of the FCIP Entity (see 3.4.15) on one side and a Fibre Channel Switching Element on the other side.

3.4.25

VE_Port_Name

Name_Identifier (see 3.1.20) of the VE_Port (see 3.4.24)

3.4.26

VE_Port Virtual ISL

Virtual ISL (see 3.4.27) that connects two VE_Ports (see 3.4.24)

3.4.27

Virtual ISL

ISL that connects two VE_Ports (see 3.4.24) or two B_Access portals (see 3.4.1) across a non-FC link

3.5.1

ASFC_PAUSE

GFPT_WAN Primitive Signal used to pause flow on a GFPT_WAN link (see 10.3.4)

Note 1 to entry: ASFC_PAUSE is never transmitted to, or expected from, FC_Ports.

3.5.2

ASFC_RESUME

GFPT_WAN Primitive Signal used to resume flow on a GFPT_WAN link (see 10.3.4)

Note 1 to entry: ASFC_RESUME is never transmitted to, or expected from, FC_Ports.

3.5.3

ELP

Exchange Link Parameters SW_ILS (see FC-SW-4)

3.5.4

FLOGI

Fabric Login ELS (see FC-LS)

3.5.5

F_BSY

Fabric Busy (see FC-FS-2)

3.5.6

GFP Server

Generic Framing Procedure (see 3.1.18) adaptation/de-adaptation engine

3.5.7

GFPT

(Asynchronous) Transparent Generic Framing Procedure (see 3.1.18)

3.5.8

GFPT_WAN interface

Transport network-side interface, on an FC-BB-3_GFPT device, corresponding to one GFPT_WAN facility (see 3.5.10), and to one Transport Trail (see 3.5.24)

Note 1 to entry: May or may not correspond to the full SONET/SDH/OTN/PDH access facility/bandwidth.

3.5.9

GFPT_WAN link

Transport Trail (see 3.5.24) assigned to one GFPT_WAN facility (see 3.5.10)

3.5.10

GFPT_WAN facility

Transport Trail (see 3.5.24), GFP Server (see 3.5.6), FC-BB-3_GFPT devices, and their respective GFPT_WAN interfaces (see 3.5.8), corresponding to one interconnected FC_Port pair

3.5.11

inbound

sent from the FC-BB-3_GFPT device to the attached FC_Port

3.5.12

ISL

Inter-Switch Link (see FC-SW-4)

3.5.13

LEM

Login Exchange Monitor (see 10.3.3)

3.5.14

LS_ACC

Link Service Accept frame (see FC-LS)

3.5.15

LS_RJT

Link Service Reject frame (see FC-LS)

3.5.16

outbound

sent from the attached FC_Port to the FC-BB-3_GFPT device

3.5.17

PING

GFPT_WAN Primitive Signal used to initiate latency measurement on a GFPT_WAN link

Note 1 to entry: PING is never transmitted to, or expected from, FC_Ports.

3.5.18

PING_ACK

GFPT_WAN Primitive Signal used to reply to a PING and complete round-trip latency measurement on a GFPT_WAN link

Note 1 to entry: PING_ACK is never transmitted to, or expected from, FC_Ports.

3.5.19

PLOGI

Port Login (see FC-LS)

3.5.20

P_BSY

N_Port Busy (see FC-FS-2)

3.5.21

RPSC ELS

Report Port Speed Capabilities ELS (see FC-LS)

3.5.22

SW_ACC

SW Accept Reply frame (see FC-SW-4)

3.5.23

SW_RJT

SW Reject Reply frame (see FC-SW-4)

3.5.24

Transport Trail

contiguously or virtually-concatenated signal group (see T1.105-2001) comprised of one or more standardized SONET/SDH/OTN/PDH synchronous transport signals

3.5.25

WAN Primitive Signal

ASFC_PAUSE (see 3.5.1), ASFC_RESUME (see 3.5.2), PING (see 3.5.17), or PING_ACK (see 3.5.18) Primitive Signal

Note 1 to entry: These Primitive Signals are always generated and terminated by FC-BB-3_GFPT devices and transmitted only between FC-BB-3_GFPT devices.

Note 2 to entry: They are never transmitted to nor received from FC_Ports.

3.5.26

WAN_HOLDOFF_TOV

time-out value, specific to FC-BB-3_GFPT devices, which defines the period that elapses, following detection/ indication of a GFPT_WAN link failure, before a GFPT_WAN Down condition is declared for the purposes of the state machine described in 10.3.2

Note 1 to entry: The criteria for such detection are WAN-specific and outside the scope of this standard.

3.9.1

expected

keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may also be implemented

3.9.2

ignored

keyword used to describe an unused bit, byte, word, field or code value. The content or value of an ignored bit, byte, word, field or code value shall not be examined by the receiving device and may be set to any value by the transmitting device

3.9.3

invalid

keyword used to describe an illegal or unsupported bit, byte, word, field or code value. Receipt of an invalid bit, byte, word, field or code value shall be reported as an error

3.9.4

mandatory

keyword indicating an item that is required to be implemented as defined in this standard

3.9.5

may

keyword that indicates flexibility of choice with no implied preference (equivalent to"may or may not")

3.9.6

may not

keyword that indicates flexibility of choice with no implied preference (equivalent to"may or may not")

3.9.7

optional

keyword that describes features that are not required to be implemented by this standard. However, if any optional feature defined by this standards is implemented, then it shall be implemented as defined in this standard

3.9.8

reserved

keyword referring to bits, bytes, words, fields and code values that are set aside for future standardization. A reserved bit, byte, word or field shall be set to zero, or in accordance with a future extension to this standard.

Recipients are not required to check reserved bits, bytes, words or fields for zero values. Receipt of reserved code values in defined fields shall be reported as an error

3.9.9

shall

keyword indicating a mandatory requirement. Designers are required to implement all such mandatory requirements to ensure interoperability with other products that conform to this standard

3.9.10

should

keyword indicating flexibility of choice with a strongly preferred alternative; equivalent to the phrase"it is strongly recommended"

3.9.11

x or xx

the value of the bit or field is not relevant