Specifications

Page 91 /148
§ PIM sparse mode and dense mode—Protocol-Independent Multicast is
a multicast routing protocol. PIM sparse mode routes to multicast groups
that might span wide-area and interdomain internets. PIM dense mode
is a flood-and-prune protocol.
§ MSDP—Multicast Source Discovery Protocol allows multiple PIM sparse
mode
§ domains to be joined. A rendezvous point (RP) in a PIM sparse mode
domain has a peering relationship with an RP in another domain,
enabling it to discover multicast sources from other domains.
§ IGMP—Internet Group Management Protocol, Versions 1 and 2, is used
to manage membership in multicast groups.
§ SAP/SDP—Session Announcement Protocol and Session Description
Protocol handle conference session announcements.
3.1.3.3 Traffic engineering protocols
§ MPLS—Multiprotocol Label Switching, formerly known as tag switching,
allows you to manually or dynamically configure label-switched paths
(LSPs) through a network. It lets you direct traffic through particular
paths rather than rely on the IGP’s least-cost algorithm to choose a path.
§ RSVP—The Resource Reservation Protocol, Version 1, provides a
mechanism for engineering network traffic patterns that is independent
of shortest path decided upon by a routing protocol. RSVP itself is not a
routing protocol; it operates with current and future unicast and multicast
routing protocols. The primary purpose of the JUNOS RSVP software is
to support dynamic signaling for MPLS LSPs.
§ LDP—Label Distribution Protocol. A fundamental concept in MPLS is
that two Label Switching Routers (LSRs) must agree on the meaning of
the labels used to forward traffic between them. LDP supports the
general components of the Internet Draft draft-ietf-mpls-ldp-05.txt along
with these optional features listed in the draft specification:
o Upstream unsolicited label distribution discipline
o Liberal label retention mode.
o Neighbor discovery.
§ LDP on top of RSVP Engineered Tunnels—This feature provides
support for two-level label stacks, allowing to implement a traffic
engineering (MPLS/RSVP) core with LDP on the edges.
3.2 IP Routing
The Mxxx has a theoretical memory limit of approx. 500,000 route prefixes in its
routing table (for BGP, OSPF and IS-IS internal and external routes, RIPv2 and
static routes). Benchmark tests have shown the Mxxx to run at wire speed with a
table of 380,000 prefixes.
The supported Interior Gateway Protocols are :
§ OSPFv2 (RFC 1583) with support for the NSSA extensions as defined by
RFC 1587
§ IS-IS
§ RIPv2
The supported Exterior Gateway Protocols is BGP-4.
JUNOS supports also static routing.
A complete list of supported RFCs can be found in the Junos specifications
section.
Juniper Networks acknowledges that Cisco stills holds an important footprint in
the Internet, so the Mxxx routers have to interoperate flawlessly. The term we
use in "transparent interoperability"; i.e. if you notice the Mxxx router is there,
then there is a problem. To this end Juniper has implemented several
configuration knobs to insure Cisco interoperability even when in means deviating
from the written standards. The ultimate test is, of course, the real thing.
Interoperability between Juniper's and Cisco's BGP (as well as OSPF and ISIS)
has been proven several times over in the best way possible, live network
implementations.