2.3.8 Point-to-Point Protocol Extensions (pppext)

NOTE: This charter is a snapshot of the 46th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 18-Oct-99

Chair(s):

Karl Fox <karl@extant.net>

Internet Area Director(s):

Thomas Narten <narten@raleigh.ibm.com>
Erik Nordmark <nordmark@eng.sun.com>

Internet Area Advisor:

Thomas Narten <narten@raleigh.ibm.com>

Mailing Lists:

General Discussion:ietf-ppp@merit.edu
To Subscribe: ietf-ppp-request@merit.edu
Archive: ftp://merit.edu/pub/ietf-ppp-archive

Description of Working Group:

Note: A separate list has been set up for L2TP discussions:

L2TP Discussions:l2tp@ipsec.org To Subscribe: l2tp-request@ipsec.org Archive: http://www.ipsec.org/email/l2tp/

The Point-to-Point Protocol (PPP, RFC 1661) is a mature protocol with a large number of subprotocols, encapsulations and other extensions. The group will actively advance PPP's most useful extensions to full standard, while defending against further enhancements of questionable value.

The Layer 2 Tunneling Protocol (L2TP) is a brand-new protocol for tunneling PPP sessions over various network types. The group will actively advance the L2TP base protocol through the standards process and consider extensions to the base protocol.

Goals and Milestones:

Aug 99

  

Advance L2TP MIB to Proposed Standard

Aug 99

  

Advance SDL draft to Experimental

Aug 99

  

Advance AODI draft to Proposed Standard

Dec 99

  

Advance CHAP (RFC 1994) to Standard

Dec 99

  

Advance Multilink (RFC 1990) to Standard

Dec 99

  

Advance LQM (RFC 1989) to Standard

Dec 99

  

Advance IPCP (RFC 1332) to Draft Standard

Dec 99

  

Advance BCP (RFC 1638) to Draft Standard

Dec 99

  

Advance CCP (RFC 1962) to Draft Standard

Dec 99

  

Advance ECP (RFC 1968) to Draft Standard

Dec 99

  

Advance PPP over ISDN (RFC 1618) to Draft Standard

Mar 00

  

Advance L2TP to Draft Standard

Mar 00

  

Advance LCP MIB (RFC 1471) to Draft Standard

Mar 00

  

Advance CHAP MIB (RFC 1472) to Draft Standard

Mar 00

  

Advance IPCP MIB (RFC 1473) to Draft Standard

Mar 00

  

Advance BCP MIB (RFC 1474) to Draft Standard

Internet-Drafts:

Request For Comments:

RFC

Status

Title

 

RFC1332

PS

The PPP Internet Protocol Control Protocol (IPCP)

RFC1378

PS

The PPP AppleTalk Control Protocol (ATCP)

RFC1377

PS

The PPP OSI Network Layer Control Protocol (OSINLCP)

RFC1472

PS

The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol

RFC1473

PS

The Definitions of Managed Objects for the IP Network Control Protocol of the Point-to-Point Protocol

RFC1471

PS

The Definitions of Managed Objects for the Link Control Protocol of the Point-to-Point Protocol

RFC1474

PS

The Definitions of Managed Objects for the Bridge Network Control Protocol of the Point-to-Point Protocol

RFC1553

PS

Compressing IPX Headers Over WAN Media (CIPX)

RFC1552

PS

The PPP Internetwork Packet Exchange Control Protocol (IPXCP)

RFC1547

 

Requirements for an Internet Standard Point-to-Point Protocol

RFC1570

PS

PPP LCP Extensions

RFC1598

PS

PPP in X.25

RFC1618

PS

PPP over ISDN

RFC1638

PS

PPP Bridging Control Protocol (BCP)

RFC1663

PS

PPP Reliable Transmission

RFC1661

S

The Point-to-Point Protocol (PPP)

RFC1662

S

PPP in HDLC-like Framing

RFC1764

PS

The PPP XNS IDP Control Protocol (XNSCP)

RFC1763

PS

The PPP Banyan Vines Control Protocol (BVCP)

RFC1762

DS

The PPP DECnet Phase IV Control Protocol (DNCP)

RFC1968

PS

The PPP Encryption Control Protocol (ECP)

RFC1962

PS

The PPP Compression Control Protocol (CCP)

RFC1973

PS

PPP in Frame Relay

RFC1979

 

PPP Deflate Protocol

RFC1975

 

PPP Magnalink Variable Resource Compression

RFC1977

 

PPP BSD Compression Protocol

RFC1974

 

PPP Stac LZS Compression Protocol

RFC1967

 

PPP LZS-DCP Compression Protocol (LZS-DCP)

RFC1976

 

PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)

RFC1963

 

PPP Serial Data Transport Protocol (SDTP)

RFC1990

DS

The PPP Multilink Protocol (MP)

RFC1989

DS

PPP Link Quality Monitoring

RFC1978

 

PPP Predictor Compression Protocol

RFC1993

 

PPP Gandalf FZA Compression Protocol

RFC1994

DS

PPP Challenge Handshake Authentication Protocol (CHAP)

RFC2043

PS

The PPP SNA Control Protocol (SNACP)

RFC2097

PS

The PPP NetBIOS Frames Control Protocol (NBFCP)

RFC2118

 

Microsoft Point-To-Point Compression (MPPC) Protocol

RFC2125

PS

The PPP Bandwidth Allocation Protocol (BAP) The PPP Bandwidth Allocation Control Protocol (BACP)

RFC2153

 

PPP Vendor Extensions

RFC2290

PS

Mobile-IPv4 Configuration Option for PPP IPCP

RFC2284

PS

PPP Extensible Authentication Protocol (EAP)

RFC2363

PS

PPP Over FUNI

RFC2364

PS

PPP over AAL5

RFC2419

PS

The PPP DES Encryption Protocol, Version 2 (DESE-bis)

RFC2420

PS

The PPP Triple-DES Encryption Protocol (3DESE)

RFC2433

 

Microsoft PPP CHAP Extensions

RFC2484

PS

PPP LCP Internationalization Configuration Option

RFC2509

PS

IP Header Compression over PPP

RFC2615

PS

PPP over SONET/SDH

RFC2661

PS

Layer Two Tunneling Protocol 'L2TP'

RFC2701

 

Multi-link Multi-node PPP

RFC2716

E

PPP EAP TLS Authentication Protocol

Current Meeting Report

PPP Extensions (PPPEXT) Working Group
46th IETF--Washington, D.C.
Monday, November 8, 1999, 1930-2200

Chair: Karl Fox <karl@extant.net>
Reported by Matt Holdrege <holdrege@lucent.com>
57 people were in attendance

VPN Interoperability Workshop Announcement
Anita Freeman <anfreema@cisco.com>
The 10th PPP Workshop plus 8th IPsec Workshop will meet together in San Diego on Jan 9-14th.

PPP Bridge Control Protocol
draft-ietf-pppext-bcp-01.txt
Mitsuru Higashiyama <Mitsuru.Higashiyama@yy.anritsu.co.jp>
The old BCP is from 1994 as RFC 1638. IEEE 802 has standardized many Bridge Management Protocols. 802.1Q standardized Virtual LAN's supporting STP, GARP multicast registrations protocols (GMRP, GARP VLAN registrations protocol (GVRP) and others. Tinygram-Compression option is obsoleted in the draft. 802.3 Frames with VLAN tagging adds new fields to the Ethernet header. Backwards compatibility, but the new BCP can handle the old STP protocol. This covers 802.1Q and 802.1D COS. Supports multiple bridge management protocols with one general format.

Allows easy support by LAN switches with high-speed hardware logic. We had a discussion about using a different protocol (BCPv2) or the version-id as described in this draft.

We will add an option for 802.1Q in a new format. The PID will stay the same. The draft will be updated. It was also decided to not obsolete tinygram-compression. Implementations can reject tinygram-compression if they do not wish to support it.

PPP Multiplexing
draft-ietf-pppext-pppmux-00.txt
Irfan Ali <fia225@email.mot.com>
Rahesth Pazhyannur pazhyannr@cig.mot.com
Craig Fox fox@cisco.com

Objective: Reduce PPP frame overhead 5-7 bytes per each RTP/UDP packet. This is for VoIP over cellular infrastructure networks such as T1 lines between BSC's and MSC's. The authors were recommended to look at the RMOA in the ATM forum which might employ similar techniques. The usefulness of this protocol will depend on the cellular infrastructure employed and bandwidth financial concerns.

draft-simpson-des-as-01.txt
Bill Simpson
We had a discussion on moving PPP DES Encryption Protocol (RFC 2419) to Historic status. Since everyone has moved towards triple-DES, RFC 2419 will move to Historic.

Discussion of PPPEXT Standards Track Document Status
Karl Fox <karl@extant.net>
L2TP work has moved to the L2TP Extensions WG
SDL is in the IESG for approval as an Experimental RFC
AODI is being commented on, on the list.
The rest of the RFC's on the PPP charter need to be moved forward as planned.

Draft-ietf-pppext-secure-ra-00.txt
Pyda Srisuresh srisuresh@yahoo.com
This talk was supposed to be as part of the L2TP WG, but the author isn't able to make that session so he presented it here. This draft provides link-level authentication authorization and accounting services.

Static/Dynamic IP address assignment to a remote user from an enterprise address pool

Provides host-route connectivity to remote user and monitors link status.
Uses RADIUS to provide the AAA services so it can scale to a large number of remote users.

Proposed LNS RADIUS attributes are IPSEC_MANDATE, SECURITY_PROFILE and IKE_NEGOTIATED_PROFILE.

The group didn't think his was a PPPEXT item as it doesn't extend PPP and perhaps not a L2TPEXT work item for the same reason. It is perhaps an IPsec policy issue.

Slides

PPP Bridge Control Protocol
VPN Interoperability Workshop
ATM access network extensions
L2TP Overhead