draft-ietf-mboned-ipv6-multicast-issues-00.txt   draft-ietf-mboned-ipv6-multicast-issues-01.txt 
MBONE Deployment WG P. Savola MBONE Deployment WG P. Savola
Internet-Draft CSC/FUNET Internet-Draft CSC/FUNET
Expires: February 9, 2005 August 11, 2004 Expires: March 3, 2005 September 2, 2004
IPv6 Multicast Deployment Issues IPv6 Multicast Deployment Issues
draft-ietf-mboned-ipv6-multicast-issues-00.txt draft-ietf-mboned-ipv6-multicast-issues-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 9, 2005. This Internet-Draft will expire on March 3, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2004).
Abstract Abstract
This memo describes known issues with IPv6 multicast, and provides This memo describes known issues with IPv6 multicast, and provides
historical reference of how some earlier problems have been resolved. historical reference of how some earlier problems have been resolved.
skipping to change at page 7, line 37 skipping to change at page 7, line 37
One should note that as Embedded RP does not require MSDP peerings One should note that as Embedded RP does not require MSDP peerings
between the RPs, it's possible to deploy more RPs in a PIM domain. between the RPs, it's possible to deploy more RPs in a PIM domain.
For example, the scalability and redundancy could be achieved by For example, the scalability and redundancy could be achieved by
co-locating RP functionality in the DRs: each major source, which co-locating RP functionality in the DRs: each major source, which
"owns" a group, could have its own DR act as the RP. This has about "owns" a group, could have its own DR act as the RP. This has about
the same redundancy characteristics as using SSM -- so there may not the same redundancy characteristics as using SSM -- so there may not
be an actually very urgent need for Anycast-RP if operational methods be an actually very urgent need for Anycast-RP if operational methods
to include fate-sharing of the groups is followed. to include fate-sharing of the groups is followed.
In any case, a "cold failover" variant of anycast-RP, without state In any case, "cold failover" redundancy without state sharing is
sharing, applicable for long-term redundancy, is still an option. In still an option. This does not offer any load-balancing of RPs or
this mechanism, multiple routers would be configured with the RP shared trees, but provides only long-term redundancy. In this
address, but only one would be active at the time: if the main RP mechanism, multiple routers would be configured with the RP address
goes down, another takes its place. However, the multicast state (with appropriate unicast metrics), but only one of them would be
stored in the RP would be lost, unless it is synchronized by some active at any time: if the main RP goes down, another takes its
out-of-band mechanism. place. However, the multicast state stored in the RP would be lost,
unless it is synchronized by some out-of-band mechanism.
4.1.2 Embedded RP and Control Mechanisms 4.1.2 Embedded RP and Control Mechanisms
With ASM and MSDP deployment, the ISPs can better control who is With ASM and MSDP deployment, the ISPs can better control who is
using their RPs. using their RPs.
With Embedded RP, anyone could use a third-party RP to host their With Embedded RP, anyone could use a third-party RP to host their
groups unless some mechanisms, for example access-lists, are in place groups unless some mechanisms, for example access-lists, are in place
to control the use of the RP [I-D.ietf-mboned-embeddedrp]. to control the use of the RP [I-D.ietf-mboned-embeddedrp].
 End of changes. 

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