ADDRESS RESOLUTION PROTOCOL PARAMETERS
ADDRESS RESOLUTION PROTOCOL PARAMETERS
(last updated 2002-02-05)
(last updated 2002-02-05)
The Address Resolution Protocol (ARP) specified in [
RFC826] has
The Address Resolution Protocol (ARP) specified in [
RFC826] has
several parameters. The assigned values for these parameters are
several parameters. The assigned values for these parameters are
listed here.
listed here.
REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES
REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES
The Reverse Address Resolution Protocol (RARP) specified in [
RFC903]
The Reverse Address Resolution Protocol (RARP) specified in [
RFC903]
uses the "Reverse" codes below.
uses the "Reverse" codes below.
DYNAMIC REVERSE ARP
DYNAMIC REVERSE ARP
The Dynamic Reverse Address Resolution Protocol (DRARP) uses the
The Dynamic Reverse Address Resolution Protocol (DRARP) uses the
"DRARP" codes below. For further information, contact: David Brownell
"DRARP" codes below. For further information, contact: David Brownell
(suneast!helium!db@Sun.COM).
(suneast!helium!db@Sun.COM).
INVERSE ADDRESS RESOULUTION PROTOCOL
INVERSE ADDRESS RESOULUTION PROTOCOL
The Inverse Address Resolution Protocol (IARP) specified in [
RFC1293]
The Inverse Address Resolution Protocol (IARP) specified in [
RFC1293]
uses the "InARP" codes below.
uses the "InARP" codes below.
Assignments:
Assignments:
Number Operation Code (op) References
Number Operation Code (op) References
------ -------------------------- ----------
------ -------------------------- ----------
1 REQUEST [
RFC826]
1 REQUEST [
RFC826]
2 REPLY [
RFC826]
2 REPLY [
RFC826]
3 request Reverse [
RFC903]
3 request Reverse [
RFC903]
4 reply Reverse [
RFC903]
4 reply Reverse [
RFC903]
5 DRARP-Request [David Brownell]
5 DRARP-Request [David Brownell]
6 DRARP-Reply [David Brownell]
6 DRARP-Reply [David Brownell]
7 DRARP-Error [David Brownell]
7 DRARP-Error [David Brownell]
8 InARP-Request [
RFC1293]
8 InARP-Request [
RFC1293]
9 InARP-Reply [
RFC1293]
9 InARP-Reply [
RFC1293]
10 ARP-NAK [
RFC1577]
10 ARP-NAK [
RFC1577]
11 MARS-Request [Armitage]
11 MARS-Request [Armitage]
12 MARS-Multi [Armitage]
12 MARS-Multi [Armitage]
13 MARS-MServ [Armitage]
13 MARS-MServ [Armitage]
14 MARS-Join [Armitage]
14 MARS-Join [Armitage]
15 MARS-Leave [Armitage]
15 MARS-Leave [Armitage]
16 MARS-NAK [Armitage]
16 MARS-NAK [Armitage]
17 MARS-Unserv [Armitage]
17 MARS-Unserv [Armitage]
18 MARS-SJoin [Armitage]
18 MARS-SJoin [Armitage]
19 MARS-SLeave [Armitage]
19 MARS-SLeave [Armitage]
20 MARS-Grouplist-Request [Armitage]
20 MARS-Grouplist-Request [Armitage]
21 MARS-Grouplist-Reply [Armitage]
21 MARS-Grouplist-Reply [Armitage]
22 MARS-Redirect-Map [Armitage]
22 MARS-Redirect-Map [Armitage]
23 MAPOS-UNARP [Maruyama]
23 MAPOS-UNARP [Maruyama]
Number Hardware Type (hrd) References
Number Hardware Type (hrd) References
------ ----------------------------------- ----------
------ ----------------------------------- ----------
1 Ethernet (10Mb) [JBP]
1 Ethernet (10Mb) [JBP]
2 Experimental Ethernet (3Mb) [JBP]
2 Experimental Ethernet (3Mb) [JBP]
3 Amateur Radio AX.25 [PXK]
3 Amateur Radio AX.25 [PXK]
4 Proteon ProNET Token Ring [Doria]
4 Proteon ProNET Token Ring [Doria]
5 Chaos [GXP]
5 Chaos [GXP]
6 IEEE 802 Networks [JBP]
6 IEEE 802 Networks [JBP]
7 ARCNET [JBP]
7 ARCNET [JBP]
8 Hyperchannel [JBP]
8 Hyperchannel [JBP]
9 Lanstar [TU]
9 Lanstar [TU]
10 Autonet Short Address [MXB1]
10 Autonet Short Address [MXB1]
11 LocalTalk [JKR1]
11 LocalTalk [JKR1]
12 LocalNet (IBM PCNet or SYTEK LocalNET) [JXM]
12 LocalNet (IBM PCNet or SYTEK LocalNET) [JXM]
13 Ultra link [RXD2]
13 Ultra link [RXD2]
14 SMDS [GXC1]
14 SMDS [GXC1]
15 Frame Relay [AGM]
15 Frame Relay [AGM]
16 Asynchronous Transmission Mode (ATM) [JXB2]
16 Asynchronous Transmission Mode (ATM) [JXB2]
17 HDLC [JBP]
17 HDLC [JBP]
18 Fibre Channel [Yakov Rekhter]
18 Fibre Channel [Yakov Rekhter]
19 Asynchronous Transmission Mode (ATM) [
RFC2225]
19 Asynchronous Transmission Mode (ATM) [
RFC2225]
20 Serial Line [JBP]
20 Serial Line [JBP]
21 Asynchronous Transmission Mode (ATM) [MXB1]
21 Asynchronous Transmission Mode (ATM) [MXB1]
22 MIL-STD-188-220 [Jensen]
22 MIL-STD-188-220 [Jensen]
23 Metricom [Stone]
23 Metricom [Stone]
24 IEEE 1394.1995 [Hattig]
24 IEEE 1394.1995 [Hattig]
25 MAPOS [Maruyama]
25 MAPOS [Maruyama]
26 Twinaxial [Pitts]
26 Twinaxial [Pitts]
27 EUI-64 [Fujisawa]
27 EUI-64 [Fujisawa]
28 HIPARP [JMP]
28 HIPARP [JMP]
29 IP and ARP over ISO 7816-3 [Guthery]
29 IP and ARP over ISO 7816-3 [Guthery]
30 ARPSec [Etienne]
30 ARPSec [Etienne]
31 IPsec tunnel [
RFCDHCP]
31 IPsec tunnel [
RFCDHCP]
32 InfiniBand (TM) [Kashyap]
32 InfiniBand (TM) [Kashyap]
Protocol Type (pro)
Protocol Type (pro)
Use the same codes as listed in the section called "Ethernet Numbers
Use the same codes as listed in the section called "Ethernet Numbers
of Interest" (all hardware types use this code set for the protocol
of Interest" (all hardware types use this code set for the protocol
type).
type).
REFERENCES
REFERENCES
[
RFC826] Plummer, D., "An Ethernet Address Resolution Protocol or
[
RFC826] Plummer, D., "An Ethernet Address Resolution Protocol or
Converting Network Protocol Addresses to 48-bit Ethernet
Converting Network Protocol Addresses to 48-bit Ethernet
Addresses for Transmission on Ethernet Hardware", STD 37, RFC
Addresses for Transmission on Ethernet Hardware", STD 37, RFC
826, MIT-LCS, November 1982.
826, MIT-LCS, November 1982.
[
RFC903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A
[
RFC903] Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A
Reverse Address Resolution Protocol", STD 38,
RFC 903,
Reverse Address Resolution Protocol", STD 38,
RFC 903,
Stanford University, June 1984.
Stanford University, June 1984.
[
RFC1293] Bradley, T., and C. Brown, "Inverse Address Resolution
[
RFC1293] Bradley, T., and C. Brown, "Inverse Address Resolution
Protocol",
RFC 1293, Wellfleet Communications, Inc.,
Protocol",
RFC 1293, Wellfleet Communications, Inc.,
January 1992.
January 1992.
[
RFC2225] Laubach, M., and J. Halpern, "Classical UP and ARP over
[
RFC2225] Laubach, M., and J. Halpern, "Classical UP and ARP over
ATM",
RFC 2225, Com21, Newbridge Networks, October 1997.
ATM",
RFC 2225, Com21, Newbridge Networks, October 1997.
[
RFCDHCP] B. Patel, B. Aboba, S. Kelly, and V. Gupta, "DHCPv4
[
RFCDHCP] B. Patel, B. Aboba, S. Kelly, and V. Gupta, "DHCPv4
Configuration of IPsec Tunnel Mode",
RFC XXXX, Month Year.
Configuration of IPsec Tunnel Mode",
RFC XXXX, Month Year.
PEOPLE
PEOPLE
[Armitage] Grenville Armitage, , April 1995.
[Armitage] Grenville Armitage, , April 1995.
[AGM] Andy Malis
[AGM] Andy Malis
[GXC1] George Clapp
[GXC1] George Clapp
[Doria] Avri Doria December 1994.
[Doria] Avri Doria December 1994.
[Etienne] Jerome Etienne, , June 2000.
[Etienne] Jerome Etienne, , June 2000.
[Fujisawa] Kenji Fujisawa , October 1998.
[Fujisawa] Kenji Fujisawa , October 1998.
[Guthery] Scott Guthery, , March 2000.
[Guthery] Scott Guthery, , March 2000.
[GXP] Gill Pratt
[GXP] Gill Pratt
[Jensen] Herb Jensen, , February 1995.
[Jensen] Herb Jensen, , February 1995.
[JBP] Jon Postel
[JBP] Jon Postel
[JKR1] Joyce K. Reynolds
[JKR1] Joyce K. Reynolds
[JMP] Jean-Michel Pittet, , November 1998.
[JMP] Jean-Michel Pittet, , November 1998.
[JXM] Joseph Murdock <---none--->
[JXM] Joseph Murdock <---none--->
[Kashyap] Vivek Kashyap, , February 2002.
[Kashyap] Vivek Kashyap, , February 2002.
[Hattig] Myron Hattig, , February 1997.
[Hattig] Myron Hattig, , February 1997.
[Maruyama] Mitsuru Maruyama, , March 1997.
[Maruyama] Mitsuru Maruyama, , March 1997.
[MXB1] Mike Burrows
[MXB1] Mike Burrows
[Pitts] Marion Pitts , May 1997.
[Pitts] Marion Pitts , May 1997.
[PXK] Philip Koch
[PXK] Philip Koch
[RXD2] Rajiv Dhingra
[RXD2] Rajiv Dhingra
[Stone] Jonathan Stone, , May 1996.
[Stone] Jonathan Stone, , May 1996.
[TU] Tom Unger
[TU] Tom Unger
[David Brownell]
[David Brownell]
[Mark Laubach]
[Mark Laubach]
[Yakov Rekhter]
[Yakov Rekhter]
[]
[]
AUTONOMOUS SYSTEM NUMBERS
AUTONOMOUS SYSTEM NUMBERS
(last updated 2002-12-03)
(last updated 2002-12-03)
The Autonomous System (AS) numbers are used by various routing
The Autonomous System (AS) numbers are used by various routing
protocols. AS numbers are allocated to the regional registries by the
protocols. AS numbers are allocated to the regional registries by the
IANA. These registries are the ARIN ,
IANA. These registries are the ARIN ,
RIPE-NCC , and the APNIC . AS Numbers
RIPE-NCC , and the APNIC . AS Numbers
can be obtained from the registry in your region. Listed below are
can be obtained from the registry in your region. Listed below are
the allocated blocks to the regional registries.
the allocated blocks to the regional registries.
Number Description
Number Description
-------------- -------------------------------------------------------------
-------------- -------------------------------------------------------------
0 Reserved - May be use to identify non-routed networks
0 Reserved - May be use to identify non-routed networks
1 - 1876 Allocated by ARIN
1 - 1876 Allocated by ARIN
1877 - 1901 Allocated by RIPE NCC
1877 - 1901 Allocated by RIPE NCC
1902 - 2042 Allocated by ARIN
1902 - 2042 Allocated by ARIN
2043 Allocated by RIPE NCC
2043 Allocated by RIPE NCC
2044 - 2046 Allocated by ARIN
2044 - 2046 Allocated by ARIN
2047 Allocated by RIPE NCC
2047 Allocated by RIPE NCC
2048 - 2106 Allocated by ARIN
2048 - 2106 Allocated by ARIN
2107 - 2136 Allocated by RIPE NCC
2107 - 2136 Allocated by RIPE NCC
2137 - 2584 Allocated by ARIN
2137 - 2584 Allocated by ARIN
2585 - 2614 Allocated by RIPE NCC
2585 - 2614 Allocated by RIPE NCC
2615 - 2772 Allocated by ARIN
2615 - 2772 Allocated by ARIN
2773 - 2822 Allocated by RIPE NCC
2773 - 2822 Allocated by RIPE NCC
2823 - 2829 Allocated by ARIN
2823 - 2829 Allocated by ARIN
2830 - 2879 Allocated by RIPE NCC
2830 - 2879 Allocated by RIPE NCC
2880 - 3153 Allocated by ARIN
2880 - 3153 Allocated by ARIN
3154 - 3353 Allocated by RIPE NCC
3154 - 3353 Allocated by RIPE NCC
3354 - 4607 Allocated by ARIN
3354 - 4607 Allocated by ARIN
4608 - 4864 Allocated by APNIC
4608 - 4864 Allocated by APNIC
4865 - 5376 Allocated by ARIN
4865 - 5376 Allocated by ARIN
5377 - 5631 Allocated by RIPE NCC
5377 - 5631 Allocated by RIPE NCC
5632 - 6655 Allocated by ARIN
5632 - 6655 Allocated by ARIN
6656 - 6911 Allocated by RIPE NCC
6656 - 6911 Allocated by RIPE NCC
6912 - 7466 Allocated by ARIN
6912 - 7466 Allocated by ARIN
7467 - 7722 Allocated by APNIC
7467 - 7722 Allocated by APNIC
7723 - 8191 Allocated by ARIN
7723 - 8191 Allocated by ARIN
8192 - 9215 Allocated by RIPE NCC
8192 - 9215 Allocated by RIPE NCC
9216 - 10239 Allocated by APNIC
9216 - 10239 Allocated by APNIC
10240 - 11263 Allocated by ARIN
10240 - 11263 Allocated by ARIN
11264 - 12287 Allocated by ARIN
11264 - 12287 Allocated by ARIN
12288 - 13311 Allocated by RIPE NCC
12288 - 13311 Allocated by RIPE NCC
13312 - 14335 Allocated by ARIN
13312 - 14335 Allocated by ARIN
14336 - 15359 Allocated by ARIN
14336 - 15359 Allocated by ARIN
15360 - 16383 Allocated by RIPE NCC
15360 - 16383 Allocated by RIPE NCC
16384 - 17407 Allocated by ARIN
16384 - 17407 Allocated by ARIN
17408 - 18431 Allocated by APNIC
17408 - 18431 Allocated by APNIC
18432 - 19455 Allocated by ARIN
18432 - 19455 Allocated by ARIN
19456 - 20479 Allocated by ARIN
19456 - 20479 Allocated by ARIN
20480 - 21503 Allocated by RIPE NCC
20480 - 21503 Allocated by RIPE NCC
21504 - 22527 Allocated by ARIN
21504 - 22527 Allocated by ARIN
22528 - 23551 Allocated by ARIN
22528 - 23551 Allocated by ARIN
23552 - 24575 Allocated by APNIC
23552 - 24575 Allocated by APNIC
24576 - 25599 Allocated by RIPE NCC
24576 - 25599 Allocated by RIPE NCC
25600 - 26623 Allocated by ARIN (March 2002)
25600 - 26623 Allocated by ARIN (March 2002)
26624 - 27647 Allocated by ARIN (September 2002)
26624 - 27647 Allocated by ARIN (September 2002)
27648 - 28671 Allocated by LACNIC (November 2002)
27648 - 28671 Allocated by LACNIC (November 2002)
28672 - 29695 Allocated by RIPE NCC (December 2002)
28672 - 29695 Allocated by RIPE NCC (December 2002)
29696 - 32767 Held by the IANA
29696 - 32767 Held by the IANA
32768 - 64511 Reserved by the IANA
32768 - 64511 Reserved by the IANA
64512 - 65534 Designated for private use (Allocated to the IANA)
64512 - 65534 Designated for private use (Allocated to the IANA)
65535 Reserved
65535 Reserved
Specially designated Autonomous System Numbers:
Specially designated Autonomous System Numbers:
23456 AS_TRAN [draft-ietf-idr-as4bytes-04.txt]
23456 AS_TRAN [draft-ietf-idr-as4bytes-04.txt]
[]
[]
BEEP Parameters per [
RFC3080]
BEEP Parameters per [
RFC3080]
-BEEP Profiles
-BEEP Profiles
-BEEP Templates
-BEEP Templates
(last updated 2002-08-09)
(last updated 2002-08-09)
BEEP Profiles
BEEP Profiles
-------------
-------------
The IANA maintains a registry of standards-track BEEP
The IANA maintains a registry of standards-track BEEP
profiles (as specified in Appendix B of
RFC 3080).
profiles (as specified in Appendix B of
RFC 3080).
To add a BEEP Profile:
To add a BEEP Profile:
Section 5.1 of
RFC 3080 contains a registration template
Section 5.1 of
RFC 3080 contains a registration template
that should be completed, approved by the IESG, and then
that should be completed, approved by the IESG, and then
placed in this registry.
placed in this registry.
As a courtesy to developers of non-standards track BEEP
As a courtesy to developers of non-standards track BEEP
profiles, the mailing list beepwg@lists.beepcore.org may be
profiles, the mailing list beepwg@lists.beepcore.org may be
used to solicit commentary.
used to solicit commentary.
Standards-Track BEEP Profiles Reference
Standards-Track BEEP Profiles Reference
-------------------------------------------- ---------
-------------------------------------------- ---------
http://iana.org/beep/TLS [
RFC3080]
http://iana.org/beep/TLS [
RFC3080]
http://iana.org/beep/SASL/mechanism [
RFC3080]
http://iana.org/beep/SASL/mechanism [
RFC3080]
http://iana.org/beep/SYSLOG/RAW [
RFC3195]
http://iana.org/beep/SYSLOG/RAW [
RFC3195]
http://iana.org/beep/SYSLOG/COOKED [
RFC3195]
http://iana.org/beep/SYSLOG/COOKED [
RFC3195]
http://iana.org/beep/APEX [
RFC3340]
http://iana.org/beep/APEX [
RFC3340]
http://iana.org/beep/soap [
RFC3288]
http://iana.org/beep/soap [
RFC3288]
BEEP Features
BEEP Features
-------------
-------------
The IANA maintains a registry of standards-track BEEP
The IANA maintains a registry of standards-track BEEP
features (as specified in Appendix B of
RFC 3080).
features (as specified in Appendix B of
RFC 3080).
To add a BEEP Feature:
To add a BEEP Feature:
Section 5.2 of
RFC 3080 contains a registration template
Section 5.2 of
RFC 3080 contains a registration template
that should be completed, approved by the IESG, and then
that should be completed, approved by the IESG, and then
placed in this registry.
placed in this registry.
As a courtesy to developers of non-standards track BEEP
As a courtesy to developers of non-standards track BEEP
features, the mailing list beepwg@lists.beepcore.org may be
features, the mailing list beepwg@lists.beepcore.org may be
used to solicit commentary.
used to solicit commentary.
Standards-Track BEEP Features Reference
Standards-Track BEEP Features Reference
--------------------------------------------- ---------
--------------------------------------------- ---------
None listed at this time
None listed at this time
References
References
----------
----------
[
RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core",
[
RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core",
RFC 3080, February 2001.
RFC 3080, February 2001.
[
RFC3195] D. New and M. Rose, "Reliable Delivery for syslog",
[
RFC3195] D. New and M. Rose, "Reliable Delivery for syslog",
RFC 3195, November 2001.
RFC 3195, November 2001.
[
RFC3288] E. O'Tuathail and M. Rose, "Using SOAP in BEEP",
[
RFC3288] E. O'Tuathail and M. Rose, "Using SOAP in BEEP",
RFC 3288, June 2002.
RFC 3288, June 2002.
[
RFC3340] M. Rose, G. Klyne, and D. Crocker, "The Application
[
RFC3340] M. Rose, G. Klyne, and D. Crocker, "The Application
Exchange Core",
RFC 3340, July 2002.
Exchange Core",
RFC 3340, July 2002.
(created 2000-01-30)
(created 2000-01-30)
[]
[]
BORDER GATEWAY PROTOCOL
BORDER GATEWAY PROTOCOL
(last updated 2001-08-17)
(last updated 2001-08-17)
The Border Gateway Protocol (BGP) has Attribute Types as listed here.
The Border Gateway Protocol (BGP) has Attribute Types as listed here.
Value Code Reference
Value Code Reference
----- --------------------------------- ---------
----- --------------------------------- ---------
1 ORIGIN [
RFC1771]
1 ORIGIN [
RFC1771]
2 AS_PATH [
RFC1771]
2 AS_PATH [
RFC1771]
3 NEXT_HOP [
RFC1771]
3 NEXT_HOP [
RFC1771]
4 MULTI_EXIT_DISC [
RFC1771]
4 MULTI_EXIT_DISC [
RFC1771]
5 LOCAL_PREF [
RFC1771]
5 LOCAL_PREF [
RFC1771]
6 ATOMIC_AGGREGATE [
RFC1771]
6 ATOMIC_AGGREGATE [
RFC1771]
7 AGGREGATOR [
RFC1771]
7 AGGREGATOR [
RFC1771]
8 COMMUNITY [
RFC1997]
8 COMMUNITY [
RFC1997]
9 ORIGINATOR_ID [
RFC1998]
9 ORIGINATOR_ID [
RFC1998]
10 CLUSTER_LIST [
RFC1998]
10 CLUSTER_LIST [
RFC1998]
11 DPA [Chen]
11 DPA [Chen]
12 ADVERTISER [
RFC1863]
12 ADVERTISER [
RFC1863]
13 RCID_PATH / CLUSTER_ID [
RFC1863]
13 RCID_PATH / CLUSTER_ID [
RFC1863]
14 MP_REACH_NLRI [
RFC2283]
14 MP_REACH_NLRI [
RFC2283]
15 MP_UNREACH_NLRI [
RFC2283]
15 MP_UNREACH_NLRI [
RFC2283]
16 EXTENDED COMMUNITIES [Rosen]
16 EXTENDED COMMUNITIES [Rosen]
17 NEW_AS_PATH [E.Chen]
17 NEW_AS_PATH [E.Chen]
18 NEW_AGGREGATOR [E.Chen]
18 NEW_AGGREGATOR [E.Chen]
19-254 Unassigned
19-254 Unassigned
255 reserved for development
255 reserved for development
References
References
[
RFC1771] Rekhter, Y., and Li, T., "A Border Gateway Protocol 4
[
RFC1771] Rekhter, Y., and Li, T., "A Border Gateway Protocol 4
(BGP-4)",
RFC 1771, March 1995.
(BGP-4)",
RFC 1771, March 1995.
[
RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
[
RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Attribute",
RFC 1997, August 1996.
Attribute",
RFC 1997, August 1996.
[
RFC1998] Bates, T., Chandra, R, "BGP Route Reflection An alternative
[
RFC1998] Bates, T., Chandra, R, "BGP Route Reflection An alternative
to full mesh IBGP",
RFC 1998, June 1996.
to full mesh IBGP",
RFC 1998, June 1996.
[
RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full
[
RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full
mesh routing",
RFC 1863, October 1995.
mesh routing",
RFC 1863, October 1995.
[
RFC2283] Bates, T., et al., "Multiprotocol Extensions for BGP-4", RFC
[
RFC2283] Bates, T., et al., "Multiprotocol Extensions for BGP-4", RFC
2283, February 1998.
2283, February 1998.
People
People
------
------
[Chen] Chen, E., Bates, T., "Destination Preference Attribute for
[Chen] Chen, E., Bates, T., "Destination Preference Attribute for
BGP", Work in progress, March 1996.
BGP", Work in progress, March 1996.
[E.Chen] Enke Chen, , August 2001
[E.Chen] Enke Chen, , August 2001
[Rosen] Eric Rosen , March 1999.
[Rosen] Eric Rosen , March 1999.
(draft-ramachandra-bgp-ext-communities-00.txt)
(draft-ramachandra-bgp-ext-communities-00.txt)
[]
[]
Capability Codes - Per [
RFC3392]
Capability Codes - Per [
RFC3392]
(last updated 2001-11-12)
(last updated 2001-11-12)
As specified in this document, the Capability optional parameter
As specified in this document, the Capability optional parameter
contains the Capability Code field. Capability Code value 0 is
contains the Capability Code field. Capability Code value 0 is
reserved. Capability Code values 1 through 63 are to be assigned by
reserved. Capability Code values 1 through 63 are to be assigned by
IANA using the "IETF Consensus" policy defined in
RFC2434. Capability
IANA using the "IETF Consensus" policy defined in
RFC2434. Capability
Code values 64 through 127 are to be assigned by IANA, using the
Code values 64 through 127 are to be assigned by IANA, using the
"First Come First Served" policy defined in
RFC2434. Capability
"First Come First Served" policy defined in
RFC2434. Capability
Code values 128 through 255 are vendor-specific, and values in this
Code values 128 through 255 are vendor-specific, and values in this
range are not to be assigned by IANA.
range are not to be assigned by IANA.
Capability Codes
Capability Codes
Value Description Reference
Value Description Reference
------- ------------------------------------------ ---------
------- ------------------------------------------ ---------
0 Reserved [
RFC3392]
0 Reserved [
RFC3392]
1 Multiprotocol Extensions for BGP-4 [
RFC2858]
1 Multiprotocol Extensions for BGP-4 [
RFC2858]
2 Route Refresh Capability for BGP-4 [
RFC2918]
2 Route Refresh Capability for BGP-4 [
RFC2918]
3 Cooperative Route Filtering Capability [Rekhter]
3 Cooperative Route Filtering Capability [Rekhter]
4 Multiple routes to a destination capability [
RFC3107]
4 Multiple routes to a destination capability [
RFC3107]
5-63 Unassigned
5-63 Unassigned
64 Graceful Restart Capability [Chen]
64 Graceful Restart Capability [Chen]
65 Support for 4-octet AS number capabiltiy [Chen]
65 Support for 4-octet AS number capabiltiy [Chen]
66 Support for Dynamic Capability [Chen]
66 Support for Dynamic Capability [Chen]
67 -127 Unassigned
67 -127 Unassigned
128-255 Vendor Specific
128-255 Vendor Specific
References
References
----------
----------
[
RFC2858] Bates, T., Y. Rekhter, R. Chandra, and D. Katz,
[
RFC2858] Bates, T., Y. Rekhter, R. Chandra, and D. Katz,
"Multiprotocol Extensions for BGP-4",
RFC 2858, June 2000.
"Multiprotocol Extensions for BGP-4",
RFC 2858, June 2000.
[
RFC2918] Chen, E., "Route Refresh Capability for BGP-4",
RFC 2918,
[
RFC2918] Chen, E., "Route Refresh Capability for BGP-4",
RFC 2918,
September 2000.
September 2000.
[
RFC3107] Y. Rekhter and E. Rosen, "Carrying Label Information in
[
RFC3107] Y. Rekhter and E. Rosen, "Carrying Label Information in
BGP-4",
RFC 3107, May 2001.
BGP-4",
RFC 3107, May 2001.
[
RFC3392] R. Chandra and J. Scudder, "Capabilities Advertisement
[
RFC3392] R. Chandra and J. Scudder, "Capabilities Advertisement
with BGP-4",
RFC 3392, November 2002.
with BGP-4",
RFC 3392, November 2002.
People
People
------
------
[Chandra] Ravi Chandra, , May 2000
[Chandra] Ravi Chandra, , May 2000
[Chen] Enke Chen, , October 2000, August 2001,
[Chen] Enke Chen, , October 2000, August 2001,
November 2001.
November 2001.
[Rekhter] Yakov Rekhter, , October 2000.
[Rekhter] Yakov Rekhter, , October 2000.
[]
[]
BOOTP AND DHCP PARAMETERS
BOOTP AND DHCP PARAMETERS
(last updated 2002-11-05)
(last updated 2002-11-05)
The Bootstrap Protocol (BOOTP) [
RFC951] describes an IP/UDP bootstrap
The Bootstrap Protocol (BOOTP) [
RFC951] describes an IP/UDP bootstrap
protocol (BOOTP) which allows a diskless client machine to discover
protocol (BOOTP) which allows a diskless client machine to discover
its own IP address, the address of a server host, and the name of a
its own IP address, the address of a server host, and the name of a
file to be loaded into memory and executed. The Dynamic Host
file to be loaded into memory and executed. The Dynamic Host
Configuration Protocol (DHCP) [
RFC2131] provides a framework for
Configuration Protocol (DHCP) [
RFC2131] provides a framework for
automatic configuration of IP hosts. The "DHCP Options and BOOTP
automatic configuration of IP hosts. The "DHCP Options and BOOTP
Vendor Information Extensions" [
RFC2132] describes the additions to
Vendor Information Extensions" [
RFC2132] describes the additions to
the Bootstrap Protocol (BOOTP) which can also be used as options with
the Bootstrap Protocol (BOOTP) which can also be used as options with
the Dynamic Host Configuration Protocol (DHCP).
the Dynamic Host Configuration Protocol (DHCP).
BCP 29,
RFC 2489, "Procedure for Defining New DHCP Options" [
RFC2489],
BCP 29,
RFC 2489, "Procedure for Defining New DHCP Options" [
RFC2489],
describes the procedure for defining new DHCP options. This new
describes the procedure for defining new DHCP options. This new
procedure provides guidance to IANA in the assignment of new option
procedure provides guidance to IANA in the assignment of new option
codes. The DHCP option number space (1-254) is split into two parts.
codes. The DHCP option number space (1-254) is split into two parts.
The site-specific options (128-254) are defined as "Private Use" and
The site-specific options (128-254) are defined as "Private Use" and
require no review by the DHC WG. The public options (1-127) are
require no review by the DHC WG. The public options (1-127) are
defined as "Specification Required" and new options must be reviewed
defined as "Specification Required" and new options must be reviewed
prior to assignment of an option number by IANA.
prior to assignment of an option number by IANA.
BOOTP Vendor Extensions and DHCP Options are listed below:
BOOTP Vendor Extensions and DHCP Options are listed below:
Data
Data
Tag Name Length Meaning
Tag Name Length Meaning
--- ---- ------ -------
--- ---- ------ -------
0 Pad 0 None [
RFC2132]
0 Pad 0 None [
RFC2132]
1 Subnet Mask 4 Subnet Mask Value [
RFC2132]
1 Subnet Mask 4 Subnet Mask Value [
RFC2132]
2 Time Offset 4 Time Offset in [
RFC2132]
2 Time Offset 4 Time Offset in [
RFC2132]
Seconds from UTC
Seconds from UTC
3 Router N N/4 Router addresses [
RFC2132]
3 Router N N/4 Router addresses [
RFC2132]
4 Time Server N N/4 Timeserver addresses [
RFC2132]
4 Time Server N N/4 Timeserver addresses [
RFC2132]
5 Name Server N N/4 IEN-116 Server addresses [
RFC2132]
5 Name Server N N/4 IEN-116 Server addresses [
RFC2132]
6 Domain Server N N/4 DNS Server addresses [
RFC2132]
6 Domain Server N N/4 DNS Server addresses [
RFC2132]
7 Log Server N N/4 Logging Server addresses [
RFC2132]
7 Log Server N N/4 Logging Server addresses [
RFC2132]
8 Quotes Server N N/4 Quotes Server addresses [
RFC2132]
8 Quotes Server N N/4 Quotes Server addresses [
RFC2132]
9 LPR Server N N/4 Printer Server addresses [
RFC2132]
9 LPR Server N N/4 Printer Server addresses [
RFC2132]
10 Impress Server N N/4 Impress Server addresses [
RFC2132]
10 Impress Server N N/4 Impress Server addresses [
RFC2132]
11 RLP Server N N/4 RLP Server addresses [
RFC2132]
11 RLP Server N N/4 RLP Server addresses [
RFC2132]
12 Hostname N Hostname string [
RFC2132]
12 Hostname N Hostname string [
RFC2132]
13 Boot File Size 2 Size of boot file in 512 byte [
RFC2132]
13 Boot File Size 2 Size of boot file in 512 byte [
RFC2132]
chunks
chunks
14 Merit Dump File N Client to dump and name [
RFC2132]
14 Merit Dump File N Client to dump and name [
RFC2132]
the file to dump it to
the file to dump it to
15 Domain Name N The DNS domain name of the [
RFC2132]
15 Domain Name N The DNS domain name of the [
RFC2132]
client
client
16 Swap Server N Swap Server addeess [
RFC2132]
16 Swap Server N Swap Server addeess [
RFC2132]
17 Root Path N Path name for root disk [
RFC2132]
17 Root Path N Path name for root disk [
RFC2132]
18 Extension File N Path name for more BOOTP info [
RFC2132]
18 Extension File N Path name for more BOOTP info [
RFC2132]
19 Forward On/Off 1 Enable/Disable IP Forwarding [
RFC2132]
19 Forward On/Off 1 Enable/Disable IP Forwarding [
RFC2132]
20 SrcRte On/Off 1 Enable/Disable Source Routing [
RFC2132]
20 SrcRte On/Off 1 Enable/Disable Source Routing [
RFC2132]
21 Policy Filter N Routing Policy Filters [
RFC2132]
21 Policy Filter N Routing Policy Filters [
RFC2132]
22 Max DG Assembly 2 Max Datagram Reassembly Size [
RFC2132]
22 Max DG Assembly 2 Max Datagram Reassembly Size [
RFC2132]
23 Default IP TTL 1 Default IP Time to Live [
RFC2132]
23 Default IP TTL 1 Default IP Time to Live [
RFC2132]
24 MTU Timeout 4 Path MTU Aging Timeout [
RFC2132]
24 MTU Timeout 4 Path MTU Aging Timeout [
RFC2132]
25 MTU Plateau N Path MTU Plateau Table [
RFC2132]
25 MTU Plateau N Path MTU Plateau Table [
RFC2132]
26 MTU Interface 2 Interface MTU Size [
RFC2132]
26 MTU Interface 2 Interface MTU Size [
RFC2132]
27 MTU Subnet 1 All Subnets are Local [
RFC2132]
27 MTU Subnet 1 All Subnets are Local [
RFC2132]
28 Broadcast Address 4 Broadcast Address [
RFC2132]
28 Broadcast Address 4 Broadcast Address [
RFC2132]
29 Mask Discovery 1 Perform Mask Discovery [
RFC2132]
29 Mask Discovery 1 Perform Mask Discovery [
RFC2132]
30 Mask Supplier 1 Provide Mask to Others [
RFC2132]
30 Mask Supplier 1 Provide Mask to Others [
RFC2132]
31 Router Discovery 1 Perform Router Discovery [
RFC2132]
31 Router Discovery 1 Perform Router Discovery [
RFC2132]
32 Router Request 4 Router Solicitation Address [
RFC2132]
32 Router Request 4 Router Solicitation Address [
RFC2132]
33 Static Route N Static Routing Table [
RFC2132]
33 Static Route N Static Routing Table [
RFC2132]
34 Trailers 1 Trailer Encapsulation [
RFC2132]
34 Trailers 1 Trailer Encapsulation [
RFC2132]
35 ARP Timeout 4 ARP Cache Timeout [
RFC2132]
35 ARP Timeout 4 ARP Cache Timeout [
RFC2132]
36 Ethernet 1 Ethernet Encapsulation [
RFC2132]
36 Ethernet 1 Ethernet Encapsulation [
RFC2132]
37 Default TCP TTL 1 Default TCP Time to Live [
RFC2132]
37 Default TCP TTL 1 Default TCP Time to Live [
RFC2132]
38 Keepalive Time 4 TCP Keepalive Interval [
RFC2132]
38 Keepalive Time 4 TCP Keepalive Interval [
RFC2132]
39 Keepalive Data 1 TCP Keepalive Garbage [
RFC2132]
39 Keepalive Data 1 TCP Keepalive Garbage [
RFC2132]
40 NIS Domain N NIS Domain Name [
RFC2132]
40 NIS Domain N NIS Domain Name [
RFC2132]
41 NIS Servers N NIS Server Addresses [
RFC2132]
41 NIS Servers N NIS Server Addresses [
RFC2132]
42 NTP Servers N NTP Server Addresses [
RFC2132]
42 NTP Servers N NTP Server Addresses [
RFC2132]
43 Vendor Specific N Vendor Specific Information [
RFC2132]
43 Vendor Specific N Vendor Specific Information [
RFC2132]
44 NETBIOS Name Srv N NETBIOS Name Servers [
RFC2132]
44 NETBIOS Name Srv N NETBIOS Name Servers [
RFC2132]
45 NETBIOS Dist Srv N NETBIOS Datagram Distribution [
RFC2132]
45 NETBIOS Dist Srv N NETBIOS Datagram Distribution [
RFC2132]
46 NETBIOS Node Type 1 NETBIOS Node Type [
RFC2132]
46 NETBIOS Node Type 1 NETBIOS Node Type [
RFC2132]
47 NETBIOS Scope N NETBIOS Scope [
RFC2132]
47 NETBIOS Scope N NETBIOS Scope [
RFC2132]
48 X Window Font N X Window Font Server [
RFC2132]
48 X Window Font N X Window Font Server [
RFC2132]
49 X Window Manager N X Window Display Manager [
RFC2132]
49 X Window Manager N X Window Display Manager [
RFC2132]
50 Address Request 4 Requested IP Address [
RFC2132]
50 Address Request 4 Requested IP Address [
RFC2132]
51 Address Time 4 IP Address Lease Time [
RFC2132]
51 Address Time 4 IP Address Lease Time [
RFC2132]
52 Overload 1 Overload "sname" or "file" [
RFC2132]
52 Overload 1 Overload "sname" or "file" [
RFC2132]
53 DHCP Msg Type 1 DHCP Message Type [
RFC2132]
53 DHCP Msg Type 1 DHCP Message Type [
RFC2132]
54 DHCP Server Id 4 DHCP Server Identification [
RFC2132]
54 DHCP Server Id 4 DHCP Server Identification [
RFC2132]
55 Parameter List N Parameter Request List [
RFC2132]
55 Parameter List N Parameter Request List [
RFC2132]
56 DHCP Message N DHCP Error Message [
RFC2132]
56 DHCP Message N DHCP Error Message [
RFC2132]
57 DHCP Max Msg Size 2 DHCP Maximum Message Size [
RFC2132]
57 DHCP Max Msg Size 2 DHCP Maximum Message Size [
RFC2132]
58 Renewal Time 4 DHCP Renewal (T1) Time [
RFC2132]
58 Renewal Time 4 DHCP Renewal (T1) Time [
RFC2132]
59 Rebinding Time 4 DHCP Rebinding (T2) Time [
RFC2132]
59 Rebinding Time 4 DHCP Rebinding (T2) Time [
RFC2132]
60 Class Id N Class Identifier [
RFC2132]
60 Class Id N Class Identifier [
RFC2132]
61 Client Id N Client Identifier [
RFC2132]
61 Client Id N Client Identifier [
RFC2132]
62 Netware/IP Domain N Netware/IP Domain Name [
RFC2242]
62 Netware/IP Domain N Netware/IP Domain Name [
RFC2242]
63 Netware/IP Option N Netware/IP sub Options [
RFC2242]
63 Netware/IP Option N Netware/IP sub Options [
RFC2242]
64 NIS-Domain-Name N NIS+ v3 Client Domain Name [
RFC2132]
64 NIS-Domain-Name N NIS+ v3 Client Domain Name [
RFC2132]
65 NIS-Server-Addr N NIS+ v3 Server Addresses [
RFC2132]
65 NIS-Server-Addr N NIS+ v3 Server Addresses [
RFC2132]
66 Server-Name N TFTP Server Name [
RFC2132]
66 Server-Name N TFTP Server Name [
RFC2132]
67 Bootfile-Name N Boot File Name [
RFC2132]
67 Bootfile-Name N Boot File Name [
RFC2132]
68 Home-Agent-Addrs N Home Agent Addresses [
RFC2132]
68 Home-Agent-Addrs N Home Agent Addresses [
RFC2132]
69 SMTP-Server N Simple Mail Server Addresses [
RFC2132]
69 SMTP-Server N Simple Mail Server Addresses [
RFC2132]
70 POP3-Server N Post Office Server Addresses [
RFC2132]
70 POP3-Server N Post Office Server Addresses [
RFC2132]
71 NNTP-Server N Network News Server Addresses [
RFC2132]
71 NNTP-Server N Network News Server Addresses [
RFC2132]
72 WWW-Server N WWW Server Addresses [
RFC2132]
72 WWW-Server N WWW Server Addresses [
RFC2132]
73 Finger-Server N Finger Server Addresses [
RFC2132]
73 Finger-Server N Finger Server Addresses [
RFC2132]
74 IRC-Server N Chat Server Addresses [
RFC2132]
74 IRC-Server N Chat Server Addresses [
RFC2132]
75 StreetTalk-Server N StreetTalk Server Addresses [
RFC2132]
75 StreetTalk-Server N StreetTalk Server Addresses [
RFC2132]
76 STDA-Server N ST Directory Assist. Addresses[
RFC2132]
76 STDA-Server N ST Directory Assist. Addresses[
RFC2132]
77 User-Class N User Class Information [
RFC3004]
77 User-Class N User Class Information [
RFC3004]
78 Directory Agent N directory agent information [
RFC2610]
78 Directory Agent N directory agent information [
RFC2610]
79 Service Scope N service location agent scope [
RFC2610]
79 Service Scope N service location agent scope [
RFC2610]
80 Naming Authority N naming authority
80 Naming Authority N naming authority
81 Client FQDN N Fully Qualified Domain Name [DRAFT-IETF-DHC-FQDN-OPTION]
81 Client FQDN N Fully Qualified Domain Name [DRAFT-IETF-DHC-FQDN-OPTION]
82 Relay Agent Information N Relay Agent Information [
RFC3046]
82 Relay Agent Information N Relay Agent Information [
RFC3046]
83 Agent Remote ID N Agent Remote ID
83 Agent Remote ID N Agent Remote ID
84 Agent Subnet Mask N Agent Subnet Mask
84 Agent Subnet Mask N Agent Subnet Mask
85 NDS Servers N Novell Directory Services [
RFC2241]
85 NDS Servers N Novell Directory Services [
RFC2241]
86 NDS Tree Name N Novell Directory Services [
RFC2241]
86 NDS Tree Name N Novell Directory Services [
RFC2241]
87 NDS Context N Novell Directory Services [
RFC2241]
87 NDS Context N Novell Directory Services [
RFC2241]
88 IEEE 1003.1 POSIX N IEEE 1003.1 POSIX Timezone
88 IEEE 1003.1 POSIX N IEEE 1003.1 POSIX Timezone
89 FQDN N Fully Qualified Domain Name
89 FQDN N Fully Qualified Domain Name
90 Authentication N Authentication [
RFC3118]
90 Authentication N Authentication [
RFC3118]
91 Vines TCP/IP N Vines TCP/IP Server Option
91 Vines TCP/IP N Vines TCP/IP Server Option
92 Server Selection N Server Selection Option
92 Server Selection N Server Selection Option
93 Client System N Client System Architecture
93 Client System N Client System Architecture
94 Client NDI N Client Network Device Interface
94 Client NDI N Client Network Device Interface
95 LDAP N Lightweight Directory Access Protocol
95 LDAP N Lightweight Directory Access Protocol
96 IPv6 Transitions N IPv6 Transitions
96 IPv6 Transitions N IPv6 Transitions
97 UUID/GUID N UUID/GUID-based Client Identifier
97 UUID/GUID N UUID/GUID-based Client Identifier
98 User-Auth N Open Group's User Authentication [
RFC2485]
98 User-Auth N Open Group's User Authentication [
RFC2485]
99 Unassigned
99 Unassigned
100 Printer Name N Printer Name
100 Printer Name N Printer Name
101 MDHCP N DHCP multicast address
101 MDHCP N DHCP multicast address
102-107 REMOVED/Unassigned
102-107 REMOVED/Unassigned
108 Swap Path N Swap Path Option
108 Swap Path N Swap Path Option
109 Unassigned
109 Unassigned
110 IPX Compatability N IPX Compatability
110 IPX Compatability N IPX Compatability
111 Unassigned
111 Unassigned
112 Netinfo Address N NetInfo Parent Server Address
112 Netinfo Address N NetInfo Parent Server Address
113 Netinfo Tag N NetInfo Parent Server Tag
113 Netinfo Tag N NetInfo Parent Server Tag
114 URL N URL
114 URL N URL
115 Failover N DHCP Failover Protocol
115 Failover N DHCP Failover Protocol
116 Auto-Config N DHCP Auto-Configuration [
RFC2563]
116 Auto-Config N DHCP Auto-Configuration [
RFC2563]
117 Name Service Search N Name Service Search [
RFC2937]
117 Name Service Search N Name Service Search [
RFC2937]
118 Subnet Selection Option 4 Subnet Selection Option [
RFC3011]
118 Subnet Selection Option 4 Subnet Selection Option [
RFC3011]
119 Domain Search N DNS domain serach list [
RFC3396]
119 Domain Search N DNS domain serach list [
RFC3396]
120 SIP Servers DHCP Option N SIP Servers DHCP Option [
RFC3361]
120 SIP Servers DHCP Option N SIP Servers DHCP Option [
RFC3361]
121 Classless Static Route N Classless Static Route Option [
RFCCSR7]
121 Classless Static Route N Classless Static Route Option [
RFCCSR7]
Option
Option
122-125 Unassigned
122-125 Unassigned
126 Extension N Extension
126 Extension N Extension
127 Extension N Extension
127 Extension N Extension
128-254 Private Use
128-254 Private Use
255 End 0 None [
RFC2132]
255 End 0 None [
RFC2132]
DHCP Message Type 53 Values
DHCP Message Type 53 Values
Value Message Type Reference
Value Message Type Reference
----- ------------ ---------
----- ------------ ---------
1 DHCPDISCOVER [
RFC2132]
1 DHCPDISCOVER [
RFC2132]
2 DHCPOFFER [
RFC2132]
2 DHCPOFFER [
RFC2132]
3 DHCPREQUEST [
RFC2132]
3 DHCPREQUEST [
RFC2132]
4 DHCPDECLINE [
RFC2132]
4 DHCPDECLINE [
RFC2132]
5 DHCPACK [
RFC2132]
5 DHCPACK [
RFC2132]
6 DHCPNAK [
RFC2132]
6 DHCPNAK [
RFC2132]
7 DHCPRELEASE [
RFC2132]
7 DHCPRELEASE [
RFC2132]
8 DHCPINFORM [
RFC2132]
8 DHCPINFORM [
RFC2132]
9 DHCPFORCERENEW [
RFC3203]
9 DHCPFORCERENEW [
RFC3203]
Network/IP Option Type 63 Sub-Option Codes
Network/IP Option Type 63 Sub-Option Codes
Value Message Type Reference
Value Message Type Reference
----- ------------ ---------
----- ------------ ---------
1 NWIP_DOES_NOT_EXIST [
RFC2242]
1 NWIP_DOES_NOT_EXIST [
RFC2242]
2 NWIP_EXIST_IN_OPTIONS_AREA [
RFC2242]
2 NWIP_EXIST_IN_OPTIONS_AREA [
RFC2242]
3 NWIP_EXIST_IN_SNAME_FILE [
RFC2242]
3 NWIP_EXIST_IN_SNAME_FILE [
RFC2242]
4 NWIP_EXIST_BUT_TOO_BIG [
RFC2242]
4 NWIP_EXIST_BUT_TOO_BIG [
RFC2242]
5 NSQ_BROADCAST [
RFC2242]
5 NSQ_BROADCAST [
RFC2242]
6 PREFERRED_DSS [
RFC2242]
6 PREFERRED_DSS [
RFC2242]
7 NEAREST_NWIP_SERVER [
RFC2242]
7 NEAREST_NWIP_SERVER [
RFC2242]
8 AUTORETRIES [
RFC2242]
8 AUTORETRIES [
RFC2242]
9 AUTORETRY_SECS [
RFC2242]
9 AUTORETRY_SECS [
RFC2242]
10 NWIP_1_1 [
RFC2242]
10 NWIP_1_1 [
RFC2242]
11 PRIMARY_DSS [
RFC2242]
11 PRIMARY_DSS [
RFC2242]
DHCP Agent Sub-Option Codes per [
RFC3046]
DHCP Agent Sub-Option Codes per [
RFC3046]
Code Sub-Option Description Reference
Code Sub-Option Description Reference
----- ----------------------- ---------
----- ----------------------- ---------
1 Agent Circuit ID Sub-option [
RFC3046]
1 Agent Circuit ID Sub-option [
RFC3046]
2 Agent Remote ID Sub-option [
RFC3046]
2 Agent Remote ID Sub-option [
RFC3046]
3 Sub-option 3 is reserved and should [Droms]
3 Sub-option 3 is reserved and should [Droms]
not be assigned at this time;
not be assigned at this time;
proprietary and incompatible usages
proprietary and incompatible usages
of this sub-option value have been
of this sub-option value have been
seen limited deployment.
seen limited deployment.
4 DOCSIS Device Class Suboption [
RFC3256]
4 DOCSIS Device Class Suboption [
RFC3256]
REFERENCES
REFERENCES
----------
----------
[
RFC951] Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)",
[
RFC951] Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)",
RFC-951, Stanford and SUN Microsytems, September 1985.
RFC-951, Stanford and SUN Microsytems, September 1985.
[
RFC2131] Droms, R., "Dynamic Host Configuration Protocol", Bucknell
[
RFC2131] Droms, R., "Dynamic Host Configuration Protocol", Bucknell
University, March 1997.
University, March 1997.
[
RFC2132] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor
[
RFC2132] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", Silicon Graphics, Inc., Bucknell University,
Extensions", Silicon Graphics, Inc., Bucknell University,
March 1997.
March 1997.
[
RFC2241] D. Provan, "DHCP Options for Novell Directory Services",
[
RFC2241] D. Provan, "DHCP Options for Novell Directory Services",
RFC 2241, November 1997.
RFC 2241, November 1997.
[
RFC2242] R. Droms and K. Fong, "NetWare/IP Domain Name and
[
RFC2242] R. Droms and K. Fong, "NetWare/IP Domain Name and
Information",
RFC 2242, November 1997.
Information",
RFC 2242, November 1997.
[
RFC2485] S. Drach, "DHCP Option for The Open Group's User Authentication
[
RFC2485] S. Drach, "DHCP Option for The Open Group's User Authentication
Protocol",
RFC 2485, January 1999.
Protocol",
RFC 2485, January 1999.
[
RFC2489] Droms, R., "Procedure for Defining New DHCP Options",
[
RFC2489] Droms, R., "Procedure for Defining New DHCP Options",
BCP 29,
RFC 2489, January 1999.
BCP 29,
RFC 2489, January 1999.
[
RFC2563] R. Troll, "DHCP Option to Disable Stateless Auto-Configuration
[
RFC2563] R. Troll, "DHCP Option to Disable Stateless Auto-Configuration
in IPv4 Clients,
RFC 2563, May 1999.
in IPv4 Clients,
RFC 2563, May 1999.
[
RFC2610] C. Perkins and E. Guttman, "DHCP Options for Service Location
[
RFC2610] C. Perkins and E. Guttman, "DHCP Options for Service Location
Protocol",
RFC 2610, June 1999.
Protocol",
RFC 2610, June 1999.
[
RFC2937] C. Smith, "The Name Service Search Option for DHCP",
RFC 2937,
[
RFC2937] C. Smith, "The Name Service Search Option for DHCP",
RFC 2937,
September 2000.
September 2000.
[
RFC3004] G. Stump, R. Droms, Y. Gu, R. Vyaghrapuri, A. Demirtjis,
[
RFC3004] G. Stump, R. Droms, Y. Gu, R. Vyaghrapuri, A. Demirtjis,
B. Beser, and J. Privat, "The User Class Option for DHCP",
B. Beser, and J. Privat, "The User Class Option for DHCP",
RFC 3004, November 2000.
RFC 3004, November 2000.
[
RFC3011] G. Waters, "The IPv4 Subnet Selection Option for DHCP",
[
RFC3011] G. Waters, "The IPv4 Subnet Selection Option for DHCP",
RFC 3011, November 2000.
RFC 3011, November 2000.
[
RFC3046] M. Patrick, "DHCP Relay Agent Information Option",
[
RFC3046] M. Patrick, "DHCP Relay Agent Information Option",
RFC 3046, January 2001.
RFC 3046, January 2001.
[
RFC3118] R. Droms and W. Arbaugh, "Authentication for DHCP Messages",
[
RFC3118] R. Droms and W. Arbaugh, "Authentication for DHCP Messages",
RFC 3118, June 2001.
RFC 3118, June 2001.
[
RFC3203] Y. T'Jones, C. Hublet, and P. De Schrijver, "DHCP
[
RFC3203] Y. T'Jones, C. Hublet, and P. De Schrijver, "DHCP
Reonfigure Extension",
RFC 3203, December 2001.
Reonfigure Extension",
RFC 3203, December 2001.
[
RFC3256] D. Jones and R. Woundy, "The DOCSIS Device Class DHCP
[
RFC3256] D. Jones and R. Woundy, "The DOCSIS Device Class DHCP
Relay Agent Information Sub-option",
RFC 3256,
Relay Agent Information Sub-option",
RFC 3256,
April 2002.
April 2002.
[
RFC3361] H. Schulzrinne, "DHCPv4 Option for SIP Servers",
RFC 3361,
[
RFC3361] H. Schulzrinne, "DHCPv4 Option for SIP Servers",
RFC 3361,
August 2002.
August 2002.
[
RFC3396] B. Aboba and S. Cheshire, "DHCP Domain Search Option",
[
RFC3396] B. Aboba and S. Cheshire, "DHCP Domain Search Option",
RFC 3396, November 2002.
RFC 3396, November 2002.
[
RFCCSR7] T. Lemon, S. Cheshire, and B. Volz, "The Classless Static
[
RFCCSR7] T. Lemon, S. Cheshire, and B. Volz, "The Classless Static
Route Option for DHCPv4",
RFC XXXX, Month Year.
Route Option for DHCPv4",
RFC XXXX, Month Year.
PEOPLE
PEOPLE
------
------
[Droms] Ralph Droms, , January 2001.
[Droms] Ralph Droms, , January 2001.
[]
[]
Building Blocks per [
RFC3048]
Building Blocks per [
RFC3048]
Example template for registration
Example template for registration
Building Block Name:
Building Block Name:
Version Number:
Version Number:
Description:
Description:
Specification:
Specification:
Contact:
Contact:
Building Block Registry
Building Block Registry
-----------------------
-----------------------
There are no registrations at this time.
There are no registrations at this time.
References
References
----------
----------
[
RFC3048] B. Whetten, L. Vicisano, R. Kermode, M. Handley, S. Floyd,
[
RFC3048] B. Whetten, L. Vicisano, R. Kermode, M. Handley, S. Floyd,
and M. Luby, "Reliable Multicast Transport Building Blocks
and M. Luby, "Reliable Multicast Transport Building Blocks
for One-to-Many Bulk-data Transfer",
RFC XXXX, Month-Year.
for One-to-Many Bulk-data Transfer",
RFC XXXX, Month-Year.
(created 2001-01)
(created 2001-01)
[]
[]
|
