Re: HDLC frames delivered over PWs
Carlos Pignataro <[email protected]>
| Newsgroups | gmane.ietf.l2tpext |
|---|---|
| Organization | cisco Systems, Inc. |
| Message-ID | <[email protected]> |
Hello Javi,
All frames (think of it as a pseudo-wire); you can refer to RFC4349,
first paragraph of Section 4.1 and first bullet of Section 5:
http://tools.ietf.org/html/rfc4349#section-4.1
The HDLCPW Type over L2TP is
intended to operate in an "interface to interface" or "port to port"
fashion, passing all HDLC data and control PDUs over the PW. The
HDLC PDU is stripped of flags and trailing FCS, bit/byte unstuffing
is performed, and the remaining data, including the address, control,
and protocol fields, is transported over the PW.
http://tools.ietf.org/html/rfc4349#section-5
o HDLC data and control fields are transported transparently (see
Section 4.1). The specific negotiations and signaling of the
protocol being transported are performed between Remote Systems
transparently, and the LCCE does not participate in them.
Thanks,
--Carlos.
On 9/4/2006 4:37 AM, Javi allegedly said the following:
> One question related to transport of HDLC (or LAPB) frames over L2TPv3
> (+PWE3):
>
> What HDLC frames are delivered over PWs?, only frames I (Information),
> also RR and RNR, or all frames. It is a very important efficiency
> factor. For instance, RR frames are continuously send, it would consume
> too bandwidth in IP network.
>
> Javi Muñoz
>
>
> _______________________________________________
> L2tpext mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/l2tpext
>
--
--Carlos Pignataro.
Escalation RTP - cisco Systems