draft-ietf-dhc-multopt-02.txt   draft-ietf-dhc-multopt-03.txt 
Network Working Group Baiju V. Patel DHC working group Baiju V. Patel, Intel Corp.
INTERNET DRAFT Intel Corporation Internet Draft Munil Shah, Microsoft Corp.
August 1998 Stephen R. Hanna, Sun Microsystems, Inc.
Munil Shah Expires: February 1999 draft-ietf-dhc-multopt-03.txt
Microsoft Corporation
March 1997
Multicast address allocation extensions options Multicast Address Allocation Configuration Options
<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
and may be updated, replaced, or obsoleted by other documents at any months. Internet Drafts may be updated, replaced, or obsoleted by
time. It is inappropriate to use Internet-Drafts as reference other documents at any time. It is not appropriate to use Internet
material or to cite them other than as ``work in progress.'' Drafts as reference material or to cite them other than as a "working
draft" or "work in progress".
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 ds.internic.net, nic.nordu.net, ftp.isi.edu, or
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au.
ftp.isi.edu (US West Coast).
1. Abstract
This document describes host configuration options that may be used
by multicast address allocation protocols[3]. The options include
critical information such as the multicast address
of the multicast address allocation server(s) and a list of
multicast scopes supported by respective servers. These options are
designed to work with the extensions to DHCP [1] servers to support
multicast address allocation (described in a separate draft),
however, their use may not be limited to the above protocol.
2 Requirements
Throughout this document, the words that are used to define the
significance of particular requirements are capitalized. These
words are:
o "MUST"
This word or the adjective "REQUIRED" means that the
item is an absolute requirement of this specification.
o "MUST NOT"
This phrase means that the item is an absolute prohibition
of this specification.
o "SHOULD"
This word or the adjective "RECOMMENDED" means that there
may exist valid reasons in particular circumstances to ignore
this item, but the full implications should be understood and
the case carefully weighed before choosing a different course.
o "SHOULD NOT" A revised version of this draft document will be submitted to the RFC
editor as a Proposed Standard for the Internet Community. Discussion
and suggestions for improvement are requested. This document will
expire before February 1999. Distribution of this draft is unlimited.
This phrase means that there may exist valid reasons in Abstract
particular circumstances when the listed behavior is acceptable
or even useful, but the full implications should be understood
and the case carefully weighed before implementing any behavior
described with this label.
o "MAY" This document describes DHCP options that may be used to provide
access to Multicast Address Allocation servers, such as MDHCP
servers.
This word or the adjective "OPTIONAL" means that this item is 1. Terminology
truly optional. One vendor may choose to include the item
because a particular marketplace requires it or because it
enhances the product, for example; another vendor may omit the
same item.
3 Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and"OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
This document uses the following terms: This document uses the following terms:
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 "MDHCP client" o "MDHCP client"
A MDHCP client is a DHCP client that supports MDHCP extensions. An MDHCP client is an Internet host requesting multicast
address allocation services via MDHCP.
o "MDHCP server" o "MDHCP server"
A MDHCP server is a DHCP server that supports MDHCP extensions. An MDHCP server is an Internet host providing multicast
address allocation services via MDHCP.
4 Multicast Address Allocation Configuration Options
Any client attempting to request a multicast address must know the
multicast group address to which the server is listening to and a
list of multicast scopes supported by the multicast address servers.
The following two options are specifically designed to provide the
multicast address server address and the scope list that can
specifically be used by the protocol described in [3], however, its
use is not limited to the 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:
Code Len IP Address Count List
+-----+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
| 107 | n | i1 | i2 | i3 | i4 | N | l1 | | ln |
+-----+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
Where IP address is the address of the MDHCP server, to its best
knowledge, reachable from the client via unicast.
The scope list a list of N tuples, where each tuple is of
the form,
Scope ID ( 4 Bytes ) TTL Desc Scope Description. 2. Multicast Address Allocation Configuration Options
Len
+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
| ID1 | ID2 | ID3 | ID4 | T | n | d1 | | dn |
+-----+-----+-----+-----+-----+-----+-----+-...-+-----+
where scope ID is a unique identifier to designate the scope, The MDHCP protocol [3] allows hosts (known as MDHCP clients) to
TTL is the multicast TTL value for the multicast addresses of request multicast address allocation services from multicast address
the scope, scope allocation servers (known as MDHCP servers). One way that MDHCP
description is a string describing the scope (need not be null clients communicate with MDHCP servers is by sending multicast
terminated) and scope len is the length of scope description. messages to an MDHCP Server Multicast Address.
Scope id is numeric representation of the scope and is used by the This document defines a DHCP option (as described in [1] and [2])
client to indicate a multicast scope to the server. In order to that may be used to configure MDHCP clients with an appropriate MDHCP
keep the usage of scope id consistent in the MBONE, this draft Server Multicast Address and TTL.
SHOULD be coordinated with [3] reserve a scope id for each
multicast range in [3]. The scope id with its MSB(most significant
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
represent other pre-defined internet scopes.
The code for this option is 107. 2.1. MDHCP Server Multicast Address option
Example: The MDHCP Server Multicast Address option specifies a multicast
address and TTL that MDHCP clients SHOULD use to contact MDHCP
servers.
The IP address of the MDHCP server is 10.1.1.1. There are two A DHCP client can obtain this parameter as part of the normal DHCP
scopes supported by the multicast address allocation server: protocol message exchange or separately via DHCPINFORM.
1) Inside the abcd.com, 2) world. Then this option will be used as:
Code Len IP Address Count Code Len Multicast Address TTL
+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+
| 107 | 32 | 10 | 1 | 1 | 1 | 2 | | TBD | 5 | i1 | i2 | i3 | i4 | ttl |
+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+
Scope ID TTL Len Desc The code for this option is TBD and the length is 5.
+--+--+--+--+---+---+--+--+-...-+--+--+
| 1 |10 |16 | Inside abcd.com |
+--+--+--+--+---+---+--+--+-...-+--+--+
| 2 |16 |5 | world |
+--+--+--+--+---+---+--+--+-...-+--+--+
4 References 3. References
[1] Droms, R., "Dynamic Host Configuration Protocol", RFC1541, [1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
October 1993 March 1997.
[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 2132, March 1997.
University, October 1993.
[3] Meyer, D., ``Administratively scoped IP Multicast''
<draft-ietf-mboned-admin-ip-space-01.txt>
[4] Patel, B., and Shah, M., ``Multicast address allocation [3] Patel, B., M. Shah, and S. Hanna, "Multicast address
extensions to the Dynamic Host Configuration allocation based on the Dynamic Host Configuration Protocol",
Protocol'' <draft-ietf-dhc-mdhcp-00.txt> draft-ietf-malloc-mdhcp-00.txt, August 1998.
5 Author's Address 4. Authors' Addresses
Baiju V. Patel Baiju V. Patel
Intel Corp. Intel Corp.
2111 NE 25th Ave. 2111 NE 25th Ave.
Hillsboro, OR 97124 Hillsboro, OR 97124
Phone: 503 264 2422 Phone: 503 264 2422
EMail: baiju@ibeam.intel.com EMail: baiju.v.patel@intel.com
Munil Shah Munil Shah
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone:425 703 3924 Phone:425 703 3924
Email:munils@microsoft.com Email:munils@microsoft.com
This document will expire on April, 1998 Stephen R. Hanna
Sun Microsystems, Inc.
2 Elizabeth Drive, M/S UCHL03-205
Chelmsford, MA 01824
Phone: +1.978.442.0166
Email: steve.hanna@sun.com
 End of changes. 

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