RFC-Ref is not longer maintained; use RFC browser at: http://zvon.org/comp/r/ref-RFC.html
RFC 2491:IPv6 over Non-Broadcast Multiple Access (...
RFC-Ref

destination


Click on the red underlined text to get to the source

... implicitly exist if the sender has an NBMA destination address to which it can transmit packets whenever it desires. ...
... For destinations not currently considered to be Neighbors, a host ...
... NHRP query for the flow's destination IP address. ...
... IP source, identifying the flow's destination as a transient Neighbor. ...
... When the destination of a flow is solicited as a transient neighbor ...
... NBMA address will be the one chosen by the destination when the flow was originally established through hop- by-hop processing. This supports the existing ND ...
... ND ability for IPv6 destinations to perform their own dynamic interface load sharing. ...
... exist if the sender has an NBMA destination address to which it can transmit packets whenever it desires. ...


... multicast IP destination address. (IPv6 assumes that multicasting is an integral ...
... addresses of the IPv6 destination group's members. ...
... flows of IP packets may exist between source/destination pairs that are separated by IP routing boundaries. Shortcuts are created ...
... IPv6 allows a router to inform the members of an LL that there is a better 'first hop' to a given destination (section 8.2 [7]). The advertisement itself is achieved through a Router ...
... that is currently acting as the default router for the IP destination that the Redirect refers to. If a Redirect arrives that indicates a better first hop for a given destination ...
... destination that the Redirect refers to. If a Redirect arrives that indicates a better first hop for a given destination, and supplies a link layer (NBMA ...
... Create a Neighbor Solicitation message referring to the off-LL destination (target) for which a shortcut is desired ...
... host SHALL update its Neighbor and Destination caches. ...
... The destination of the flow that caused the trigger (or the target of ...
... target is reachable. If there is no appropriate entry in the Neighbor cache, or the destination is currently considered unreachable, the last hop router ...
... host. Specifically, if the target of the resulting short-cut is the destination host then the ICMP Target Address ...
... ICMP Target Address MUST be the same as the ICMP Destination Address in the original message. If the target ...
... IP traffic. This retains a useful feature of Neighbor Discovery - destination interface load sharing. ...
... link layer address format are defined in NBMA-specific companion documents. Source, destination or client protocol addresses ...
... NS message is used as the NHRP destination protocol address. A CIE SHALL NOT be specified. ...
... interface from which this message is sent. Destination Address IPv6 Source Address ...
... Client Protocol Address Destination Address Target of triggering NS ...
... NS (this is equivalent to the NHRP Destination Protocol Address) Target ...


... node SHALL place a call to set up a VC to the next hop destination. Any time the IPv6/NBMA ...
... If the call to the next hop destination node fails the sending node ...
... create a VC to the next hop destination will be detected and handled at the IPv6 Network Layer ...
... At this time no rules are specified for mapping outbound packets to VCs using anything more than the packet's destination address. ...
... If the packet's destination is one of the following multicast addresses, it SHALL be sent over the IPv6/NBMA ...
... If packet's destination is any other address, then the usual MARS ...
... At this time no rules are specified for mapping outbound packets to VCs using anything more than the packet's destination address. ...
... Before sending a packet to a new destination within the same LL a node will first perform a Neighbor Discovery ...
... target. This is done to resolve the IPv6 destination address into a link- layer ...
... Redirects are unidirectional. Even after the source has reacted to a redirect, the destination will continue to send IPv6 packets back to the redirected node ...
... the redirected node on the old path. This happens because the destination node has no way of determining the IPv6 address of the ...
... If a Neighbor or Destination cache entry is purged then any VCs associated with the purged entry SHOULD be released. ...


... Redirect Message to inform an IPv6 host of a better first-hop for reaching a particular destination, as described in [7]. This can be used to direct hosts ...
... Subsequent data sent from the IPv6 host to the destination will be sent to the next-hop address ...
... next-hop node when it sends data to the redirected destination. The node's IPv6 ...
... VC to the next-hop destination exists. If a pt-pt VC does not exist, then the IPv6/NBMA ...
... data packet and initiate a setup of a VC to the destination. When the VC is created, or if one already exists, then ...
... create a VC to the next-hop destination as specified in the Redirect message, but the next-hop will not be redirected to the source host ...
... Because no Neighbor Discovery takes place, the next-hop destination has no way of determining the identity of the caller ...
... update it's neighbor or destination caches. However, it will continue to transmit data back to the redirected host ...
... node should be able to use the new VC from the redirected destination if it too receives a redirect redirecting it to the redirected node. This behavior is consistent ...
... Query packet, it follows the steps described in 4.4.2. The node determines that the destination address of the packet is the all-nodes multicast address ...


... ICMPv6 packets. The IPv6 packets are then transmitted, and received by the intended destination set, using separate pt-mpt VCs per destination group ...
... destination set, using separate pt-mpt VCs per destination group. ...
... aggregation on the basis of a packet's function rather than its explicit IPv6 destination. The trade-off here is that the aggregation removes ...
... ND or RD messages, and logically remap their destinations to the All Nodes group ...
... IP layer, filtering will occur based on the packet's actual destination IP address, and only the targeted node will end up responding. ...


... through common header fields such as IPv6 destination addresses) is a local configuration issue. ...



Google
Web
RFC-Ref