draft-ietf-ospf-isis-flood-opt-00.txt   draft-ietf-ospf-isis-flood-opt-01.txt 
Network Working Group Alex Zinin Network Working Group Alex Zinin
Internet Draft Mike Shand Internet Draft Mike Shand
Expiration Date: April 2001 Cisco Systems Expiration Date: September 2001 Cisco Systems
File name: draft-ietf-ospf-isis-flood-opt-00.txt October 2000 File name: draft-ietf-ospf-isis-flood-opt-01.txt March 2001
Flooding optimizations Flooding optimizations
in link-state routing protocols in link-state routing protocols
draft-ietf-ospf-isis-flood-opt-00.txt draft-ietf-ospf-isis-flood-opt-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet Drafts are working documents of the Internet Engineering Internet Drafts are working documents of the Internet Engineering
Task Force (IETF), its Areas, and its Working Groups. Note that other Task Force (IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet Drafts. groups may also distribute working documents as Internet Drafts.
skipping to change at page 7, line 36 skipping to change at page 7, line 36
the FloodingActive interface field to FALSE. (We always the FloodingActive interface field to FALSE. (We always
prefer sending LSAs to multiple neighbors simultaneously). prefer sending LSAs to multiple neighbors simultaneously).
2. Otherwise, among the interfaces in the P2pIntList, set 2. Otherwise, among the interfaces in the P2pIntList, set
FloodingActive field to TRUE for those interfaces that have FloodingActive field to TRUE for those interfaces that have
the best interface cost. Set it to FALSE for all other the best interface cost. Set it to FALSE for all other
interfaces in the list. interfaces in the list.
3.2.2 Initial LSDB synchronization 3.2.2 Initial LSDB synchronization
Whenever a neighbor's FSM reaches state ExStart, routers exchange Implementations may decide to maintain a single link state request
database description packets to inform each other about the contents list per neighbor in an area. This may be used to split the Loading
of their LSDBs. If at this moment there is at least one full adja- process among several links when more than one adjacency is coming up
cency with the same neighbor going through another interface, the simultaneously. Note that in this case, whenever the link state
router can speed up establishment of the new adjacency by including request list for a particular neighbor becomes empty, a LoadingDone
in the DBD packets only those LSAs that are currently in the event should be generated for all adjacencies with this neighbor that
neighbor's retransmission list (if any). are currently in the Loading state.
The implementation may also consider ignoring the contents of
received database description packets. However, there is some proba-
bility that already established adjacencies are not quite reliable
and the other router is trying to deliver some LSAs and the router in
question misses its chance to get them since it is ignoring the DBD
contents.
Implementations may also decide to maintain a single link state
request list per neighbor in an area. This may be used to split the
Loading process among several links when more than one adjacency is
coming up simultaneously. Note that in this case, whenever the link
state request list for a particular neighbor becomes empty, a
LoadingDone event should be generated for all adjacencies with this
neighbor that are currently in the Loading state.
3.2.3 Asynchronous Flooding 3.2.3 Asynchronous Flooding
Asynchronous flooding algorithm is changed as follows. Note that Asynchronous flooding algorithm is changed as follows. Note that
changes described below do not affect flooding back to a multiaccess changes described below do not affect flooding back to a multiaccess
interface if the router is the DR. The changes are only in the part interface if the router is the DR. The changes are only in the part
where LSA is sent over other interfaces. where LSA is sent over other interfaces.
If the flooding scope is domain-wide, perform the following for If the flooding scope is domain-wide, perform the following for
all areas. If the flooding scope is area-wide, do the following all areas. If the flooding scope is area-wide, do the following
skipping to change at page 12, line 13 skipping to change at page 11, line 46
Hello PDUs and LSDB synchronization pocess), note however that the Hello PDUs and LSDB synchronization pocess), note however that the
routers should be explicitly configured to do so. routers should be explicitly configured to do so.
4 Security issues 4 Security issues
This document does not introduce any new security issues to ISIS or This document does not introduce any new security issues to ISIS or
OSPF. OSPF.
5 Acknowledgements 5 Acknowledgements
The authors would like to acknowledge Tony Przygienda and Yakov The authors would like to acknowledge Tony Przygienda, Yakov Rekhter,
Rekhter for their comments, and Jeff Learman for reviewing this docu- and John Moy for their comments, and Jeff Learman for reviewing this
ment. document.
6 References 6 References
[Ref1] J. Moy. OSPF version 2. Technical Report RFC 2328, Internet [Ref1] J. Moy. OSPF version 2. Technical Report RFC 2328, Internet
Engineering Task Force, 1998. ftp://ftp.isi.edu/in- Engineering Task Force, 1998. ftp://ftp.isi.edu/in-
notes/rfc2328.txt. notes/rfc2328.txt.
[Ref2] ISO, "Intermediate system to Intermediate system routeing [Ref2] ISO, "Intermediate system to Intermediate system routeing
information exchange protocol for use in conjunction with the information exchange protocol for use in conjunction with the
Protocol for providing the Connectionless-mode Network Service Protocol for providing the Connectionless-mode Network Service
(ISO 8473)," ISO/IEC 10589:1992. (ISO 8473)," ISO/IEC 10589:1992.
[Ref3] D. Awduche, Y. Rekhter, J. Drake, R. Coltun, [Ref3] D. Awduche, Y. Rekhter, J. Drake, R. Coltun,
skipping to change at page 12, line 34 skipping to change at page 12, line 19
information exchange protocol for use in conjunction with the information exchange protocol for use in conjunction with the
Protocol for providing the Connectionless-mode Network Service Protocol for providing the Connectionless-mode Network Service
(ISO 8473)," ISO/IEC 10589:1992. (ISO 8473)," ISO/IEC 10589:1992.
[Ref3] D. Awduche, Y. Rekhter, J. Drake, R. Coltun, [Ref3] D. Awduche, Y. Rekhter, J. Drake, R. Coltun,
"Multi-Protocol Lambda Switching: Combining MPLS Traffic "Multi-Protocol Lambda Switching: Combining MPLS Traffic
Engineering Control With Optical Crossconnects", draft- Engineering Control With Optical Crossconnects", draft-
awduche-mpls-te-optical-02.txt. Work in progress. awduche-mpls-te-optical-02.txt. Work in progress.
[Ref4] J. Lang, et al. "Link Management Protocol (LMP)", [Ref4] J. Lang, et al. "Link Management Protocol (LMP)",
draft-ietf-mpls-lmp-00.txt. Work in progress. draft-ietf-mpls-lmp-01.txt. Work in progress.
7 Authors' addresses 7 Authors' addresses
Alex Zinin Mike Shand Alex Zinin Mike Shand
Cisco Systems Cisco Systems Cisco Systems Cisco Systems
150 West Tasman Dr. 4, The Square 150 West Tasman Dr. 4, The Square
San Jose,CA Stockley Park San Jose,CA Stockley Park
95134 UXBRIDGE 95134 UXBRIDGE
E-mail: azinin@cisco.com Middlesex E-mail: azinin@cisco.com Middlesex
UB11 1BN, UK UB11 1BN, UK
 End of changes. 

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