I-D ACTION:draft-ietf-pppext-rfc2284bis-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF.

	Title		: Extensible Authentication Protocol (EAP)
	Author(s)	: L. Blunk, J. Vollbrecht, B. Aboba
	Filename	: draft-ietf-pppext-rfc2284bis-03.txt
	Pages		: 26
	Date		: 03-Apr-02
	
This document defines the Extensible Authentication Protocol (EAP), an
authentication protocol which supports multiple authentication
mechanisms. EAP typically runs directly over the link layer without
requiring IP and therefore includes its own support for in-order
delivery and retransmission. Fragmentation is not supported within EAP
itself; however, individual EAP methods may support this.  While EAP was
originally developed for use with PPP, it is also now in use with IEEE
802.

This document obsoletes RFC 2284.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-rfc2284bis-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pppext-rfc2284bis-03.txt".

I-D ACTION:draft-ietf-pppext-rfc2284bis-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF.

	Title		: Extensible Authentication Protocol (EAP)
	Author(s)	: L. Blunk, J. Vollbrecht, B. Aboba
	Filename	: draft-ietf-pppext-rfc2284bis-04.txt
	Pages		: 27
	Date		: 08-Apr-02
	
This document defines the Extensible Authentication Protocol (EAP), an
authentication protocol which supports multiple authentication
mechanisms. EAP typically runs directly over the link layer without
requiring IP and therefore includes its own support for in-order
delivery and retransmission. Fragmentation is not supported within EAP
itself; however, individual EAP methods may support this.  While EAP was
originally developed for use with PPP, it is also now in use with IEEE
802.

This document obsoletes RFC 2284.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-rfc2284bis-04.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pppext-rfc2284bis-04.txt".

Latest EAP-SKE draft

Hi.

I'd like to announce the availability of a revised draft on EAP-SKE. It
should appear shortly on the IETF ID directories.

In the meanwhile, you can grab it at: 

http://www.bell-labs.com/user/lsalgarelli/id/draft-salgarelli-pppext-eap-ske-01.txt

Comments are welcome.

Thanks
Luca

I-D ACTION:draft-salgarelli-pppext-eap-ske-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: EAP-SKE authentication and key exchange protocol
	Author(s)	: L. Salgarelli et al.
	Filename	: draft-salgarelli-pppext-eap-ske-01.txt
	Pages		: 28
	Date		: 16-Apr-02
	
This note describes EAP Shared Key Exchange (SKE), a method for
authentication of Mobile Nodes (MN) and generation of a per
session, per node EAP Master Secret.  The method applies to
scenarios where a Mobile Node (MN) is in a foreign network such as
a public 802.11 or 802.3 network that uses Home-AAA and Foreign-AAA
services.  The method requires presence of a pre-deployed
cryptographically secure shared key on the MN and its Home-AAA
server, and use of the 802.1x standard [1], Extensible
Authentication Protocol (EAP) [2] messages, and RADIUS [3]
authentication servers.  The protocol can easily be extended to
support the migration from RADIUS to DIAMETER [4].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-salgarelli-pppext-eap-ske-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-salgarelli-pppext-eap-ske-01.txt".

I-D ACTION:draft-ietf-pppext-rfc2878bis-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Point-to-Point Protocol Extensions Working Group of the IETF.

	Title		: PPP Bridging Control Protocol (BCP)
	Author(s)	: M. Higashiyama, F. Baker, T. Liao
	Filename	: draft-ietf-pppext-rfc2878bis-00.txt
	Pages		: 38
	Date		: 18-Apr-02
	
The Point-to-Point Protocol (PPP) [6] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.  PPP
defines an extensible Link Control Protocol, and proposes a family of
Network Control Protocols for establishing and configuring different
network-layer protocols.
This document defines the Network Control Protocol for establishing
and configuring Remote Bridging for PPP links.
This document obsoletes RFC 2878, which was based on the IEEE
802.1D-1993 MAC Bridge[3]. This document extends that specification
by improving support for bridge control packets.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-rfc2878bis-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pppext-rfc2878bis-00.txt".

Question about multi-class extension to multilink PPP.

PPP multiplexing and L2TP.

Hi,

Is it possible to tunnel PPP mux frames in a L2TP tunnel ?

Thanks for your help,
Francis

RE: PPP multiplexing and L2TP.

question on multilink ppp mibs

hi all,

RFC 1990 doesnot specify the relationship of the multilink ppp module
with
MIB II ifTable. Do we need to add an entry/s in the ifTable for
multilink.

Also I was not able to find any mibs associated with multilink ppp. Are
there any mibs defined, standard or otherwise, to manage the multilink
ppp layer. Should we be using
the existing ppp mibs do manage the multilink ppp layer.

thanks in advance
prakash

Re: question on multilink ppp mibs

On Wed, May 01, 2002 at 11:39:46AM -0400, Prakash Easwar wrote:
>RFC 1990 doesnot specify the relationship of the multilink ppp module
>with MIB II ifTable. Do we need to add an entry/s in the ifTable for
>multilink.

I chose the following approach...
http://www.nanog.org/mtg-0102/ppt/mibs/sld070.htm

>Also I was not able to find any mibs associated with multilink ppp. Are
>there any mibs defined, standard or otherwise, to manage the multilink
>ppp layer. Should we be using the existing ppp mibs do manage the multilink ppp layer.

You might be able to find something at http://www.mibcentral.com

Other than performance stats, we chose to just use cli for config settings:

rs(config)# ppp set ? 
 mlp-encaps-format        - Set MLP encapsulation format(Default: long format)
 mlp-frag-size            - Set size of the mlp frames under which no 
                            fragmentation is needed(Default: 1500 Bytes)
 mlp-fragq-depth          - Set the depth of mlp fragment q(default is 1000).  
 mlp-orderq-depth         - Set the depth of mlp order q(default is 1001).

Regards,
Mike MacFaden