Multicast Address-Set Claim (MASC) Parameters
MASC Message Types
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
MASC OPEN Message Optional Parameter Types
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Value |
Type |
Reference |
| No registrations at this time. |
MASC UPDATE Message Attribute Types
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Value |
Type |
Reference |
| 0 |
PREFIX_IN_USE (prefix is being used by the origin) |
RFC 2909 |
| 1 |
CLAIM_DENIED (the claim is refused (probably
by the origin's parent domain)) |
RFC 2909 |
| 2 |
CLAIM_TO_EXPAND (origin is trying to expand
the size of an existing prefix) |
RFC 2909 |
| 3 |
NEW_CLAIM (origin is trying to claim a new prefix) |
RFC 2909 |
| 4 |
PREFIX_MANAGED (parent is informing child of
space available) |
RFC 2909 |
| 5 |
WITHDRAW (origin is withdrawing a previous claim) |
RFC 2909 |
| 6-127 |
Unassigned |
|
MASC UPDATE Message Optional Parameter Types (128-255)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
Types 128-255 are reserved for "optional" attributes.
| Value |
Type |
Reference |
| No registrations at this time. |
MASC NOTIFICATION Message Error Codes and Subcodes
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
Notification Error Subcodes
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
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.
Notification Message Header Error Subcodes (Value 1)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
| 1 |
Bad Message Length |
(MC) |
RFC 2909 |
| 2 |
Bad Message Type |
(CC) |
RFC 2909 |
Notification OPEN Message Error Subcodes (Value 2)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
| 1 |
Unsupported Version Number |
(MC) |
RFC 2909 |
| 2 |
Bad Peer Domain ID |
(MC) |
RFC 2909 |
| 3 |
Bad Peer MASC Node ID |
(MC) |
RFC 2909 |
| 4-5 |
Unassigned |
|
|
| 6 |
Unacceptable Hold Time |
(MC) |
RFC 2909 |
| 7 |
Invalid Parent Configuration |
(MC) |
RFC 2909 |
| 8 |
Inconsistent Role |
(MC) |
RFC 2909 |
| 9 |
Bad Parent Domain ID |
(MC) |
RFC 2909 |
| 10 |
No Common Parent |
(MC) |
RFC 2909 |
| 11-12 |
Unassigned |
|
|
| 13 |
Unrecognized Address Family |
(MC) |
RFC 2909 |
Notification UPDATE Message Error Subcodes (Value 3)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
| 1 |
Malformed Attribute List |
(MC) |
RFC 2909 |
| 2 |
Unrecognized Required Attribute |
(CC) |
RFC 2909 |
| 3-4 |
Unassigned |
|
|
| 5 |
Attribute Length Error |
(MC) |
RFC 2909 |
| 6-9 |
Unassigned |
|
|
| 10 |
Invalid Address field |
(CC) |
RFC 2909 |
| 11 |
Invalid Mask field |
(CC) |
RFC 2909 |
| 12 |
Non-Contiguous Mask |
(CC) |
RFC 2909 |
| 13 |
Unrecognized Address Family |
(MC) |
RFC 2909 |
| 14 |
Claim Type Error |
(CC) |
RFC 2909 |
| 15 |
Origin Domain ID Error |
(CC) |
RFC 2909 |
| 16 |
Origin Node ID Error |
(CC) |
RFC 2909 |
| 17 |
Claim Lifetime Too Short |
(CC) |
RFC 2909 |
| 18 |
Claim Lifetime Too Long |
(CC) |
RFC 2909 |
| 19 |
Claim Timestamp Too Old |
(CC) |
RFC 2909 |
| 20 |
Claim Timestamp Too New |
(CC) |
RFC 2909 |
| 21 |
Claim Prefix Size Too Small |
(CC) |
RFC 2909 |
| 22 |
Claim Prefix Size Too Large |
(CC) |
RFC 2909 |
| 23 |
Illegal Origin Role Error |
(CC) |
RFC 2909 |
| 24 |
No Appropriate Parent Prefix |
(CC) |
RFC 2909 |
| 25 |
No Appropriate Child Prefix |
(CC) |
RFC 2909 |
| 26 |
No Appropriate Internal Prefix |
(CC) |
RFC 2909 |
| 27 |
No Appropriate Sibling Prefix |
(CC) |
RFC 2909 |
| 28 |
Claim Holdtime Too Short |
(CC) |
RFC 2909 |
| 29 |
Claim Holdtime Too Long |
(CC) |
RFC 2909 |
Notification Hold Timer Expired Subcodes (Value 4)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
the O-bit is always zero
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
Notification Finite State Machine Error Subcodes (Value 5)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
| 1 |
Open/Close MASC Connection FSM Error |
(MC) |
RFC 2909 |
| 2 |
Unexpected Message Type FSM Error |
(MC) |
RFC 2909 |
NOTIFICATION Subcodes (Value 6)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
the O-bit is always zero
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |
Notification Cease Subcodes (Value 7)
- RFC 2909: The Multicast Address-Set Claim (MASC) Protocol
the O-bit is always zero
| Subcode |
Symbolic Name |
O-bit |
Reference |
| 0 |
Unspecific |
(MC) |
RFC 2909 |