File: madcap-parameters

package info (click to toggle)
doc-iana 2001.08-1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 8,176 kB
  • ctags: 954
  • sloc: perl: 1,057; makefile: 83; sh: 27
file content (100 lines) | stat: -rw-r--r-- 3,733 bytes parent folder | download
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
MADCAP-PARAMETERS

The Multicast Address Dynamic Client Allocation Protocol (MADCAP)
specified in [RFC2730] has several parameters. New values may only be
defined by IETF Consensus, as described in [RFC2434]. Basically, this
means that they are defined by RFCs approved by the IESG.

The current assigned values for these parameters are listed here.

MADCAP MESSAGE TYPES

Value   Name                                       References
-----   ----                                       ----------
  1     DISCOVER                                   [RFC2730]
  2     OFFER                                      [RFC2730]
  3     REQUEST                                    [RFC2730]
  4     RENEW                                      [RFC2730]
  5     ACK                                        [RFC2730]
  6     NAK                                        [RFC2730]
  7     RELEASE                                    [RFC2730]
  8     GETINFO                                    [RFC2730]

MADCAP OPTIONS

Value   Name                                       References
-----   ----                                       ----------
  0     End                                        [RFC2730]
  1     Lease Time                                 [RFC2730]
  2     Server Identifier                          [RFC2730]
  3     Lease Identifier                           [RFC2730]
  4     Multicast Scope                            [RFC2730]
  5     Option Request List                        [RFC2730]
  6     Start Time                                 [RFC2730]
  7     Number of Addresses Requested              [RFC2730]
  8     Requested Language                         [RFC2730]
  9     Multicast Scope List                       [RFC2730]
 10     List of Address Ranges                     [RFC2730]
 11     Current Time                               [RFC2730]
 12     Feature List                               [RFC2730]
 13     Retry Time                                 [RFC2730]
 14     Minimum Lease Time                         [RFC2730]
 15     Maximum Start Time                         [RFC2730]
 16     Error                                      [RFC2730]
 17     Multicast Scope Nesting State		   [RFC2907]	

MADCAP LEASE IDENTIFIER TYPES

Value    Name                                      References
-----    ----                                      ----------
  0      Random Lease Identifier                   [RFC2730]
  1      Address-Specific Lease Identifier         [RFC2730]

MADCAP FEATURE CODES

Value    Name                                      References
-----    ----                                      ----------
  0      Server Mobility                           [RFC2730]
  1      Retry After                               [RFC2730]
  2      Shared Lease Identifier                   [RFC2730]

MADCAP ERROR CODES

Value     Name                                     References
-----     ----                                     ----------
  0       Valid Request Could Not Be Completed     [RFC2730]
  1       Invalid Request                          [RFC2730]
  2       Excessive Clock Skew                     [RFC2730]
  3       Required Feature Not Supported           [RFC2730]
1024-2047 Reserved for Experimental Use            [RFC2730]


REFERENCES
----------

[RFC2434] Alvestrand, H. and T. Narten, "Guidelines for Writing an
          IANA Considerations Section in RFCs", RFC 2434, October 1998.

[RFC2730] Hanna, S., Patel, B., and M. Shah, "Multicast Address
          Dynamic Client Allocation Protocol (MADCAP)", RFC 2730, December
          1999.

[RFC2907] Kermode, R., "MADCAP Multicast Scope Nesting State Option",
          RFC 2907, September 2000. 

PEOPLE
------


[]