draft-ietf-dhc-multopt-00.txt   draft-ietf-dhc-multopt-01.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-00.txt> <draft-ietf-dhc-multopt-01.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 3, line 53 skipping to change at page 3, line 53
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.
Example: Example:
The multicast address allocation servers are listening to multicast The multicast address allocation servers are listening to multicast
address 239.1.1.1. The maximum allowed value for the TTL for this address 239.1.1.1. The maximum allowed value for the TTL for this
address is 16. There are two scopes supported by the multicast address is 16. There are two scopes supported by the multicast
address allocation server: 1) Inside the abcd.com, 2) world. Then address allocation server: 1) Inside the abcd.com, 2) world. Then
this option will be used as: this option will be used as:
 End of changes. 

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