Does FRPW[RFC4591] support LAPF frames (with control field)[Q.933] or only Core-LAPF frames (without control field)[Q.933/Annex A]? If FRPW supports LAPF frames, must the ingress PE read the control field or it must be carried transparently to the egress PE?
Javi, The response at <http://www.ietf.org/mail-archive/web/pwe3/current/msg12573.html> is applicable here to RFC 4349 and RFC 4591 respectively. Thanks, -- Carlos. On 8/8/2011 2:58 PM, Javi wrote: > Does FRPW[RFC4591] support LAPF frames (with control field)[Q.933] or > only Core-LAPF frames (without control field)[Q.933/Annex A]? > > If FRPW supports LAPF frames, must the ingress PE read the control field > or it must be carried transparently to the egress PE? > _______________________________________________ > L2tpext mailing list > L2tpext <at> ietf.org > https://www.ietf.org/mailman/listinfo/l2tpext >
[RFC5611] indicates: "Using the variable-rate AAL2 mode, we may dynamically allocate channels to be transported (i.e. VAD), thus conserving bandwidth." Is it possible to use the MeGaCo protocol to indicate to the PEs which channels may be transported by a TDMPW? (it would allow to select the channels to be transported based on any criteria, such as an external signalling protocol).
RSS Feed