From owner-ietf-ppp-outgoing@merit.edu  Thu Nov  2 06:36:41 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16601
	for <pppext-archive@odin.ietf.org>; Thu, 2 Nov 2000 06:36:41 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id E86CB5DDB9; Thu,  2 Nov 2000 06:36:06 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D51675DDBD; Thu,  2 Nov 2000 06:36:06 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 288725DDB9
	for <ietf-ppp@merit.edu>; Thu,  2 Nov 2000 06:36:05 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16331;
	Thu, 2 Nov 2000 06:36:03 -0500 (EST)
Message-Id: <200011021136.GAA16331@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ppp@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pppext-mppe-05.txt
Date: Thu, 02 Nov 2000 06:36:03 -0500
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

--NextPart

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		: Microsoft Point-To-Point Encryption (MPPE) Protocol
	Author(s)	: G. Pall, G. Zorn
	Filename	: draft-ietf-pppext-mppe-05.txt
	Pages		: 12
	Date		: 01-Nov-00
	
The Point-to-Point Protocol (PPP) [1] provides a standard method
for transporting multi-protocol datagrams over point-to-point
links.

The PPP Compression Control Protocol [2] provides a method to
negotiate and utilize compression protocols over PPP encapsulated
links.

This document describes the use of the Microsoft Point to Point
Encryption (MPPE) to enhance the confidentiality of PPP-
encapsulated packets.

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

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-mppe-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pppext-mppe-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001101143729.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-mppe-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pppext-mppe-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001101143729.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Thu Nov  2 06:37:24 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA16874
	for <pppext-archive@odin.ietf.org>; Thu, 2 Nov 2000 06:37:23 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 52A395DE0C; Thu,  2 Nov 2000 06:36:55 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2E3A55DE19; Thu,  2 Nov 2000 06:36:55 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 6B5D95DE0C
	for <ietf-ppp@merit.edu>; Thu,  2 Nov 2000 06:36:52 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16690;
	Thu, 2 Nov 2000 06:36:51 -0500 (EST)
Message-Id: <200011021136.GAA16690@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ppp@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pppext-mppe-keys-03.txt
Date: Thu, 02 Nov 2000 06:36:50 -0500
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

--NextPart

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		: Derivating Keys for use with Microsoft Point-to-Point 
                          Encryption (MPPE)
	Author(s)	: G. Zorn
	Filename	: draft-ietf-pppext-mppe-keys-03.txt
	Pages		: 20
	Date		: 01-Nov-00
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.

The PPP Compression Control Protocol [2] provides a method to negotiate
and utilize compression protocols over PPP encapsulated links.

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

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-mppe-keys-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pppext-mppe-keys-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Thu Nov  2 14:38:35 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA29409
	for <pppext-archive@odin.ietf.org>; Thu, 2 Nov 2000 14:38:34 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id DE0DB5DDAE; Thu,  2 Nov 2000 14:38:09 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id CCDA25DDAD; Thu,  2 Nov 2000 14:38:09 -0500 (EST)
Received: from nl-imail01.cmg.nl (nl-mail-dmz.cmg-gecis.nl [195.109.155.100])
	by segue.merit.edu (Postfix) with SMTP id 8F5F75DD91
	for <ietf-ppp@merit.edu>; Thu,  2 Nov 2000 14:38:07 -0500 (EST)
Received: FROM nl-iscan.cmg.nl BY nl-imail01.cmg.nl ; Thu Nov 02 20:36:57 2000 +0100
Received: FROM nl-amv-route01.cmg.nl BY nl-iscan.cmg.nl ; Thu Nov 02 20:33:21 2000 +0100
Received: from nl-irelay.cmg.nl (NL-IRELAY [10.16.67.60]) by nl-amv-route01.cmg.nl with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39)
	id WD5NSS13; Thu, 2 Nov 2000 20:33:17 +0100
Received: from mail pickup service by nl-irelay.cmg.nl with Microsoft SMTPSVC;
	 Thu, 2 Nov 2000 20:30:14 +0100
Received: from loki.ietf.org ([132.151.1.177]) by nl-irelay.cmg.nl with Microsoft SMTPSVC(5.0.2195.1600);	 Thu, 2 Nov 2000 17:11:05 +0100
Received: (from adm@localhost)	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA27507	for ietf-123-outbound.09@ietf.org; Thu, 2 Nov 2000 09:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA26164	for <all-ietf@loki.ietf.org>; Thu, 2 Nov 2000 06:36:51 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16690;	Thu, 2 Nov 2000 06:36:51 -0500 (EST)
Message-Id: <200011021136.GAA16690@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ppp@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pppext-mppe-keys-03.txt
Date: Thu, 02 Nov 2000 06:36:50 -0500
X-OriginalArrivalTime: 02 Nov 2000 16:11:05.0505 (UTC) FILETIME=[80C74110:01C044E7]
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

--NextPart

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		: Derivating Keys for use with Microsoft Point-to-Point 
                          Encryption (MPPE)
	Author(s)	: G. Zorn
	Filename	: draft-ietf-pppext-mppe-keys-03.txt
	Pages		: 20
	Date		: 01-Nov-00
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.

The PPP Compression Control Protocol [2] provides a method to negotiate
and utilize compression protocols over PPP encapsulated links.

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

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-mppe-keys-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pppext-mppe-keys-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

--OtherAccess--

--NextPart--




--9B095B5ADSN=_01C044DC88685DA000001765nl?irelay.cmg.nl--



From owner-ietf-ppp-outgoing@merit.edu  Fri Nov  3 05:07:22 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA21541
	for <pppext-archive@odin.ietf.org>; Fri, 3 Nov 2000 05:07:21 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 3D98C5DDF2; Fri,  3 Nov 2000 05:06:57 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 268425DD9C; Fri,  3 Nov 2000 05:06:57 -0500 (EST)
Received: from nl-imail01.cmg.nl (nl-mail-dmz.cmg-gecis.nl [195.109.155.100])
	by segue.merit.edu (Postfix) with SMTP id 1DBDA5DDFA
	for <ietf-ppp@merit.edu>; Fri,  3 Nov 2000 05:06:55 -0500 (EST)
Received: FROM nl-iscan.cmg.nl BY nl-imail01.cmg.nl ; Fri Nov 03 11:09:35 2000 +0100
Received: FROM nl-amv-route01.cmg.nl BY nl-iscan.cmg.nl ; Fri Nov 03 11:08:17 2000 +0100
Received: from nl-irelay.cmg.nl (NL-IRELAY [10.16.67.60]) by nl-amv-route01.cmg.nl with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39)
	id WD5NTN0Z; Fri, 3 Nov 2000 11:09:04 +0100
Received: from mail pickup service by nl-irelay.cmg.nl with Microsoft SMTPSVC;
	 Fri, 3 Nov 2000 11:06:27 +0100
Received: from loki.ietf.org ([132.151.1.177]) by nl-irelay.cmg.nl with Microsoft SMTPSVC(5.0.2195.1600);	 Thu, 2 Nov 2000 17:11:05 +0100
Received: (from adm@localhost)	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA27507	for ietf-123-outbound.09@ietf.org; Thu, 2 Nov 2000 09:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28])	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA26164	for <all-ietf@loki.ietf.org>; Thu, 2 Nov 2000 06:36:51 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16690;	Thu, 2 Nov 2000 06:36:51 -0500 (EST)
Message-Id: <200011021136.GAA16690@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ppp@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pppext-mppe-keys-03.txt
Date: Thu, 02 Nov 2000 06:36:50 -0500
X-OriginalArrivalTime: 02 Nov 2000 16:11:05.0505 (UTC) FILETIME=[80C74110:01C044E7]
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

--NextPart

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		: Derivating Keys for use with Microsoft Point-to-Point 
                          Encryption (MPPE)
	Author(s)	: G. Zorn
	Filename	: draft-ietf-pppext-mppe-keys-03.txt
	Pages		: 20
	Date		: 01-Nov-00
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.

The PPP Compression Control Protocol [2] provides a method to negotiate
and utilize compression protocols over PPP encapsulated links.

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

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-mppe-keys-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-mppe-keys-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pppext-mppe-keys-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001101145210.I-D@ietf.org>

--OtherAccess--

--NextPart--








From owner-ietf-ppp-outgoing@merit.edu  Fri Nov 10 11:41:15 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01916
	for <pppext-archive@odin.ietf.org>; Fri, 10 Nov 2000 11:41:15 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 8C97D5DE01; Fri, 10 Nov 2000 11:40:38 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7B51D5DDCB; Fri, 10 Nov 2000 11:40:38 -0500 (EST)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104])
	by segue.merit.edu (Postfix) with ESMTP id 5916E5DDC6
	for <ietf-ppp@merit.edu>; Fri, 10 Nov 2000 11:40:36 -0500 (EST)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e4.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA382000
	for <ietf-ppp@merit.edu>; Fri, 10 Nov 2000 11:40:01 -0500
From: jmartz@us.ibm.com
Received: from RCHASA28.RCHLAND.IBM.COM (d27ml103.rchland.ibm.com [9.5.39.110])
	by northrelay02.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id LAA83420
	for <ietf-ppp@merit.edu>; Fri, 10 Nov 2000 11:39:30 -0500
Importance: Normal
To: ietf-ppp@merit.edu
Subject: How to avoid getting "inappropriate" RADIUS attributes?
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OFDF949567.6A764308-ON85256993.005937F5@RCHLAND.IBM.COM>
Date: Fri, 10 Nov 2000 11:42:05 -0500
X-MIMETrack: Serialize by Router on d27ml103/27/M/IBM(Release 5.0.5 |September 22, 2000) at
 11/10/2000 10:42:06 AM,
	Serialize complete at 11/10/2000 10:42:06 AM
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 005B9A8085256993_="
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

This is a multipart message in MIME format.
--=_alternative 005B9A8085256993_=
Content-Type: text/plain; charset="us-ascii"

Sometimes you want the RADIUS server to return an attribute such as the 
Framed-IP-Address attribute. And sometimes you do not. 

For example, a PPP NAS sends an access-request for a previously 
unauthenticated link, it makes sense for the RADIUS server to return an IP 
address in an access-accept response.

However, if the NAS is doing a CHAP rechallenge for the link of an already 
authenticated/established PPP session, you certainly do not want the 
RADIUS server to attempt to allocate another IP address and return it to 
NAS in the access-accept.  The IP address has already been negotiated and 
you wouldn't change it.

Another situation where the correct behavior is not clear to me is when 
RADIUS is used with the multilink protocol (MP). As an example, suppose 
link A and link B are part of the same MP bundle. This implies that the 
same user name was used to authenticate both links. My naive expectation 
is that if RADIUS returned the IP address attribute, it should return the 
same IP address for both links. But it does not seem to work this way.

What is the commonly accepted way for a NAS to let the RADIUS server know 
it does not want an attribute? Or at least to ensure it does not get a 
different value for that attribute? Is including the attribute in the 
access-request sufficient? Is so, how would this work when using MP?

-john martz, 8-852-5539,  jmartz@us.ibm.com
IBM AS/400 TCP/IP PPP development (and stuff)

--=_alternative 005B9A8085256993_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Sometimes you want the RADIUS server to return an attribute such as the Framed-IP-Address attribute. And sometimes you do not. </font>
<br>
<br><font size=2 face="sans-serif">For example, a PPP NAS sends an access-request for a previously unauthenticated link, it makes sense for the RADIUS server to return an IP address in an access-accept response.</font>
<br>
<br><font size=2 face="sans-serif">However, if the NAS is doing a CHAP rechallenge for the link of an already authenticated/established PPP session, you certainly do not want the RADIUS server to attempt to allocate another IP address and return it to NAS in the access-accept. &nbsp;The IP address has already been negotiated and you wouldn't change it.</font>
<br>
<br><font size=2 face="sans-serif">Another situation where the correct behavior is not clear to me is when RADIUS is used with the multilink protocol (MP). As an example, suppose link A and link B are part of the same MP bundle. This implies that the same user name was used to authenticate both links. My naive expectation is that if RADIUS returned the IP address attribute, it should return the same IP address for both links. But it does not seem to work this way.</font>
<br>
<br><font size=2 face="sans-serif">What is the commonly accepted way for a NAS to let the RADIUS server know it does not want an attribute? Or at least to ensure it does not get a different value for that attribute? Is including the attribute in the access-request sufficient? Is so, how would this work when using MP?</font>
<br><font size=2 face="sans-serif"><br>
-john martz, 8-852-5539, &nbsp;jmartz@us.ibm.com<br>
IBM AS/400 TCP/IP PPP development (and stuff)<br>
</font>
--=_alternative 005B9A8085256993_=--



From owner-ietf-ppp-outgoing@merit.edu  Tue Nov 14 13:07:52 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06725
	for <pppext-archive@odin.ietf.org>; Tue, 14 Nov 2000 13:07:51 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id B28605DDE4; Tue, 14 Nov 2000 13:07:13 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A165F5DDE6; Tue, 14 Nov 2000 13:07:13 -0500 (EST)
Received: from cliff.extant.net (cliff.extant.net [12.17.197.35])
	by segue.merit.edu (Postfix) with ESMTP id E6ED55DDE4
	for <ietf-ppp@merit.edu>; Tue, 14 Nov 2000 13:07:11 -0500 (EST)
Received: from karl.extant.net (dhcp-17-sro.extant.net [216.28.121.217]) by cliff.extant.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id VLR26BW1; Tue, 14 Nov 2000 11:07:48 -0700
Message-Id: <4.3.2.7.2.20001114130415.045bac30@cliff.extant.net>
X-Sender: kfox@cliff.extant.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Nov 2000 13:06:18 -0500
To: ietf-ppp@merit.edu
From: Karl Fox <karl@extant.net>
Subject: Re: I-D ACTION:draft-ietf-pppext-pppmux-01.txt
In-Reply-To: <200010041055.GAA14888@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

We did a last call on this in July, and there has not been a single comment 
since the -01 draft was published almost six weeks ago.  I'll go ahead and 
send this up to the IESG for publication unless I hear some requests to the 
contrary in the next day or so.

Karl

At 05:55 AM 10/4/00, you wrote:
>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 Multiplexed
>        Author(s)       : R. Pazhyannur, I. Ali, G. Fox
>        Filename        : draft-ietf-pppext-pppmux-01.txt
>        Pages           : 8
>        Date            : 03-Oct-00
>        
>This draft describes a method to reduce the PPP framing overhead
>used to transport small packets over slow links. The method, PPP
>Multiplexing, sends multiple PPP encapsulated packets in a single
>PPP frame. As a result, the PPP overhead per packet is reduced.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-01.txt
>
>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-pppmux-01.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-ietf-pppext-pppmux-01.txt".
>        
>NOTE:   The mail server at ietf.org can return the document in
>        MIME-encoded form by using the "mpack" utility.  To use this
>        feature, insert the command "ENCODING mime" before the "FILE"
>        command.  To decode the response(s), you will need "munpack" or
>        a MIME-compliant mail reader.  Different MIME-compliant mail readers
>        exhibit different behavior, especially when dealing with
>        "multipart" MIME messages (i.e. documents which have been split
>        up into multiple messages), so check your local documentation on
>        how to manipulate these messages.
>                
>                
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>Content-Type: text/plain
>Content-ID:     <20001003122907.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-pppext-pppmux-01.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-01.txt>


Karl Fox <karl@extant.net>
Key fingerprint = 5B15 7260 D55E D680 0B93  4953 8A3B AB0E C05D 77A3




From owner-ietf-ppp-outgoing@merit.edu  Tue Nov 21 05:58:09 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA01082
	for <pppext-archive@odin.ietf.org>; Tue, 21 Nov 2000 05:58:09 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id CAEA45DDAA; Tue, 21 Nov 2000 05:57:32 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8F5145DDBE; Tue, 21 Nov 2000 05:57:32 -0500 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id D29DA5DDAA
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 05:57:30 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00871;
	Tue, 21 Nov 2000 05:57:24 -0500 (EST)
Message-Id: <200011211057.FAA00871@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rohc@cdt.luth.se, ietf-ppp@merit.edu
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rohc-over-ppp-00.txt
Date: Tue, 21 Nov 2000 05:57:24 -0500
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Robust Header Compression Working Group of the IETF.

	Title		: ROHC over PPP
	Author(s)	: C. Bormann
	Filename	: draft-ietf-rohc-over-ppp-00.txt
	Pages		: 7
	Date		: 20-Nov-00
	
This document describes an option for negotiating the use of robust
header compression (ROHC) on IP datagrams transmitted over the Point-
to-Point Protocol [RFC1661]. It defines extensions to the PPP Control
Protocols for IPv4 and IPv6 [RFC1332, RFC2023].

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

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-rohc-over-ppp-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rohc-over-ppp-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20001120151519.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rohc-over-ppp-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rohc-over-ppp-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20001120151519.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Tue Nov 21 08:43:03 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29192
	for <pppext-archive@odin.ietf.org>; Tue, 21 Nov 2000 08:43:03 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 691EA5DD95; Tue, 21 Nov 2000 08:42:36 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 56B135DDA0; Tue, 21 Nov 2000 08:42:36 -0500 (EST)
Received: from mail.via-net.net (unknown [208.46.234.15])
	by segue.merit.edu (Postfix) with ESMTP id 216E95DD95
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 08:42:35 -0500 (EST)
Received: from karl.xc.org (ppp020.via-net.net [208.46.234.147])
          by mail.via-net.net (Post.Office MTA v3.5.3 release 223
          ID# 0-52517U2500L250S0V35) with ESMTP id net;
          Tue, 21 Nov 2000 08:42:59 -0500
Message-Id: <4.3.2.7.2.20001121082717.05940c80@127.0.0.1>
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 21 Nov 2000 08:31:27 -0500
To: ietf-ppp@merit.edu
From: Karl Fox <karl@xc.org>
Subject: PPPEXT meeting at San Diego
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

The PPPEXT Working Group will meet at the San Diego IETF on Tuesday, 
December 12 between 1700 and 1800.  Having only a one-hour time slot, we 
will have relatively few presentations.  If you would like to make a 
presentation, please send me the following:

1) Your name and e-mail address
2) The name of your I-D
3) How many minutes you want
4) A really good reason why I should pick you over someone else

Early submissions will be given a slight preference.  I promise you that we 
won't have time for everyone.

Karl

Karl Fox <karl@xc.org>
  Key fingerprint = 4159 B4AD 339D 4E2A 255F  9CC4 9DA9 CB4B B16D E2B1




From owner-ietf-ppp-outgoing@merit.edu  Tue Nov 21 12:06:48 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12764
	for <pppext-archive@odin.ietf.org>; Tue, 21 Nov 2000 12:06:47 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 4A5CC5DDDE; Tue, 21 Nov 2000 12:06:22 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 37DAE5DDD7; Tue, 21 Nov 2000 12:06:22 -0500 (EST)
Received: from noc1.BelWue.DE (noc1.BelWue.DE [129.143.2.1])
	by segue.merit.edu (Postfix) with ESMTP id 24CBF5DDA0
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 12:06:20 -0500 (EST)
Received: from slfmgf.rcs.sel.de (slfmgf.rcs.sel.de [192.109.76.90] (may be forged))
	by noc1.BelWue.DE with ESMTP id SAA26627
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 18:06:16 +0100 (MET)
	env-from (heckhard@rcs.sel.de)
Received: from selrcx.rcs.sel.de (selrcx.rcs.sel.de [192.109.76.92])
	by slfmgf.rcs.sel.de (8.9.3/8.9.3) with ESMTP id SAA07251
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 18:06:16 +0100 (MET)
Received: from slfdav.rcs.sel.de (slfdav.rcs.sel.de [149.204.60.13])
	by selrcx.rcs.sel.de (8.9.1/8.9.1-zfz-tak-990309) with SMTP id SAA08919
	for <ietf-ppp@merit.edu>; Tue, 21 Nov 2000 18:06:15 +0100 (MET)
Received: from slfc96 (149.204.84.96)
	by slfdav.rcs.sel.de (V5.0A-1, OpenVMS V7.2-1 Alpha);
	Tue, 21 Nov 2000 18:06:27 +0100 (MET)
Message-ID: <008d01c053dd$5bee8510$6054cc95@slfc96.rcs.sel.de>
From: "Harald Eckhardt" <heckhard@rcs.sel.de>
To: <ietf-ppp@merit.edu>
Subject: How is PPPMUX used with multiclass PPP
Date: Tue, 21 Nov 2000 18:06:14 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Based on draft-ietf-pppext-pppmux-01, I have some questions:

What is the layer 2 QoS concept of PPP together with PPPMUX ?

The question is whether (and how) it is possible to negotiate PPPMUX

for the individual classes of multiclass PPP.

What is the effect of configuring PPPMuxCP if multiclass PPP is already
negotiated ?

The intention is to get individual PPPMUX instances for each class of
multiclass PPP,

either negotiated for all classes together or negotiated on a per class
basis.

Thank you in advance for a reply.

----------------------------------------------------------------------------
-------------------------------------
Harald Eckhardt
Alcatel SEL AG
Corporate Research Center, Radio Communications Department ZFZ/R
Lorenzstr. 10, 70435 Stuttgart, Germany
Phone +49 711 821 32286 FAX +49 711 821 32185
Email: heckhard@rcs.sel.de
----------------------------------------------------------------------------
-------------------------------------





From owner-ietf-ppp-outgoing@merit.edu  Wed Nov 29 12:18:57 2000
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17519
	for <pppext-archive@odin.ietf.org>; Wed, 29 Nov 2000 12:18:57 -0500 (EST)
Received: by segue.merit.edu (Postfix)
	id 7D96C5DE1F; Wed, 29 Nov 2000 12:15:49 -0500 (EST)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 6AFEB5DE1E; Wed, 29 Nov 2000 12:15:49 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by segue.merit.edu (Postfix) with ESMTP id B38A05DDB3
	for <ietf-ppp@merit.edu>; Wed, 29 Nov 2000 12:15:47 -0500 (EST)
Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA15473
	for <ietf-ppp@merit.edu>; Wed, 29 Nov 2000 12:15:47 -0500 (EST)
Received: from pai820exch001h.wins.lucent.com (h135-14-3-59.lucent.com [135.14.3.59])
	by ihemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id MAA15451
	for <ietf-ppp@merit.edu>; Wed, 29 Nov 2000 12:15:46 -0500 (EST)
Received: by pai820exch001h.micro.lucent.com with Internet Mail Service (5.5.2650.21)
	id <WYZPNN4F>; Wed, 29 Nov 2000 12:15:46 -0500
Message-ID: <2723E6389F55D311BDC200508B129547017E214F@pai820exch003u.micro.lucent.com>
From: "Jones, Nevin R (Nevin)" <nrjones@lucent.com>
To: ietf-ppp@merit.edu, "'Karl Fox'" <karl@xc.org>
Cc: "'chris murton'" <murton@nortelnetworks.com>,
        "Jones, Nevin R (Nevin)" <nrjones@lucent.com>
Subject: RE: PPPEXT meeting at San Diego
Date: Wed, 29 Nov 2000 12:15:44 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Karl:

I would like a couple of minutes to present an update to the ID "Extending
PPP with SONET Virtual Concatenation".

> 1) Your name and e-mail address
> 
Nevin Jones

nrjones@lucent.com

> 2) The name of your I-D
> 
Extending PPP over SONET/SDH with virtual concatenation

> 3) How many minutes you want
> 
10-15mins

> 4) A really good reason why I should pick you over someone else
> 
We believe that the recently standardized technique of virtual concatenation
adds considerable payload flexibitlity to the existing POS scheme.


Nevin R. Jones

Lucent Microelectronics
Broadband IC System Architecture
Rm 7E-321
600 Mountain Avenue 
Murray Hill, NJ
07974
Ph: 908-582-5343
Fax: 908-582-4185
nrjones@lucent.com

> ----------
> From: 	Karl Fox[SMTP:karl@xc.org]
> Sent: 	Tuesday, November 21, 2000 8:31 AM
> To: 	ietf-ppp@merit.edu
> Subject: 	PPPEXT meeting at San Diego
> 
> The PPPEXT Working Group will meet at the San Diego IETF on Tuesday, 
> December 12 between 1700 and 1800.  Having only a one-hour time slot, we 
> will have relatively few presentations.  If you would like to make a 
> presentation, please send me the following:
> 
> 1) Your name and e-mail address
> 2) The name of your I-D
> 3) How many minutes you want
> 4) A really good reason why I should pick you over someone else
> 
> Early submissions will be given a slight preference.  I promise you that
> we 
> won't have time for everyone.
> 
> Karl
> 
> Karl Fox <karl@xc.org>
>   Key fingerprint = 4159 B4AD 339D 4E2A 255F  9CC4 9DA9 CB4B B16D E2B1
> 
> 



