draft-ietf-dhc-multopt-01.txt   draft-ietf-dhc-multopt-02.txt 
Network Working Group Baiju V. Patel Network Working Group Baiju V. Patel
INTERNET DRAFT Intel Corporation INTERNET DRAFT Intel Corporation
Munil Shah Munil Shah
Microsoft Corporation Microsoft Corporation
March 1997 March 1997
Multicast address allocation extensions options Multicast address allocation extensions options
<draft-ietf-dhc-multopt-01.txt> <draft-ietf-dhc-multopt-02.txt>
Status of this memo Status of this memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 36 skipping to change at page 1, line 36
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
1. Abstract 1. Abstract
This document describes host configuration options that may be used This document describes host configuration options that may be used
by multicast address allocation protocols[3]. The options include by multicast address allocation protocols[3]. The options include
critical information such as the IP address (unicast or multicast) critical information such as the multicast address
of the multicast address allocation server(s) and a list of of the multicast address allocation server(s) and a list of
multicast scopes supported by respective servers. These options are multicast scopes supported by respective servers. These options are
designed to work with the extensions to DHCP [1] servers to support designed to work with the extensions to DHCP [1] servers to support
multicast address allocation (described in a separate draft), multicast address allocation (described in a separate draft),
however, their use may not be limited to the above protocol. however, their use may not be limited to the above protocol.
2 Requirements 2 Requirements
Throughout this document, the words that are used to define the Throughout this document, the words that are used to define the
significance of particular requirements are capitalized. These words significance of particular requirements are capitalized. These
are: words are:
o "MUST" o "MUST"
This word or the adjective "REQUIRED" means that the This word or the adjective "REQUIRED" means that the
item is an absolute requirement of this specification. item is an absolute requirement of this specification.
o "MUST NOT" o "MUST NOT"
This phrase means that the item is an absolute prohibition This phrase means that the item is an absolute prohibition
of this specification. of this specification.
skipping to change at page 2, line 47 skipping to change at page 2, line 47
o "DHCP client" o "DHCP client"
A DHCP client is an Internet host using DHCP to obtain A DHCP client is an Internet host using DHCP to obtain
configuration parameters such as a network address. configuration parameters such as a network address.
o "DHCP server" o "DHCP server"
A DHCP server is an Internet host that returns configuration A DHCP server is an Internet host that returns configuration
parameters to DHCP clients. parameters to DHCP clients.
o "BOOTP relay agent" o "MDHCP client"
A BOOTP relay agent or relay agent is an Internet host or router A MDHCP client is a DHCP client that supports MDHCP extensions.
that passes DHCP messages between DHCP clients and DHCP servers.
DHCP is designed to use the same relay agent behavior as
specified in the BOOTP protocol specification.
o "binding" o "MDHCP server"
A binding is a collection of configuration parameters, including A MDHCP server is a DHCP server that supports MDHCP extensions.
at least an IP address, associated with or "bound to" a DHCP
client. Bindings are managed by DHCP servers.
4 Multicast Scope List Option 4 Multicast Address Allocation Configuration Options
Any client attempting to request a multicast address must know the Any client attempting to request a multicast address must know the
address to which the server is listening to (this address may be multicast group address to which the server is listening to and a
unicast or multicast address), and a list of multicast scopes list of multicast scopes supported by the multicast address servers.
supported by the multicast address servers. This option is The following two options are specifically designed to provide the
specifically designed to provide the multicast address server multicast address server address and the scope list that can
address and the scope list that can specifically be used by the specifically be used by the protocol described in [3], however, its
protocol described in [3], however, its use is not limited to the use is not limited to the protocol described in [3].
protocol described in [3].
4.1 Multicast Group Address of MDHCP Servers.
This option is used DHCP servers to provide the multicast group
address of the MDHCP servers. The MDHCP client can obtain this
parameter as part of the normal DHCP protocol message exchange or
separately via DHCPINFORM.
Code Len Multicast Address
+-----+-----+-----+-----+-----+-----+
| TBD | 4 | i1 | i2 | i3 | i4 |
+-----+-----+-----+-----+-----+-----+
The code for this option is TBD and the length is 4.
4.2 Multicast Scople List Option.
The format of the multicast scope list option is: The format of the multicast scope list option is:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Code Len IP Address Count List
| code (1 byte) | length (1byte)| +-----+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 107 | n | i1 | i2 | i3 | i4 | N | l1 | | ln |
| IP address (4 bytes) | +-----+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TTL (1 byte) | N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Scope list
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where IP address is the address of the MDHCP server, to its best Where IP address is the address of the MDHCP server, to its best
knowledge, reachable from the client via unicast or multicast. knowledge, reachable from the client via unicast.
packets. The IP address may be a unicast or multicast address and The scope list a list of N tuples, where each tuple is of
the multicast address server must process the packets addressed to
this address. The TTL value is the maximum time to leave value to
be used for the packets sent to the IP address specified in this
option. The scope list a list of N tuples, where each tuple is of
the form, the form,
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Scope ID ( 4 Bytes ) TTL Desc Scope Description.
| scope ID(4 byte) | Scope len (1 bute) | Scope description | Len
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-----+-----+-----+-----+-----+-----+-----+-...-+-----+
| ID1 | ID2 | ID3 | ID4 | T | n | d1 | | dn |
+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
where scope ID is a unique identifier to designate the scope, scope where scope ID is a unique identifier to designate the scope,
TTL is the multicast TTL value for the multicast addresses of
the scope, scope
description is a string describing the scope (need not be null description is a string describing the scope (need not be null
terminated) and scope len is the length of scope description. terminated) and scope len is the length of scope description.
Scope id is numeric representation of the scope and is used by the Scope id is numeric representation of the scope and is used by the
client to indicate a multicast scope to the server. In order to client to indicate a multicast scope to the server. In order to
keep the usage of scope id consistent in the MBONE, this draft keep the usage of scope id consistent in the MBONE, this draft
SHOULD be coordinated with [3] reserve a scope id for each SHOULD be coordinated with [3] reserve a scope id for each
multicast range in [3]. The scope id with its MSB(most significant multicast range in [3]. The scope id with its MSB(most significant
bit) of 1 should be used for administratively scoped multicast bit) of 1 should be used for administratively scoped multicast
address range. And the scope id with its MSB of 0 should be used to address range. And the scope id with its MSB of 0 should be used to
represent other pre-defined internet scopes. represent other pre-defined internet scopes.
The code for this option is 107. The code for this option is 107.
Example: Example:
The multicast address allocation servers are listening to multicast The IP address of the MDHCP server is 10.1.1.1. There are two
address 239.1.1.1. The maximum allowed value for the TTL for this scopes supported by the multicast address allocation server:
address is 16. There are two scopes supported by the multicast 1) Inside the abcd.com, 2) world. Then this option will be used as:
address allocation server: 1) Inside the abcd.com, 2) world. Then
this option will be used as:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| code (1 byte) | 30 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 239.1.1.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 16 | 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 |16| Inside abcd.com |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 |5 |world |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Instead of specifying a multicast address, the option may also Code Len IP Address Count
specify a unicast address of the multicast address server. In above +-----+-----+-----+-----+-----+-----+-----+
example, if the address of the multicast address server (see [3]) | 107 | 32 | 10 | 1 | 1 | 1 | 2 |
was 10.1.1.1, the option will be used as: +-----+-----+-----+-----+-----+-----+-----+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Scope ID TTL Len Desc
| code (1 byte) | 30 | +--+--+--+--+---+---+--+--+-...-+--+--+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 |10 |16 | Inside abcd.com |
| 10.1.1.1 | +--+--+--+--+---+---+--+--+-...-+--+--+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 2 |16 |5 | world |
| 16 | 2 | +--+--+--+--+---+---+--+--+-...-+--+--+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0 |16|"Inside abcd.com" |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 1 |5|"world" |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4 References 4 References
[1] Droms, R., "Dynamic Host Configuration Protocol", RFC1541, [1] Droms, R., "Dynamic Host Configuration Protocol", RFC1541,
October 1993 October 1993
[2] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor [2] Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", RFC 1533, Lachman Technology, Inc., Bucknell Extensions", RFC 1533, Lachman Technology, Inc., Bucknell
University, October 1993. University, October 1993.
skipping to change at page 5, line 20 skipping to change at page 5, line 20
Hillsboro, OR 97124 Hillsboro, OR 97124
Phone: 503 264 2422 Phone: 503 264 2422
EMail: baiju@ibeam.intel.com EMail: baiju@ibeam.intel.com
Munil Shah Munil Shah
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone:206 703 3924 Phone:425 703 3924
Email:munils@microsoft.com Email:munils@microsoft.com
This document will expire on Sept, 1997 This document will expire on April, 1998

 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/