From: Victor Cappuccio (cvictor@protokolgroup.com)
Date: Sun Aug 13 2006 - 16:08:03 ART
This is nice question, reading the RFC 2328 should respond that
The LOOP . . BACK is for the routers, it loopbacks back to me, there is no
Router in the PATH ;D
Parts that I think the RFC 2328 is trying to respond this could be:
host routes are classified as links to stub networks with network mask of
0xffffffff , means = 255.255.255.255
An edge connecting a router to a network indicates that the router has
an interface on the network. Networks can be either transit or stub
networks.
Transit networks are those capable of carrying data traffic that is neither
locally originated nor locally destined. A transit network is represented by
a graph vertex having both incoming and outgoing edges. A stub network's
vertex has only incoming edges.
When interface addresses are assigned, they are modeled as stub links, with
each router advertising a stub connection to the other router's interface
address. Optionally, an IP subnet can be assigned to the point-to-point
network. In this case, both routers advertise a stub link to the IP subnet,
instead of advertising each others' IP interface addresses.
HTH
Victor.-
-----Mensaje original-----
De: nobody@groupstudy.com [mailto:nobody@groupstudy.com] En nombre de
sabrina pittarel
Enviado el: Domingo, 13 de Agosto de 2006 02:48 p.m.
Para: Group Study (E-mail)
Asunto: OSPF, loopbacks and CCIE
Hi all,
as you know OSPF advertise loopbacks as /32 networks
(stub network) regardless of the "real" mask
associated to them.
If the lab asks to advertise the loopback in ospf area
X (i.e. without using redistribution), should we make
sure the "real" subnet is advertised or a /32 network
is acceptable?
Sabrina
This archive was generated by hypermail 2.1.4 : Fri Sep 01 2006 - 15:41:57 ART