From owner-ietf-ppp@merit.edu  Mon Jul  2 10:57:21 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11329
	for <pppext-archive@odin.ietf.org>; Mon, 2 Jul 2001 10:57:20 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id BF77191255; Mon,  2 Jul 2001 10:57:11 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 7AEDA91256; Mon,  2 Jul 2001 10:57:11 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id 5E9FD91255
	for <ietf-ppp@trapdoor.merit.edu>; Mon,  2 Jul 2001 10:57:10 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C05A25DD95; Mon,  2 Jul 2001 10:58:23 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 7C8F25DD91
	for <ietf-ppp@merit.edu>; Mon,  2 Jul 2001 10:58:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10860;
	Mon, 2 Jul 2001 10:56:45 -0400 (EDT)
Message-Id: <200107021456.KAA10860@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-lbd-03.txt
Date: Mon, 02 Jul 2001 10:56:44 -0400
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		: PPP Link Balancing Detection (LBD)
	Author(s)	: J. Carlson
	Filename	: draft-ietf-pppext-lbd-03.txt
	Pages		: 5
	Date		: 29-Jun-01
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.  PPP
also defines an extensible Link Control Protocol (LCP), that allows
the detection of optional link handling procedures, and a Multilink
procedure (MP) [2], that allows operation over multiple parallel
links.  This document defines an extension to MP called Link
Balancing Detection (LBD) and the LCP options that control this
extension.  This extension allows high-speed implementations to use
the single-NCP negotiation model of MP without requiring the cost
associated with the unneeded MP datagram buffering and reordering.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-lbd-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-lbd-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-lbd-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:	<20010629141556.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ppp@merit.edu  Tue Jul  3 06:59:16 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA25023
	for <pppext-archive@odin.ietf.org>; Tue, 3 Jul 2001 06:59:16 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 8664F912BB; Tue,  3 Jul 2001 06:59:05 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 53FB9912BC; Tue,  3 Jul 2001 06:59:05 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id 39C8F912BB
	for <ietf-ppp@trapdoor.merit.edu>; Tue,  3 Jul 2001 06:59:04 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 326685DDAA; Tue,  3 Jul 2001 07:00:19 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 93DC85DDA9
	for <ietf-ppp@merit.edu>; Tue,  3 Jul 2001 07:00:18 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24650;
	Tue, 3 Jul 2001 06:58:40 -0400 (EDT)
Message-Id: <200107031058.GAA24650@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-ppp-over-aal2-class-00.txt
Date: Tue, 03 Jul 2001 06:58:38 -0400
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		: Class Extensions for PPP over AAL2
	Author(s)	: B. Thompson, B. Buffam, T. Koren
	Filename	: draft-ietf-pppext-ppp-over-aal2-class-00.txt
	Pages		: 
	Date		: 02-Jul-01
	
PPP over AAL2 [1] defines the encapsulation that allows a PPP session to be transported over an ATM virtual circuit using the AAL2 adaptation layer. 
Using AAL2 as an adaptation layer for PPP transport over ATM provides a 
bandwidth efficient transport for IP applications that generate small 
packets. An example IP application that generates small packets is RTP 
encapsulated voice (Voice over IP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-ppp-over-aal2-class-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-pppext-ppp-over-aal2-class-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-pppext-ppp-over-aal2-class-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:	<20010702161722.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-ppp-over-aal2-class-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ppp@merit.edu  Tue Jul 10 10:27:52 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA00978
	for <pppext-archive@odin.ietf.org>; Tue, 10 Jul 2001 10:27:51 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id B537D91223; Tue, 10 Jul 2001 10:27:41 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 8115991228; Tue, 10 Jul 2001 10:27:41 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id 669A191223
	for <ietf-ppp@trapdoor.merit.edu>; Tue, 10 Jul 2001 10:27:40 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 1A2AD5DE03; Tue, 10 Jul 2001 10:29:09 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 5A01C5DDF5
	for <ietf-ppp@merit.edu>; Tue, 10 Jul 2001 10:29:08 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00828;
	Tue, 10 Jul 2001 10:27:14 -0400 (EDT)
Message-Id: <200107101427.KAA00828@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-eap-srp-03.txt
Date: Tue, 10 Jul 2001 10:27:14 -0400
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		: PPP EAP SRP-SHA1 Authentication Protocol
	Author(s)	: J. Carlson, B. Aboba, H. Haverinen
	Filename	: draft-ietf-pppext-eap-srp-03.txt
	Pages		: 25
	Date		: 09-Jul-01
	
The Extensible Authentication Protocol (EAP) [RFC2284] describes a
framework that allows the use of multiple authentication mechanisms.
This document defines an authentication mechanism for EAP called
SRP-SHA1, based on the Secure Remote Password (SRP) [RFC2945]
protocol.
EAP can be used with the Point-to-Point Protocol (PPP) [RFC1661] for
link authentication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-eap-srp-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-eap-srp-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-eap-srp-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:	<20010709103802.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-eap-srp-03.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ppp@merit.edu  Mon Jul 16 01:33:40 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA12644
	for <pppext-archive@odin.ietf.org>; Mon, 16 Jul 2001 01:33:39 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id EA9F19122A; Mon, 16 Jul 2001 01:33:40 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id BA8609122B; Mon, 16 Jul 2001 01:33:40 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id A00BE9122A
	for <ietf-ppp@trapdoor.merit.edu>; Mon, 16 Jul 2001 01:33:39 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 1CD2F5DDC6; Mon, 16 Jul 2001 01:35:19 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from smtp012.mail.yahoo.com (smtp012.mail.yahoo.com [216.136.173.32])
	by segue.merit.edu (Postfix) with SMTP id 966DD5DDA3
	for <ietf-ppp@merit.edu>; Mon, 16 Jul 2001 01:35:18 -0400 (EDT)
Received: from ext.firebox.zircon.com.au (HELO jc.yahoo.com) (203.32.160.240)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 16 Jul 2001 05:34:07 -0000
X-Apparently-From: <jacques?m?caron@yahoo.com>
Message-Id: <4.3.2.7.2.20010716152050.00c53780@pop.mail.yahoo.com>
X-Sender: jacques_m_caron@pop.mail.yahoo.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 16 Jul 2001 15:33:39 +1000
To: James Carlson <james.d.carlson@east.sun.com>
From: Jacques Caron <jacques_m_caron@yahoo.com>
Subject: Comments on draft-ietf-pppext-eap-srp-03.txt
Cc: ietf-ppp@merit.edu
In-Reply-To: <200107101427.KAA00828@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Hi,

Just read the new version. Getting good!

A few comments, though:
1. It focuses a bit too much on PPP and its associated protocols (ECP). I 
guess other implementations (such as 802.1x) and associated protocols 
(WEP...) should be at least mentionned.

2. The new lightweight challange is nice, but I still have a problem with 
the link/EAP endpoint separation when using AAA. In the case of a remote 
AAA server, the reauth should probably be end-to-end (AAA server to EAP 
client), not on the local link (this enables a home server to ensure that 
the user is still connected and that the local NAS/AP is not trying to 
cheat and bill more usage time -- to the contrary of what is said in 
section 2.8, btw).
However, this requires that the key remain local (in the AAA server). But 
one wouldn't want to preclude the use of the key for encryption either 
(even though the NAS/AP operator can then decrypt the data, it's still 
better than clear data over the air in the case of 802.11 connections). I 
still think deriving two keys (by deriving a longer key and splitting it, 
for instance) would be the better solution.

3. The E bit is not protected. Not sure if that's actually an issue (my 
tortuous mind hasn't come up with a case yet), but maybe somebody else can 
find one ;->

4. I think a quick mention of the username hiding (pseudonym) feature in 
section 1 would be a good thing. Always better to describe what you're 
talking about before that stuff popping up in the description of the 
packets :-)

Thanks,

Jacques.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



From owner-ietf-ppp@merit.edu  Mon Jul 16 07:31:12 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14961
	for <pppext-archive@odin.ietf.org>; Mon, 16 Jul 2001 07:31:12 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 3AFDA9122F; Mon, 16 Jul 2001 07:31:14 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id EF6B291230; Mon, 16 Jul 2001 07:31:13 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id 957359122F
	for <ietf-ppp@trapdoor.merit.edu>; Mon, 16 Jul 2001 07:31:08 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 56D425DDE9; Mon, 16 Jul 2001 07:32:48 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by segue.merit.edu (Postfix) with ESMTP id 335C95DDBB
	for <ietf-ppp@merit.edu>; Mon, 16 Jul 2001 07:32:47 -0400 (EDT)
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6GBVo322950
	for <ietf-ppp@merit.edu>; Mon, 16 Jul 2001 14:31:50 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T54c88c517aac158f22077@esvir02nok.nokia.com>;
 Mon, 16 Jul 2001 14:31:31 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <3MS40W6C>; Mon, 16 Jul 2001 14:31:32 +0300
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B0CEF6F@trebe003.NOE.Nokia.com>
From: henry.haverinen@nokia.com
To: james.d.carlson@east.sun.com
Cc: ietf-ppp@merit.edu
Subject: Comments on draft-ietf-pppext-eap-srp-03.txt
Date: Mon, 16 Jul 2001 14:31:28 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu


Hi James,

The new version looks pretty good to me. Many thanks!

I'm just about to leave for a vacation, and I only
have time for a quick comment. A security consideration about 
Step Two of section 3.2. occurred to me: Here the plaintext is the user 
identity, which an attacker might know. Can this known plaintext-ciphertext 
pair enable the attacker to compromize the key K? I don't know, 
I'm not familiar with this usage of SHA1.

As Jacques mentioned, it makes sense to use different keys for 
each purpose. We could use K for key derivations only, and derive 
a pseudonym hidding key, a link-layer packet security key and a 
lightweight re-authentication key from it. The AAA server would only
transport the packet security key the NAS, others would remain "end-to-end".
Therefore it would be impossible for the NAS to extract hidden pseudonyms 
or to fake lightweight re-authentications on behalf of the client. This 
would also restrict the implications of key compromises: for example even 
if the pseudonym hidding key was compromised, link layer packet security
or re-authentication would not be compromised. 

I think we could copy key derivation ideas from IKE (RFC 2409) or
TLS (RFC 2246).

Regards,
Henry


From owner-ietf-ppp@merit.edu  Tue Jul 24 06:33:21 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA06621
	for <pppext-archive@odin.ietf.org>; Tue, 24 Jul 2001 06:33:20 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 41F7691263; Tue, 24 Jul 2001 06:33:21 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 0BC4591264; Tue, 24 Jul 2001 06:33:20 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id BDF2491263
	for <ietf-ppp@trapdoor.merit.edu>; Tue, 24 Jul 2001 06:33:18 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F159C5DDCE; Tue, 24 Jul 2001 06:35:13 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 74B1B5DD9F
	for <ietf-ppp@merit.edu>; Tue, 24 Jul 2001 06:35:13 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06556;
	Tue, 24 Jul 2001 06:32:54 -0400 (EDT)
Message-Id: <200107241032.GAA06556@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-posvcholo-04.txt
Date: Tue, 24 Jul 2001 06:32:54 -0400
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		: Extending PPP over SONET/SDH, with virtual 
                          concatenation, high order and low order payloads
	Author(s)	: N. Jones, C. Murton
	Filename	: draft-ietf-pppext-posvcholo-04.txt
	Pages		: 8
	Date		: 23-Jul-01
	
The RFC 1661 Point-to-Point Protocol (PPP) [1] provides a standard
method for transporting multi-protocol datagrams over point-to-point
links. The RFC 1662 PPP in HDLC-like Framing [2] and RFC 2615 PPP
over SONET/SDH (POS) [3] documents describe the use of PPP over
Synchronous Optical Network (SONET) and Synchronous Digital
Hierarchy (SDH) circuits.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-posvcholo-04.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-posvcholo-04.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-posvcholo-04.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:	<20010723141021.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-posvcholo-04.txt

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

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

--OtherAccess--

--NextPart--




From owner-ietf-ppp@merit.edu  Thu Jul 26 10:45:50 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13916
	for <pppext-archive@odin.ietf.org>; Thu, 26 Jul 2001 10:45:49 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 59B9791225; Thu, 26 Jul 2001 03:03:31 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id A6B5991228; Thu, 26 Jul 2001 03:03:30 -0400 (EDT)
Delivered-To: ietf-ppp@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by trapdoor.merit.edu (Postfix) with ESMTP id B4EAF91225
	for <ietf-ppp@trapdoor.merit.edu>; Thu, 26 Jul 2001 03:02:31 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 623E55DDA8; Thu, 26 Jul 2001 03:04:30 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from smtp010.mail.yahoo.com (smtp010.mail.yahoo.com [216.136.173.30])
	by segue.merit.edu (Postfix) with SMTP id D39415DD9D
	for <ietf-ppp@merit.edu>; Thu, 26 Jul 2001 03:04:29 -0400 (EDT)
Received: from ppp-203-197-9-195.bom.vsnl.net.in (HELO muralidharan) (203.197.9.195)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 26 Jul 2001 07:03:04 -0000
X-Apparently-From: <raghavan?muralidharan@yahoo.com>
Message-ID: <000701c115a1$6e4ad340$1000a8c0@muralidharan>
Reply-To: "R. Muralidharan" <r.muralidharan@ieee.org>
From: "R. Muralidharan" <raghavan_muralidharan@yahoo.com>
To: <ietf-ppp@merit.edu>
Subject: On draft-ietf-pppext-posvcholo-04.txt
Date: Wed, 25 Jul 2001 17:54:13 +0530
Organization: OSS Systems India/IEEE Bombay Section
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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Hi All,

    the Fourth version of the draft states that "lower levels of VC are
defined in the telecommunications standards for use if needed". In view of
this, it is suggested that the following be considered:
Section 3 be modified to include the following info for lower order VC.
For higher order VC, SONET POH bytes C2 and H4 are used and for Low order
VC, the POH byte C2 and VT overhead byte V5 are used.

Further, when an STS-1 carries VT traffic containing POS which is virtually
concatenated,  is there special symbol for the C2 byte defined? This
condition occurs when one tries to map 10Mbps Ethernet traffic onto 7 VT1.5s
in low order VC mode.

Thanks in advance
regards,
Muralidharan

----- Original Message -----
From: <Internet-Drafts@ietf.org>
To: <IETF-Announce:>
Cc: <ietf-ppp@merit.edu>
Sent: Tuesday, July 24, 2001 4:02 PM
Subject: I-D ACTION:draft-ietf-pppext-posvcholo-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 : Extending PPP over SONET/SDH, with virtual
>                           concatenation, high order and low order payloads
> Author(s) : N. Jones, C. Murton
> Filename : draft-ietf-pppext-posvcholo-04.txt
> Pages : 8
> Date : 23-Jul-01
>
> The RFC 1661 Point-to-Point Protocol (PPP) [1] provides a standard
> method for transporting multi-protocol datagrams over point-to-point
> links. The RFC 1662 PPP in HDLC-like Framing [2] and RFC 2615 PPP
> over SONET/SDH (POS) [3] documents describe the use of PPP over
> Synchronous Optical Network (SONET) and Synchronous Digital
> Hierarchy (SDH) circuits.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



