draft-ietf-ipngwg-scoped-routing-00.txt   draft-ietf-ipngwg-scoped-routing-01.txt 
INTERNET DRAFT Brian Haberman INTERNET DRAFT Brian Haberman
September 1998 IBM April 1999 IBM
Routing of Scoped Addresses Routing of Scoped Addresses
in the Internet Protocol Version 6 (IPv6) in the Internet Protocol Version 6 (IPv6)
<draft-ietf-ipngwg-scoped-routing-00.txt> <draft-ietf-ipngwg-scoped-routing-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 and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its areas, all provisions of Section 10 of RFC 2026.
and its working groups. Note that other groups may also distribute
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working documents
as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months, and may be updated, replaced, or obsoleted by other documents months, and may be updated, replaced, or obsoleted by other documents
at any time. It is not appropriate to use Internet Drafts as at any time. It is not appropriate to use Internet-Drafts as
reference material, or to cite them other than as a ``working draft'' reference material, or to cite them other than as a ``working draft''
or ``work in progress.'' or ``work in progress.''
To learn the current status of any Internet Draft, please check the The list of current Internet-Drafts can be accessed at
``1id-abstracts.txt'' listing contained in the Internet Drafts Shadow http://www.ietf.org/ietf/1id-abstracts.txt.
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific The list of Internet-Draft Shadow Directories can be accessed at
Rim), ftp.ietf.org (US East Coast), ftp.isi.edu (US West Coast). http://www.ietf.org/shadow.html.
Abstract Abstract
This document outlines a mechanism for generating routing tables that This document outlines a mechanism for generating routing tables that
include scoped IPv6 addresses. It defines a set of include scoped IPv6 addresses. It defines a set of
rules for routers to implement in order to forward scoped unicast and rules for routers to implement in order to forward scoped unicast and
multicast addresses regardless of the routing protocol. It should be multicast addresses regardless of the routing protocol. It should be
noted that these rules will apply to all scoped addresses. noted that these rules will apply to all scoped addresses.
Contents Contents
skipping to change at page 1, line 87 skipping to change at page 1, line 90
- Each interface participating in a site has a site identifier - Each interface participating in a site has a site identifier
- In the absence of explicit configuration, all site identifiers on - In the absence of explicit configuration, all site identifiers on
a node default to the same value a node default to the same value
A single site router is defined as a router configured with the same A single site router is defined as a router configured with the same
site identifier on all interfaces. A site boundary router is defined site identifier on all interfaces. A site boundary router is defined
as a router that has at least 2 distinct site identifiers configured. as a router that has at least 2 distinct site identifiers configured.
This could include a router connected to 2 distinct sites or a router This could include a router connected to 2 distinct sites or a router
connected to 1 site and a separate global network (Figure 1). connected to 1 site and a separate global network (Figure ??).
3. Single Site Routing 3. Single Site Routing
In a single site router, a routing protocol In a single site router, a routing protocol
can advertise and route all addresses and prefixes on all interfaces. can advertise and route all addresses and prefixes on all interfaces.
This configuration does not require any special handling for site This configuration does not require any special handling for site
local addresses. The reception and transmission of site local local addresses. The reception and transmission of site local
addresses is handled in the same manner as globally scoped addresses. addresses is handled in the same manner as globally scoped addresses.
This applies to both unicast and multicast routing protocols. This applies to both unicast and multicast routing protocols.
skipping to change at page 3, line 44 skipping to change at page 3, line 44
site prefix = FEC0:0:0:K/64 site prefix = FEC0:0:0:K/64
i/f 3 : global prefix = 3FFE:40::/64 i/f 3 : global prefix = 3FFE:40::/64
site prefix = FEC0:0:0:M/64 site prefix = FEC0:0:0:M/64
i/f 4 : global prefix = 3FFE:80::/64 i/f 4 : global prefix = 3FFE:80::/64
no site prefix no site prefix
Figure 2: Routing Information Exchange Figure 2: Routing Information Exchange
As an As an example, the router in Figure ?? must advertise routing
example, the router in Figure 2 must advertise routing information on information on four interfaces. The information advertised is as
four interfaces. The information advertised is as follows : follows :
- Interface 1 - Interface 1
* All global prefixes (3FFE:20::/64, 3FFE:40::/64, and * All global prefixes (3FFE:20::/64, 3FFE:40::/64, and
3FFE:80::/64) 3FFE:80::/64)
* Site prefix FEC0:0:0:N/64 * Site prefix FEC0:0:0:N/64
* Site prefix FEC0:0:0:K/64 * Site prefix FEC0:0:0:K/64
skipping to change at page 5, line 30 skipping to change at page 5, line 30
reachable with the specified source address. reachable with the specified source address.
5. Scoped Multicast Routing 5. Scoped Multicast Routing
With IPv6 multicast, there are multiple scopes With IPv6 multicast, there are multiple scopes
supported. Multicast routers must be able to control the propagation supported. Multicast routers must be able to control the propagation
of scoped packets based on administratively configured boundaries. of scoped packets based on administratively configured boundaries.
5.1. Routing Protocols 5.1. Routing Protocols
Multicast routing protocols will have to follow the same rules as the Multicast routing protocols must follow the same rules as the unicast
unicast protocols. They will be required to maintain information protocols. They will be required to maintain information about
about global prefixes as well as information about all scope global prefixes as well as information about all scope boundaries
boundaries that pass through the router. Multicast protocols that pass through the router. Multicast protocols that rely on
that rely on underlying unicast protocols (i.e. PIM) will not suffer underlying unicast protocols (i.e. PIM) will not suffer as much of a
as much of a performance impact since the unicast protocol will performance impact since the unicast protocol will handle the
handle the forwarding table generation. They must be able to handle forwarding table generation. They must be able to handle the
the additional scope boundaries used in multicast addresses. additional scope boundaries used in multicast addresses. Multicast
Multicast protocols that generate and protocols that generate and
maintain their own routing tables will have to perform the additional maintain their own routing tables will have to perform the additional
route calculations for scope. All multicast protocols will be forced route calculations for scope. All multicast protocols will be forced
to handle 14 additional scoping identifiers above the site to handle 14 additional scoping identifiers above the site
identifiers supported in IPv6 unicast addresses. identifiers supported in IPv6 unicast addresses.
5.2. Packet Forwarding 5.2. Packet Forwarding
The forwarding rules for multicast can be described by the following The forwarding rules for multicast can be described by the following
combinations : combinations :
 End of changes. 9 change blocks. 
26 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/