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

network


Click on the red underlined text to get to the source

... Non Broadcast Multiple Access (NBMA) networks may be utilized in a variety of ways. At one extreme, they can be used to simply provide administratively configurable point to point ...
... IPv6 hosts, in certain situations). At the other extreme, NBMA networks that support dynamic establishment and teardown of Virtual Circuits (or functional ...
... IPv6 over NBMA networks. It forms the basis for companion documents that provide details specific to various NBMA technologies (for example, ATM ...
... interfaces on an NBMA network. These will be generically referred to as "SVCs" in the rest of the document. The use of administratively configured point to point ...
... Certain NBMA networks may provide a form of connectionless service (e.g. SMDS ...
... world of NBMA (Non Broadcast, Multiple Access) networks ARP has been applied to IPv4 ...
... range of NBMA network technologies. ...
... multicasting. This is not particularly true of most NBMA network services, and usually requires convergence protocols to emulate the desired service ...
... applicability of RFC 2022prop beyond ATM networks. ...
... IP is deployed across NBMA networks capable of supporting dynamic establishment of calls (SVCs or functional equivalent). For IPv6 ...
... NBMA networks providing PVC support. ...
... When the NBMA network is used in PVC mode, each PVC will connect ...
... NBMA networks providing SVC support. ...
... When the NBMA network is used in SVC mode, the key components are: ...
... multicast using multipoint calls provided by the underlying NBMA network. ...
... this architecture to ATM networks, or an E.164 number when applying this architecture ...
... this architecture to SMDS networks.) ...
... NBMA-specific companion specifications. Certain NBMA networks may provide a form of connectionless service (e.g. SMDS). In ...
... Link" when used over NBMA networks, and introduces the notion of the Transient Neighbor. Section 3 describes the modifications to the MARS ...


... hosts that would share the same routing prefixes (network and subnetwork masks). ...


... Note that section 1.3.1 applies when the NBMA network is being used to provide only configured point to point (PVC ...


... The majority of this section applies only to NBMA networks when used to provide point to point and point to multipoint SVCs. Section 7 ...
... point to point and point to multipoint SVCs. Section 7 discusses the case where the NBMA network is being used to supply only point to point PVCs ...
... control messages SHALL be defined in companion documents specific to particular NBMA network technologies. ...
... For NBMA networks where LLC/SNAP encapsulation is typically used ...
... For NBMA networks that do not use LLC/SNAP encapsulation, an ...
... next hop destination will be detected and handled at the IPv6 Network Layer through NUD. ...
... For NBMA networks where LLC/SNAP encapsulation is typically used ...
... For NBMA networks that do not use LLC/SNAP encapsulation, an ...
... For NBMA networks that do not use LLC/SNAP encapsulation, alternative ...
... node is located on the NBMA network. The redirected node will set up a pt-pt VC to the new node ...
... This time limit MAY be reduced through configuration or as specified in companion documents for specific NBMA networks. ...
... signaling the establishment and teardown of pt-pt and pt-mpt SVCs for different NBMA networks SHALL be specified in companion documents. ...
... NBMA drivers can assume that they will always be talking to another driver attached to the same type of NBMA network. (For example, an IPv6/NBMA ...


... tokens SHALL be specified in companion documents specific to each NBMA network. ...
... tokens SHALL be specified in companion documents specific to each NBMA network. ...
... and [NBMA Subaddress] fields are specific to each NBMA network, and SHALL be specified in companion documents. ...


... IPv6 over NBMA networks. It forms the basis for subsidiary companion documents that provide details for various specific NBMA technologies (such as ATM ...


... ATM Forum, "ATM User Network Interface (UNI) Specification Version 3.1", ISBN 0-13-393828-X, Prentice Hall, Englewood Cliffs, NJ, June 1995. ...
... Crawford, M., "A Method for the Transmission of IPv6 Packets over Ethernet Networks", RFC 1972(-> 2464prop), August 1996. ...
... Multicast over UNI 3.1 based ATM Networks", RFC 2022prop, November 1996. ...
... Plummer, D., "An Ethernet Address Resolution Protocol - or - Converting Network Protocol Addresses to 48.bit Ethernet Address ...
... Armitage, G., Schulter, P. and M. Jork, "IPv6 over ATM Networks", RFC 2492prop, January 1999. ...


... semantics of the IPv6 protocols. No changes need to be made to the IPv6 Network Layer. Since the concept of the security association is not being changed for NBMA ...
... that chooses what (and even if) to reply to the solicitation. Thus, NBMA will be transparent to the network layer except in cases where extra services ...
... address in relation to DAD is described in A.1.4). The IPv6 network layer will join these ...
... IPv6/NBMA driver is passed the Neighbor Solicitation message from the IPv6 network layer, it follows the steps described in section 4.4.2 Sending Multicast ...
... nodes will process the data as described in section 4.5 and pass the de-encapsulated packets to the IPv6 network layer. ...
... node's link-layer address from the IPv6 network layer. It will then follow the steps described in section section 4.4.1 to send the NA message ...
... VC, de-encapsulate the message, and pass it to the IPv6 Network layer for processing as described in section 4.5. The soliciting node ...
... NBMA driver is passed the Neighbor Advertisement from the IPv6 network layer, it follows the steps described in section 4.4.2 to send the NA message ...
... incoming packet as described in section 4.5 and then pass the packet to the IPv6 network layer where it will be processed as described in [7 ...
... IPv6/NBMA driver gets the JoinLocalGroup request from the IPv6 Network Layer, it follows the process described in section 4.2. ...
... IPv6/NBMA driver gets the Router Advertisement message from the IPv6 network layer, it transmits the message by following steps described in section 4.4.2. The MARS ...
... node on the LL will then process the incoming packet as described in section 4.5 and pass the received packet to the IPv6 Network layer for processing as appropriate. ...
... IPv6/NBMA driver gets the request from the IPv6 Network Layer to send the packet, it follows the steps described in section 4.4.2. The RS ...
... unicast to the soliciting node, the IPv6 network layer will give the node's IPv6 ...
... Router Advertisement as described in section 4.5 and will pass the RA message to the IPv6 network layer. The IPv6 network layer ...
... RA message to the IPv6 network layer. The IPv6 network layer may, depending on the state of ...
... VC to a neighbor (see section 4.4.1), are detected and handled at the IPv6 network layer, through Neighbor Unreachability Detection. The node ...
... NBMA driver gets the Neighbor Solicitation message from the IPv6 network layer, it follows the steps outlined in section 4.4.2. The NS ...
... filter out the message so that the sending node's IPv6 network layer will not see the message. The IPv6 network layer ...
... IPv6 network layer will not see the message. The IPv6 network layer of any node ...
... nodes will de-encapsulate the message and pass it to the IPv6 network layer. The host ...
... encapsulate the packet, and pass the Redirect message to the IPv6 Network Layer, as described section 4.5. ...
... Redirect Message. For NBMA networks, the Redirect Message should contain the link-layer address option as described in [7 ...
... node on the NBMA network, regardless of the LL membership of the new target node. ...
... Once redirected, the IPv6 network layer will give the node's ...
... IPv6/NBMA driver gets the JoinLocalGroup request from the IPv6 network layer, it follows the process described in section 4.2. ...
... node's IPv6/NBMA driver gets the request from the IPv6 Network Layer to send the packet, it follows the steps described in section 4.4.2. This will result in one or more nodes ...
... node that receives the solicitation packet will process it as described in section section 4.5. Only the IPv6 network layer of the DHCPv6 server/relay-agent ...
... DHCPv6 Advertisement to the DHCPv6 client. The IPv6 network layer will give the node ...
... encapsulate the multicast packet and then pass it up to the IPv6 Network Layer for processing. The IPv6 network ...
... it up to the IPv6 Network Layer for processing. The IPv6 network layer will deliver the DHCPv6 ...
... Agent. Prior to sending the DHCPv6 message, the IPv6 network layer will perform Neighbor Discovery (if necessary) to obtain the link-layer address ...
... node's IPv6/NBMA driver gets the request from the IPv6 network layer to send the Group ...
... NBMA drivers will receive the packet, de-encapsulate it, and passed it up to the IPv6 Network layer. If the originating node ...
... IPv6/NBMA driver gets the request from the IPv6 network layer to send the packet, it follows the steps described in 4.4.2. The node ...
... encapsulate the incoming packet and the packet will be passed to the IPv6 network layer for processing. The MARS client ...


... between ND and connection oriented networks. ...


... guarantees, and optimal use of underlying IP and NBMA network resources are still subjects of ongoing research in the IETF ...
... flow detection as a means to optimize the use of NBMA network resources through the establishment of inter-LL shortcuts. ...
... NBMA shortcuts are for the benefit of 'the network' optimizing its forwarding of IPv6 packets in the absence of any other guidance ...
... NBMA host to have some mechanism for overriding attempts by 'the network' to optimize its internal forwarding path. ...
... A zero FlowID has IPv6 semantics of "the source allows the network to utilize its own discretion in providing best-effort forwarding service ...
... non-zero FlowID might be assigned by the source host after negotiating a preferred forwarding mechanism with 'the network' (e.g. through dynamic means such as RSVP, or administrative means). ...
... Alternatively it can simply be assigned randomly by the source host, and the network will provide default best effort forwarding (an IPv6 router ...



Google
Web
RFC-Ref