LCP echo request/reply support over multilink interface (RFC 1990)

Hi 

 

Can you please help me to understand how LCP echo request/response can
be supported on a bundle? 

 

Page no.4 of RFC 1990 says below.

 

LCP negotiations are not permitted on the bundle itself.  An
   implementation MUST NOT transmit LCP Configure-Request, -Reject,
   -Ack, -Nak, Terminate-Request or -Ack packets via the multilink
   procedure, and an implementation receiving them MUST silently discard
   them.  (By "silently discard" we mean to not generate any PPP packets
   in response; an implementation is free to generate a log entry
   registering the reception of the unexpected packet).  By contrast,
   other LCP packets having control functions not associated with
   changing the defaults for the bundle itself are permitted.  An
   implementation MAY transmit LCP Code-Reject, Protocol-Reject, Echo-
   Request, Echo-Reply and Discard-Request Packets.
 

 

"Bundle interface is a virtual interface. If there has to be LCP keep
alive on it, it has to go through one of the underlying physical links.
But LCP keep alive packet format does not seem to specify any interface
details. How does the remote identify that the LCP echo received on a
physical link belongs to bundle?

 

Regards

yp

_______________________________________________
Pppext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pppext