Clarifications with RFC 3077
William StanisLaus <[email protected]> Tue, 29 Oct 2002 06:01:43 -0500
| Newsgroups | gmane.ietf.udlr |
|---|---|
| Message-ID | <[email protected]> |
Hi all,
I am a newbee to UDLR technology. I have few clarifications with RFC 3077.
Can you help me in understanding the concept.
here we go.....
1)
In Section 7
"The number of feeds is expected to be relatively small (Section 3),
so at every feed the list of all feeds is configured manually."
In Section 7.1
When Feed multicasts the DTCP Hello Message, it passes the Feed Type
i.e.
F (1 bit): bit indicating the type of feed:
0 = Send-only feed
1 = Receive-capable feed
So the Reciever can maintain the Feed type in the DTCP routing table.
In Such cases,
for Scenario 2: "A receiver can send a broadcast/multicast packet on the
link to all nodes (point-to-multipoint)"
Section 6.2.2 (3)
As of now, Receiver sends packets to be broadcasted/multicasted to the default
feed and the default feed broadcast/multicast the packet to the other Feed &
Receivers.
Clarification :-
When the Receiver maintains the Feed types, which is dynamic at any moment,
why Receiver is not multicasting to all the Feeds which are Send only?
It can also have a default Feed which forwards the packet to all receivers and
receive capable Feeds.
The clarification is because, we have the overhead of encapulation at the
receiver side and sending to the default feed which decapulate and again
encapulate to send to Send only Feeds. Also in the Feeds the list of
other feeds are manually configured i.e. Static. Might be broken at any time.
2)
In the RFC 3077 which explaines about the Feeds , i.e. Send only and Recieve
capable Feeds. But for receivers it is always targeted as Receive only. Just
imagine a RCST with send capable receivers i.e. which has both Tx and Rx port.
What are the configurations in the UDLR if the receiver happens to be send
capable.
Thanks and Best Regards,
William StanisLaus.