[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: NodeId as destinationIpAddress in (UNI) RSVP and LMP messages
Between the pair of UNI C and UNI N there can be multiple control channels
where they can be used simultaneously or in primary/backup modes. That
really doesn't matter as long as the "signalling channel" which is a bunch
of all IPCCs between these two nodes are up. Hence the node Ids are used in
Since in optical links there may not be one to one association of signalling
and data channels the RSVP_HOP object was modified to carry the extra
information of data channels (by adding the TLVs) . See RFC 2205 for use of
the RSVP_HOP object . Depending on the IPCC being numbered/unnumbered the
IPv4_IF_ID_RSVP_HOP object is used to identify the IPCC ; i.e combination
of hop address (node address) and interface id used for unnumbered, in
numbered use the IP address (of ipcc) and lih is not used.
> -----Original Message-----
> From: Robin Qiu [mailto:firstname.lastname@example.org]
> Sent: Wednesday, December 12, 2001 9:18 AM
> To: email@example.com
> Subject: NodeId as destinationIpAddress in (UNI) RSVP and LMP messages
> Can anyone help on this?
> In UNI125.7, 12.4.2, it says that the IP header for UNI RSVP messages
> must be set to the NodeId of the UNI peer. In section 9.3, it
> also says
> that for ServiceDiscovery LMP messages, the destination IP address is
> set to the NodeId of the recipient.
> Question: how do you force to use a specific IPCC you selected,
> assuming that the selected IPCC has a different address?
> Robin Qiu
> Chat with friends online, try MSN Messenger: http://messenger.msn.com