@techreport{ietf-pppext-l2tp-link-00,
    number =    {draft-ietf-pppext-l2tp-link-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-pppext-l2tp-link/00/},
    author =    {William Palter and Mark Townsley},
    title =     {{L2TP Link Extensions}},
    pagetotal = 6,
    year =      1998,
    month =     nov,
    day =       23,
    abstract =  {The physical separation of the LAC and LNS with L2TP{[}2{]} and logical separation of the responsibilities of each with respect to negotiated link parameters introduces a lack of awareness between the tunnel endpoints that does not exist in a typical PPP dialup device. When possible, Proxy LCP provides a manner in which to negotiate link parameters at the LAC and communication of these in full to the LNS. If these options can be made acceptable to the LNS, then there should not be any insurmountable difficulty with regard to mismatch of link expectations. However, given that there are instances where negotiation of LCP{[}1{]} must take place at the LNS, some direction by the LAC as to what parameters are acceptable, as well as some communication from the LNS as to what parameters have been negotiated, is desirable.},
}