RFC 3931:Layer Two Tunneling Protocol - Version 3 ...
RFC-Ref

encapsulation


Click on the red underlined text to get to the source

... L2TP sessions, and (2) the L2TP data encapsulation to multiplex and demultiplex L2 data streams between two L2TP ...
... The channel for L2TP-encapsulated data traffic that passes between two LCCEs ...
... L2TP node and the encapsulated network layer (L3 ...


... L2TP to guarantee delivery (see Section 4.2 for details). Data messages are used to encapsulate the L2 traffic being carried over the L2TP ...
... data channels, respectively. Data messages are passed over an unreliable data channel, encapsulated by an L2TP header ...


... Session Header encapsulations. Session ID ...
... LCCE from a Remote System that, after encapsulation with its associated framing, L2TP, and IP, ...
... fragmentation on the packet before tunnel encapsulation. This creates two (or more) L2TP packets, each ...
... LCCE from a Remote System that, after encapsulation with associated framing, L2TP and IP, does not fit in ...
... MTU between tunnel endpoints and should work for any type of L2- encapsulated packet. Note that IPv6 does not support "in-flight" fragmentation ...
... fragmentation, fragmenting IP packets before encapsulation with L2TP/IP, or fragmenting the resultant L2TP ...
... circuit frames are received at an LCCE, encapsulated in L2TP (with appropriate attention to framing, as described in documents for the particular pseudowire type ...
... session negotiation. Alternative sublayers MAY be defined (e.g., an encapsulation with a larger Sequence Number field or timing information) and identified ...


... AVPs with a 32-bit Vendor ID MUST be encapsulated in the following manner: ...
... (e.g., a PPP control packet or NETBIOS frame encapsulated by Frame Relay before being tunneled). All traffic that can be classified ...



Google
Web
RFC-Ref