From owner-ietf-ppp@merit.edu  Wed Aug  1 04:53:24 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 EAA22898
	for <pppext-archive@odin.ietf.org>; Wed, 1 Aug 2001 04:53:23 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id C109C91279; Wed,  1 Aug 2001 04:54:07 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 8EDE291294; Wed,  1 Aug 2001 04:54:07 -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 6B18291279
	for <ietf-ppp@trapdoor.merit.edu>; Wed,  1 Aug 2001 04:54:06 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 369A45DDA9; Wed,  1 Aug 2001 04:54:06 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by segue.merit.edu (Postfix) with ESMTP id 57C9B5DD9F
	for <ietf-ppp@merit.edu>; Wed,  1 Aug 2001 04:54:05 -0400 (EDT)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id KAA07871;
	Wed, 1 Aug 2001 10:53:54 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id KAA12211;
	Wed, 1 Aug 2001 10:53:54 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2653.19)
	id <PRWBBQTT>; Wed, 1 Aug 2001 10:54:01 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E022917E6@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: "'R. Muralidharan'" <r.muralidharan@ieee.org>, ietf-ppp@merit.edu
Subject: AW: On draft-ietf-pppext-posvcholo-04.txt
Date: Wed, 1 Aug 2001 10:53:59 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA22898

Muralidharan,

I agree with you that section 3 is not clear. It mentions only VC-3 and VC-4. VC-11/12/2 are missing.
POS ca nbe used also via these signals with and without virtual concatenation. For VC-11/12/2 the signal lable field in the VT overhead byte (bits 5 to 7) and the extended signal label in the K4 overhead byte (bit 1 wtih a multi frame) str relevant. The signal label field shall have the code "101" (escape code to extended signal label field) and the extended signal label field shall have the code OAhex (HDLC/PPP).
For virtual concatenation in addition bit 2 of the K4 overhead byte is relevant as a multi frame counter and communication channel for LCAS.
The signal lable with and without virtual cocnatenation is the same.

Section 2 should also include some examples for VC-11/12/2 (e.g. 10 Mbit/s transport).

Regards

Juergen


> -----Ursprüngliche Nachricht-----
> Von: R. Muralidharan [mailto:raghavan_muralidharan@yahoo.com]
> Gesendet: Mittwoch, 25. Juli 2001 14:24
> An: ietf-ppp@merit.edu
> Betreff: On draft-ietf-pppext-posvcholo-04.txt
> 
> 
> 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
> 


From owner-ietf-ppp@merit.edu  Thu Aug  2 22:10:47 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 WAA09782
	for <pppext-archive@odin.ietf.org>; Thu, 2 Aug 2001 22:10:46 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id DAA5F91325; Thu,  2 Aug 2001 22:11:09 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 9FC8591322; Thu,  2 Aug 2001 22:11:09 -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 656D691326
	for <ietf-ppp@trapdoor.merit.edu>; Thu,  2 Aug 2001 22:11:02 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3CB665DE05; Thu,  2 Aug 2001 22:11:02 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from postoffice.sarnoff.com (postoffice.sarnoff.com [130.33.10.147])
	by segue.merit.edu (Postfix) with ESMTP id B9AD45DE04
	for <ietf-ppp@merit.edu>; Thu,  2 Aug 2001 22:11:01 -0400 (EDT)
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHGZ3Z00.JCV for <ietf-ppp@merit.edu>; Thu, 2 Aug 2001
          22:04:47 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5T2400.GHG; Fri, 27 Jul 2001 21:20:28 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id OAA22451;
	Tue, 24 Jul 2001 14:18:21 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA19937
	for ietf-123-outbound.05@ietf.org; Tue, 24 Jul 2001 14:05:00 -0400 (EDT)
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 GAA12898
	for <all-ietf@loki.ietf.org>; Tue, 24 Jul 2001 06:32:55 -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  Fri Aug  3 04:55:49 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 EAA09441
	for <pppext-archive@odin.ietf.org>; Fri, 3 Aug 2001 04:55:48 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id C043C91335; Fri,  3 Aug 2001 04:56:33 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 5CF6C91331; Fri,  3 Aug 2001 04:56:33 -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 C055B91335
	for <ietf-ppp@trapdoor.merit.edu>; Fri,  3 Aug 2001 04:56:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9FB825DDDA; Fri,  3 Aug 2001 04:56:30 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from postoffice.sarnoff.com (postoffice.sarnoff.com [130.33.10.147])
	by segue.merit.edu (Postfix) with ESMTP id 5DA5A5DDC9
	for <ietf-ppp@merit.edu>; Fri,  3 Aug 2001 04:56:30 -0400 (EDT)
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHHFE900.QP9 for <ietf-ppp@merit.edu>; Fri, 3 Aug 2001
          03:56:33 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5T2400.GHG; Fri, 27 Jul 2001 21:20:28 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id OAA22451;
	Tue, 24 Jul 2001 14:18:21 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA19937
	for ietf-123-outbound.05@ietf.org; Tue, 24 Jul 2001 14:05:00 -0400 (EDT)
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 GAA12898
	for <all-ietf@loki.ietf.org>; Tue, 24 Jul 2001 06:32:55 -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  Fri Aug  3 13:00:34 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 NAA21286
	for <pppext-archive@odin.ietf.org>; Fri, 3 Aug 2001 13:00:34 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 2982E91346; Fri,  3 Aug 2001 12:58:02 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id F2F369134A; Fri,  3 Aug 2001 12:58:01 -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 3BD6491346
	for <ietf-ppp@trapdoor.merit.edu>; Fri,  3 Aug 2001 12:57:58 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 1E4D45DE04; Fri,  3 Aug 2001 12:57:58 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by segue.merit.edu (Postfix) with ESMTP id 935665DDE3
	for <ietf-ppp@merit.edu>; Fri,  3 Aug 2001 12:57:57 -0400 (EDT)
Received: from eastmail2.East.Sun.COM ([129.148.1.241])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA00376
	for <ietf-ppp@merit.edu>; Fri, 3 Aug 2001 10:57:54 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA12007
	for <ietf-ppp@merit.edu>; Fri, 3 Aug 2001 12:57:55 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.11.4+Sun/8.11.4) id f73GwhU13497;
	Fri, 3 Aug 2001 12:58:43 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15210.55363.80339.251678@gargle.gargle.HOWL>
Date: Fri, 3 Aug 2001 12:58:43 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: pppext <ietf-ppp@merit.edu>
Subject: Experimental EAP implementation with SRP-SHA1
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

I've coded up and tested an EAP implementation with support for the
required MD5-Challenge method as well as the new SRP-SHA1 (-03 draft).
The implementation is based on ANU PPP-2.4.1 (maintained by Paul
Mackerras).  It consists of a set of patches for ANU PPP, and depends
on the use of Thomas Wu's SRP implementation.

I've tested it on Linux (2.2 kernel, not that I think it matters) and
Solaris 9 beta, with libsrp-1.7.3 and openssl-0.9.6.  It implements
the optional "pseudonym" feature as well.

	ftp://playground.sun.com/pub/eap/index.html

-- 
James Carlson, Internet Engineering       <james.d.carlson@east.sun.com>
SUN Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677


From owner-ietf-ppp@merit.edu  Sat Aug 18 19:42:41 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16488
	for <pppext-archive@odin.ietf.org>; Sat, 18 Aug 2001 19:42:40 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id B83BF9123B; Sat, 18 Aug 2001 19:43:26 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 905989123E; Sat, 18 Aug 2001 19:43:26 -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 4DBE09123B
	for <ietf-ppp@trapdoor.merit.edu>; Sat, 18 Aug 2001 19:43:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2FA765DDAC; Sat, 18 Aug 2001 19:43:24 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 1724D5DD98
	for <ietf-ppp@merit.edu>; Sat, 18 Aug 2001 19:43:23 -0400 (EDT)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id QAA14099
	for <ietf-ppp@merit.edu>; Sat, 18 Aug 2001 16:36:20 -0700 (PDT)
	(envelope-from aboba@internaut.com)
Date: Sat, 18 Aug 2001 16:36:20 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: ietf-ppp@merit.edu
Subject: 2nd Notice: EAP Implementation Survey
Message-ID: <Pine.BSF.4.21.0108181634540.14094-100000@internaut.com>
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

This is the second notice relating to the EAP Implementation survey
required for RFC 2284bis. If you have not already filled out the survey
relating to your EAP implementation, please do so now. 



                        EAP Implementation Survey
                        -------------------------

Please fill this out and return it to aboba@internaut.com by September 21, 2001.

For EAP (RFC 2284) to advance to Draft Standard, every feature must have at
least two independent implementations, or must be cut from the draft.
I'm putting together the RFC 2284bis document.  Please read these directions
carefully and email your answers to me directly, not to the list.

I only need a reply to this if your implementation is INDEPENDENT, that
is, not based on another implementation. If you started out once upon
a time with another code base and eventually replaced all the code
with fresh code, that counts as independent.  If you did your
implementation from scratch, better yet.

Please provide contact information and fill out the Company, Product
and Version fields following their colons, and mark the features
with a Y or N *before* the feature, and keep the spelling and order
exactly as they are here (so I can automate processing the results).
Lines starting with __ are headers and should not be marked.

Y means you support that feature in your EAP implementation NOW, N means you
do not.  No fair saying you'll be adding it later, it has to be in your
implementation that's already done and being used somewhere, although
beta or experimental software counts as in use, as long as its actually
running.

If you make both an EAP client and access device, please send in
two submissions (as two separate email messages), one for each.
If you make different flavors of access device (say, a switch,
access point and NAS), but they have the same EAP implementation,
you only need to send me an entry for one flavor. Similarly,
if you ship multiple client implementations, but they are using
the same code base, just send me one entry.

Contact name:
Contact email address:
Contact phone number:
Company name:
Product Name:
Product Version:
Client or Access Device (only one per entry):
Media Type(s) Supported (PPP, IEEE 802, Bluetooth, Other):
If Other, please describe:

__ Configuration Option
LCP Configuration option (C227) supported

__ Message Codes supported:
Request
Response
Success
Failure

__ EAP Types supported:
Identity
Notification
Nak (Response only)
MD5-Challenge
One-Time Password (OTP) (RFC 1938)
Generic Token Card

__ Length field check
Octets outside the range of the Length field ignored on reception

__ Request and Response messages
One Type specified per EAP Request or Response
Type field of the Response same as the Type of the Request (except Nak)
Authenticator transmits Request
Peer sends a Response packet in reply to a Request
Responses not retransmitted on a timer
Identifier field of Response matches that of the Request
Retransmitted Request sent with same Identifier value
New (non-retransmission) Requests modify the Identifier field
Additional Requests sent until a valid Response is received, or
  retry counter expires
Retransmission timer of 6 seconds with a maximum
  of 10 retransmissions used as default
Peer silently discards received retransmissions while waiting for
  user input

__ Success and Failure messages
Success packet is sent by the authenticator to the peer
Success packet is not sent by peer to authenticator
Success packet acknowledges successful authentication
Success packet sent with Code field set to 3
Failure packet is sent by the authenticator to the peer
Failure packet is not sent by peer to authenticator
Failure packet acknowledges unsuccessful authentication
Failure packet sent with Code field set to 4
Authenticator issues multiple Requests before sending a Failure
Peer allows for loss of Success and Failure packets
Peer uses Network protocol packet as alternative indication of Success
Peer uses receipt of LCP Terminate-Request as alternative indication of
Failure

__Identity type
Identity Request can contain a displayable message
Identity field is not null terminates
Length of identity field derived from Length field
Identity can be bypassed
If Identity is unknown, Identity Response is zero bytes in length
Authenticator retries Identity Request
Identity Request retried a minimum of 3 times before termination
Failure indicated within new Identity Request

__ Notification type
Peer displays Notification to the user
Peer logs Notification if it cannot be displayed
Notification request used to indicate invalid authentication attempt
Notification is not null terminated
Length of notification field derived from Length field
Response sent in reply to Notification Request
The Type-Data field of Notification Response is zero octets in length
Notification Response sent immediately (independent of display or logging)

__ Nak type
Nak Type sent in Response
Nak Type NOT sent in a Request
Nak Type-data field contains single octet indicating desired auth type

__ MD5-Challenge type
MD5-Challenge Response can be sent in reply to MD5-Challenge Request
Nak message can be sent in reply to MD5-Challenge Request

__ OTP type
Request contains OTP challenge
Request is not null terminated
Length of Request derived from Length field
Type 5 (OTP) Response can be sent in reply to the Request
Type 3 (Nak) Response can be sent in reply to the Request

__ Generic Token Card type
Request contains displayable message greater than zero octets in length
Length of message determined by length field
Request is not null terminated
Type 6 (GTC) response can be sent in reply to GTC Request
Type 3 (Nak) response can be sent in reply to GTC Request

__ Security considerations
Upon authentication failure, link is terminated
Upon authentication failure, traffic limited to filtered subset
Counters used for authentication failure not reset until after
   successful authentication, link termination
For each named user support for exactly one authentication method





From owner-ietf-ppp@merit.edu  Sat Aug 18 22:30:36 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18537
	for <pppext-archive@odin.ietf.org>; Sat, 18 Aug 2001 22:30:36 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id AB6E891207; Sat, 18 Aug 2001 22:30:49 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 7D65D9123E; Sat, 18 Aug 2001 22:30:49 -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 7113B91207
	for <ietf-ppp@trapdoor.merit.edu>; Sat, 18 Aug 2001 22:30:48 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 454F55DDA2; Sat, 18 Aug 2001 22:30:48 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from internaut.com (unknown [64.38.134.99])
	by segue.merit.edu (Postfix) with ESMTP id 9CFC25DD98
	for <ietf-ppp@merit.edu>; Sat, 18 Aug 2001 22:30:47 -0400 (EDT)
Received: from localhost (aboba@localhost)
	by internaut.com (8.9.3/8.9.3) with ESMTP id TAA14282
	for <ietf-ppp@merit.edu>; Sat, 18 Aug 2001 19:23:44 -0700 (PDT)
	(envelope-from aboba@internaut.com)
Date: Sat, 18 Aug 2001 19:23:44 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
To: ietf-ppp@merit.edu
Subject: Request for review
Message-ID: <Pine.BSF.4.21.0108181923300.14276-100000@internaut.com>
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

This is a request for review of the following draft:

http://www.ietf.org/internet-drafts/draft-aboba-pppext-eapgss-06.txt

Comments welcome. 




From owner-ietf-ppp@merit.edu  Sun Aug 19 07:45:20 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11076
	for <pppext-archive@odin.ietf.org>; Sun, 19 Aug 2001 07:45:20 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 2DF5D91242; Sun, 19 Aug 2001 07:46:00 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id EBBE291243; Sun, 19 Aug 2001 07:45:59 -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 D975691242
	for <ietf-ppp@trapdoor.merit.edu>; Sun, 19 Aug 2001 07:45:58 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BE2BC5DD9A; Sun, 19 Aug 2001 07:45:58 -0400 (EDT)
Delivered-To: ietf-ppp@merit.edu
Received: from arianne.in.ishoni.com (unknown [164.164.83.132])
	by segue.merit.edu (Postfix) with ESMTP id 3FE235DD95
	for <ietf-ppp@merit.edu>; Sun, 19 Aug 2001 07:45:56 -0400 (EDT)
Received: from leonoid.ishoni.com (leonoid.in.ishoni.com [192.168.1.12])
	by arianne.in.ishoni.com (8.11.1/8.11.4/Ishonir2) with ESMTP id f7JBnph06774;
	Sun, 19 Aug 2001 17:19:51 +0530
Received: by leonoid.in.ishoni.com with Internet Mail Service (5.5.2653.19)
	id <RD35LR6M>; Sun, 19 Aug 2001 17:20:35 +0530
Message-ID: <E0FDC90A9031D511915D00C04F0CCD256E5997@leonoid.in.ishoni.com>
From: Rohit Khosla <rkhosla@ishoni.com>
To: "'Nurit Sprecher'" <nurit.sprecher@SeabridgeNetworks.com>,
        "'L2tp (E-mail)'" <l2tp@l2tp.net>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
Subject: RE: PPPoA/PPPoE over ATM Encapsulation Type
Date: Sun, 19 Aug 2001 17:20:35 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C128A5.2871B520"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C128A5.2871B520
Content-Type: text/plain;
	charset="windows-1255"

VC Mux

thanks,
rohit

-----Original Message-----
From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]
Sent: Sunday, August 19, 2001 6:04 PM
To: L2tp (E-mail); 'ietf-ppp@merit.edu'
Subject: PPPoA/PPPoE over ATM Encapsulation Type


Hi all,

When PPPoE/PPP is encapsulated over ATM AAL5, there are two options for
encapsulations: LLC and VC Multiplexing. 

Can someone advise me please which of the options is more common and
more popular?

Thanks in advance, Nurit.

------_=_NextPart_001_01C128A5.2871B520
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: PPPoA/PPPoE over ATM Encapsulation Type</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>VC Mux</FONT>
</P>

<P><FONT SIZE=3D2>thanks,</FONT>
<BR><FONT SIZE=3D2>rohit</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Nurit Sprecher [<A =
HREF=3D"mailto:nurit.sprecher@SeabridgeNetworks.com">mailto:nurit.sprech=
er@SeabridgeNetworks.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Sunday, August 19, 2001 6:04 PM</FONT>
<BR><FONT SIZE=3D2>To: L2tp (E-mail); 'ietf-ppp@merit.edu'</FONT>
<BR><FONT SIZE=3D2>Subject: PPPoA/PPPoE over ATM Encapsulation =
Type</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi all,</FONT>
</P>

<P><FONT SIZE=3D2>When PPPoE/PPP is encapsulated over ATM AAL5, there =
are two options for</FONT>
<BR><FONT SIZE=3D2>encapsulations: LLC and VC Multiplexing. </FONT>
</P>

<P><FONT SIZE=3D2>Can someone advise me please which of the options is =
more common and</FONT>
<BR><FONT SIZE=3D2>more popular?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks in advance, Nurit.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C128A5.2871B520--


From owner-ietf-ppp@merit.edu  Mon Aug 20 07:08:00 2001
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10889
	for <pppext-archive@odin.ietf.org>; Mon, 20 Aug 2001 07:07:55 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
	id 6D9E29121C; Mon, 20 Aug 2001 07:08:54 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
	id 3B9BC91248; Mon, 20 Aug 2001 07:08:54 -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 1F0C09121C
	for <ietf-ppp@trapdoor.merit.edu>; Mon, 20 Aug 2001 07:08:53 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F17CD5DDE1; Mon, 20 Aug 2001 07:08:52 -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 6DF205DDE0
	for <ietf-ppp@merit.edu>; Mon, 20 Aug 2001 07:08:52 -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 HAA10798;
	Mon, 20 Aug 2001 07:07:31 -0400 (EDT)
Message-Id: <200108201107.HAA10798@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-ttls-00.txt
Date: Mon, 20 Aug 2001 07:07:30 -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		: EAP Tunneled TLS Authentication Protocol (EAP-TTLS)
	Author(s)	: P. Funk, S. Blake-Wilson
	Filename	: draft-ietf-pppext-eap-ttls-00.txt
	Pages		: 38
	Date		: 17-Aug-01
	
EAP-TTLS is an EAP protocol that extends EAP-TLS. In EAP-TLS, a TLS 
handshake is used to mutually authenticate a client and server. EAP-
TTLS extends this authentication negotiation by using the secure 
connection established by the TLS handshake to exchange additional 
information between client and server.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-eap-ttls-00.txt

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

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

--OtherAccess--

--NextPart--