
Multicast Address-Set Claim (MASC) Parameters

(last updated 2001-08-23)

Registries included below:
- 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

Note: 
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) 


Registry Name: MASC Message Types
Reference: [RFC2909]
Registration Procedures: IETF Consensus

Registry:
Value  Type                  Reference
-----  --------------------  ---------
1      OPEN                  [RFC2909]
2      UPDATE                [RFC2909]
3      NOTIFICATION          [RFC2909]
4      KEEPALIVE             [RFC2909]


Registry Name: MASC OPEN Message Optional Parameter Types
Reference: [RFC2909]
Registration Procedures: IETF Consensus 

Registry:
Value  Type         Reference
-----  -----------  ---------
There are no registrations at this time 


Registry Name: MASC UPDATE Message Attribute Types
Reference: [RFC2909]
Registration Procedures: IETF Consensus 

Registry:
Value    Type                                                  Reference
-------  ----------------------------------------------------  ---------
0        PREFIX_IN_USE (prefix is being used by the origin)    [RFC2909]

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 prefix)    [RFC2909]

4        PREFIX_MANAGED (parent is informing child of          [RFC2909]
         space available)

5        WITHDRAW (origin is withdrawing a previous claim)     [RFC2909]
         

Registry Name: MASC NOTIFICATION Message Error Codes and Subcodes
Reference: [RFC2909]
Registration Procedures: IETF consensus

Registry:
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]


Registry Name: Notification Error Subcodes
Reference: [RFC2909]
Registration Procedures: IETF consensus

Note:
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.


Sub-registry: Notification Message Header Error Subcodes (Value 1)
Reference: [RFC2909]
Registration Procedures: IETF consensus

Registry:
Subcode  Symbolic Name           O-bit  Reference
-------  ----------------------  -----  ---------
0        Unspecific              (MC)   [RFC2909]
1        Bad Message Length      (MC)   [RFC2909]
2        Bad Message Type        (CC)   [RFC2909]


Sub-registry: Notification OPEN Message Error Subcodes (Value 2)
Reference: [RFC2909]
Registration Procedures: IETF consensus

Registry:
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]
4-5      Unassigned
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]
11-12    Unassigned
13       Unrecognized Address Family      (MC)   [RFC2909]

Sub-registry: Notification UPDATE Message Error Subcodes (Value 3)
Reference: [RFC2909]
Registration Procedures: IETF consensus

Registry:
Subcode  Symbolic Name                      O-bit  Reference
-------  ---------------------------------  -----  ---------
0        Unspecific                         (MC)   [RFC2909]
1        Malformed Attribute List           (MC)   [RFC2909]
2        Unrecognized Required Attribute    (CC)   [RFC2909]
3-4      Unassigned
5        Attribute Length Error             (MC)   [RFC2909]
6-9      Unassigned
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]

Sub-registry: Notification Hold Timer Expired Subcodes (Value 4)
Reference: [RFC2909]
Registration Procedures: IETF consensus
Note: the O-bit is always zero

Registry:
Subcode  Symbolic Name       O-bit  Reference
-------  ------------------  -----  ---------
0        Unspecific          (MC)   [RFC2909]

Sub-registry: Notification Finite State Machine Error Subcodes (Value 5)
Reference: [RFC2909]
Registration Procedures: IETF consensus

Registry:
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]

Sub-registry: NOTIFICATION Subcodes (Value 6)
Reference: [RFC2909]
Registration Procedures: IETF consensus
Note: the O-bit is always zero

Registry:
Subcode  Symbolic Name       O-bit  Reference
-------  ------------------  -----  ---------
0        Unspecific          (MC)   [RFC2909]

Sub-registry: Notification Cease Subcodes (Value 7)
Reference: [RFC2909]
Registration Procedures: IETF consensus
Note: the O-bit is always zero

Registry:
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 2000-09)

[]


