1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
MASC Parameters -- [RFC2909]
-MASC Message Types
-MASC OPEN Message Optional Parameter Types
-MASC UPDATE Message Attribute Types
-MASC UPDATE Message Optional Parameter Types
-MASC NOTIFICATION Message Error Codes and Subcodes
RFC 2909 defines several number spaces. For all of these number
spaces, certain values are defined in RFC 2909. New values may
only be defined by IETF Consensus, as described in [RFC2434].
(New values are defined by the RFCs approved by the IESG)
MASC Message Types
Value Type Reference
----- ------ ---------
1 - OPEN [RFC2909]
2 - UPDATE [RFC2909]
3 - NOTIFICATION [RFC2909]
4 - KEEPALIVE [RFC2909]
MASC OPEN Message Optional Parameter Types
Value Type Reference
----- ------ ---------
MASC UPDATE Message Attribute Types
Value Type Reference
----- ------ ---------
0 = PREFIX_IN_USE (prefix is being used by the [RFC2909]
origin)
1 = CLAIM_DENIED (the claim is refused (probably [RFC2909]
by the origin's parent domain))
2 = CLAIM_TO_EXPAND (origin is trying to expand [RFC2909]
the size of an existing prefix)
3 = NEW_CLAIM (origin is trying to claim a new [RFC2909]
prefix)
4 = PREFIX_MANAGED (parent is informing child of [RFC2909]
space available)
5 = WITHDRAW (origin is withdrawing a previous [RFC2909]
claim)
MASC NOTIFICATION Message Error Codes and Subcodes
Error Code Symbolic Name Reference
---------- ------------- ---------
1 Message Header Error [RFC2909]
2 OPEN Message Error [RFC2909]
3 UPDATE Message Error [RFC2909]
4 Hold Timer Expired [RFC2909]
5 Finite State Machine Error [RFC2909]
6 NOTIFICATION Message Error [RFC2909]
7 Cease [RFC2909]
Notification Error Subcodes
---------------------------
This 1-octet unsigned integer provides more specific information
about the nature of the reported error. Each Error Code may
have one or more Error Subcodes associated with it. If no
appropriate Error Subcode is defined, then a zero (Unspecific)
value is used for the Error Subcode field, and the O-bit must be
zero (i.e. the connection will be closed). The notation used in
the error description below is: MC = Must Close connection =O-bit
is zero; CC = Can Close connection = O-bit might be zero.
Message Header Error subcodes:
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
1 - Bad Message Length (MC) [RFC2909]
2 - Bad Message Type (CC) [RFC2909]
OPEN Message Error subcodes:
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
1 - Unsupported Version Number (MC) [RFC2909]
2 - Bad Peer Domain ID (MC) [RFC2909]
3 - Bad Peer MASC Node ID (MC) [RFC2909]
6 - Unacceptable Hold Time (MC) [RFC2909]
7 - Invalid Parent Configuration (MC) [RFC2909]
8 - Inconsistent Role (MC) [RFC2909]
9 - Bad Parent Domain ID (MC) [RFC2909]
10 - No Common Parent (MC) [RFC2909]
13 - Unrecognized Address Family (MC) [RFC2909]
UPDATE Message Error subcodes:
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
1 - Malformed Attribute List (MC) [RFC2909]
2 - Unrecognized Required Attribute (CC) [RFC2909]
5 - Attribute Length Error (MC) [RFC2909]
10 - Invalid Address field (CC) [RFC2909]
11 - Invalid Mask field (CC) [RFC2909]
12 - Non-Contiguous Mask (CC) [RFC2909]
13 - Unrecognized Address Family (MC) [RFC2909]
14 - Claim Type Error (CC) [RFC2909]
15 - Origin Domain ID Error (CC) [RFC2909]
16 - Origin Node ID Error (CC) [RFC2909]
17 - Claim Lifetime Too Short (CC) [RFC2909]
18 - Claim Lifetime Too Long (CC) [RFC2909]
19 - Claim Timestamp Too Old (CC) [RFC2909]
20 - Claim Timestamp Too New (CC) [RFC2909]
21 - Claim Prefix Size Too Small (CC) [RFC2909]
22 - Claim Prefix Size Too Large (CC) [RFC2909]
23 - Illegal Origin Role Error (CC) [RFC2909]
24 - No Appropriate Parent Prefix (CC) [RFC2909]
25 - No Appropriate Child Prefix (CC) [RFC2909]
26 - No Appropriate Internal Prefix (CC) [RFC2909]
27 - No Appropriate Sibling Prefix (CC) [RFC2909]
28 - Claim Holdtime Too Short (CC) [RFC2909]
29 - Claim Holdtime Too Long (CC) [RFC2909]
Hold Timer Expired subcodes (the O-bit is always zero):
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
Finite State Machine Error subcodes:
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
1 - Open/Close MASC Connection FSM Error (MC) [RFC2909]
2 - Unexpected Message Type FSM Error (MC) [RFC2909]
Cease subcodes (the O-bit is always zero):
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
NOTIFICATION subcodes (the O-bit is always zero):
Subcode Symbolic Name O-bit Reference
------- ------------- ----- ---------
0 - Unspecific (MC) [RFC2909]
References
----------
[RFC2909] Radoslavov, P., D. Estrin, R. Govindan, M. Handley,
S. Kumar, and D. Thaler, "The Multicast Address-Set
Claim (MASC) Protocol", RFC 2909, September 2000.
(created 09/00)
[]
|
