iccp_aief_dewg_r1 (Clean) - NERC

screechingagendaΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 8 μήνες)

62 εμφανίσεις


July

15
, 20
10


Ver
3
.
0

{iccp_aief.doc}


1

Association Information Exchange Form


The attached ICCP Association Information Exchange Form has been created to
facilitate ICCP associations between ICCP nodes.
All fields are required to create an
association.

ICCP node administrators should fill out this form using their own setup
information. Thus the form will contain information supplied by
company
-
A

to
company
-
B
detailing the parameters needed during
company
-
B’s

ICCP association
configuration. Note that
similar information needs to be supplied by
company
-
B

to
company
-
A
.



ICCP Association Information Exchange Form


July
15
, 20
1
0

2

Ver
3
.
0

{iccp_aief.doc}

Date:



Company
-
A:


Contact for Company
-
A:





Company
-
B:


Contact for Company
-
B:





General Notes:










Table 1: Company
-
wide / Server independent information

1.

ICCP vendor and
platform


The name of the Company
-
A’s ICCP vendor, vendor
software version, as well what operating system and
hardware platform used for the ICCP servers.


2.

Number of possible ICCP servers:


This is the total number of ICCP servers that may be
available to

a remote client to associate with. Include
backup servers if they have unique addresses. This
number should equal the number of copies of Table 2
included in this form. Typically 1
-

10.


3.

Company A’s domain name:


The domain name of company A.
Recommended to be
the 4 character ISN node name of C
ompany
-
A.



4.

Company B’s domain name:


The domain name of company B. Recommended to be
the 4 character node name of
company
-
B
.



ICCP Association Information Exchange Form


July
15
, 20
1
0

3

Ver
3
.
0

{iccp_aief.doc}

5.

Association type


“Single direction Client
-
Server”: Enter this if
Company A’s and Company B’s ICCP nodes act as
either Client
or
Server over one association.
Information can be sent in
only one

direction per
association. The client must initiate the association.


“Dual d
irection Client
-
Server”: Enter this if Company
A’s and Company B’s ICCP nodes act as Client
and

Server over one association. Information can be sent in
either

direction per association. The association type is
determined by prior agreement between the tw
o users.
Typically “Dual direction Client
-
Server”.


6.

Association Initiation:


This field is only used if the association type is “Dual
direction Client
-
Server” and indicates which ICCPnode
shall initiate the association (e.g.
company
-
A
). The
initiator of t
he association is determined by prior
agreement between the two users.


7.

Bilateral table ID:


Company A’s bilateral table name used when Company
B is accessing Company A’s data (e.g. “1.1”).


8.

Supported ICCP services:


A list of the conformance blocks
supported by the
server (e.g. Blocks 1, 2).


9.

ICCP version:


The version of ICCP running on the server (e.g.
TASE.2 Version 1996
-
08).


10.

Shortest periodic interval:


Frequency in seconds at which Company B can request
data from Company A.


11.

Maximum MMS PDU

size.


Size in bytes of the maximum MMS protocol data unit.



ICCP Association Information Exchange Form


July
15
, 20
1
0

4

Ver
3
.
0

{iccp_aief.doc}

Table 2: ICCP Server specific information


1. Server names and descriptions:


The names by which
company
-
A
refers to these servers.
(Note: The following information boxes must remain in

same server order!)


2. IP network addresses:


If you are using TCP/IP, this optional field is the IP
address for this ICCP server if TCP/IP can be used as
the network transport.


3. AP Titles:


Object identifier representing the Application
Process
Title given to this application. The standardized format
of the AP Title is found in Appendix A.


4. AE Qualifiers


A long integer (32 bit signed) is used to qualify the
application entity.


5. Presentation Selectors (PSEL)


2 or 4 byte
number used to select the correct instance of
the presentation layer (e.g. 00 09 or 00 00 00 09).


6. Session Selectors (SSEL)


2 or 4 byte number used to select the correct instance of
the session layer (e.g. 00 09 or 00 00 00 09).


7. Transport
Selectors (TSEL)


2 or 4 byte number used to select the correct instance of
the session layer (e.g. 00 09 or 00 00 00 09).


8X.509 Certificate filename

Subject CN, and expiration date.



The current in use certificate information for this server
identified by the filename and the CN contained in the
subject field of the certificate. (Note: Only required if
running Secure ICCP)



ICCP Association Information Exchange Form


July
15
, 20
1
0

5

Ver
3
.
0

{iccp_aief.doc}



Appendix
A
: AP Title Standard


The AP Title is used by some ISO applications to determine what application is calling

since NSAP’s, TSEL’s, SSEL’s and PSEL’s of the caller may not passed to applications
upon association. The AP Title consists of 9 16 bit decimal numbers:


Field Name

1

2

3

Field format

One single 16 bit
decimal integer)

One 16 bit
decimal integer

Seven
16 bit decimal integers

Required value
in decimal

2

(joint
-
iso
-
ccitt)

16 (country
based naming
hierarchy)

3826 XXXX XXXX XXXX XXXX YYYY
0073

(3826 is the abbreviated NERC org ID used
to specify ISN applications), XXXX XXXX
XXXX XXXX is for the
registered ISN node
ID in decimal (one 16 bit decimal number for
each ASCII character in the site ID including
padding underscores), YYYY is the for the
node number (one 16 bit decimal number),
the last 16 bit number is an application
specification where d
ecimal 0073 indicates
ICCP.)


For example, an ICCP application at MAIN1 would have an AP Title of:

0002 0016 3826 0077 0065 0073 0078 0049 0073


Note: Some ICCP vendors do not provide a user interface for setting AP Titles. In this
case the user may be
required to manually edit a Directory Information Base ASCII file.


ASCII to Hex and Decimal Conversion Table:







ASCII

Dec

ASCII

Dec

ASCII

Dec

ASCII

Dec

_

95

9

57

I

73

R

82

1

49

A

65

J

74

S

83

2

50

B

66

K

75

T

84

3

51

C

67

L

76

U

85

4

52

D

68

M

77

V

86

5

53

E

69

N

78

W

87

6

54

F

70

O

79

X

88

7

55

G

71

P

80

Y

89

8

56

H

72

Q

81

Z

90

Note: Only use this ASCII conversion table to calculate the AP Title.


ICCP Association Information Exchange Form


July
15
, 20
1
0

6

Ver
3
.
0

{iccp_aief.doc}

Revision history
:

Version Date

Comments

1/16/98

Added transport layer parameters

Added AP
Title and NSAP appendices

1/23/98

Fixed IP addressing and association
parameter errors

Changed AP Title standard

2/24/98

Added ICCP vendor information

5/20/98

Added more instructions to help user
fill out forms.

5/26/98

Added cover page

Added M,R,O
column

9/25/98

Moved rows (formerly labeled 2.3


㈮㠠湯眠污扥汥搠ㄮ㌠


ㄮN⤮†)e汥瑥搠
牯r
 潲oe牬y慢 汥搠ㄮ㔩

ㄲ⼱N㤸

f渠瑡扬e′Ⱐ 桡n来搠晩d汤l‴Ⱐ㠬‹Ⱐ 湤n
10 from “Recommended” to
“Mandatory”

ㄯㄹN㤹

c楸e搠dy灯g牡灨楣a氠敲牯rs

㔯ㄳR㤹

䵯癥搠
䅳獯A楡瑩潮⁴ype a湤⁩湩瑩a瑯爠
晲潭⁔o扬攠㈠瑯⁔b扬e‱⸠⁕灤 瑥搠
癥牳楯渠湵浢敲⁡湤⁤a瑥t楮⁨敡摥爯r
景潴f爮⁛止灝

㜯ㄵTㄹ㤹

Version 2.0

Made AP Titles mandatory per
Appendix B. Removed John
Gillerman as document owner.
Upgraded document to Version 2.0.

7/9/2009

Version
3.0

Made extensive revisions due to intial
yearly document review.