From Majordomo-Owner@merit.edu  Wed Jun  2 14:32:24 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07701
	for <pppext-archive@odin.ietf.org>; Wed, 2 Jun 1999 14:32:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0950444413; Wed,  2 Jun 1999 14:32:14 -0400 (EDT)
To: pppext-archive@ietf.org
From: Majordomo@merit.edu
Subject: Confirmation for subscribe ietf-ppp
Reply-To: Majordomo@merit.edu
Message-Id: <19990602183214.0950444413@segue.merit.edu>
Date: Wed,  2 Jun 1999 14:32:14 -0400 (EDT)
Sender: Majordomo-Owner@merit.edu

--

Someone (possibly you) has requested that your email address be added
to or deleted from the mailing list "ietf-ppp@segue.merit.edu".

If you really want this action to be taken, please send the following
commands (exactly as shown) back to "Majordomo@segue.merit.edu":

	auth 696e20a1 subscribe ietf-ppp pppext-archive@lists.ietf.org

If you do not want this action to be taken, simply ignore this message
and the request will be disregarded.

If your mailer will not allow you to send the entire command as a single
line, you may split it using backslashes, like so:

        auth 696e20a1 subscribe ietf-ppp \
        pppext-archive@lists.ietf.org

If you have any questions about the policy of the list owner, please
contact "ietf-ppp-approval@segue.merit.edu".

Thanks!

Majordomo@segue.merit.edu


From karl@extant.net  Wed Jun  2 14:40:26 1999
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07823
	for <pppext-archive@lists.ietf.org>; Wed, 2 Jun 1999 14:40:25 -0400 (EDT)
Received: from bluegill ([216.28.121.202]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA47EB;
          Wed, 2 Jun 1999 14:40:18 -0400
Message-Id: <4.2.0.56.19990602143924.0440e5b0@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Wed, 02 Jun 1999 14:40:08 -0400
To: pppext-archive@ietf.org
From: "Karl Fox" <karl@extant.net>
Subject: Test message
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Just testing.  Please ignore.

[1]

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


From owner-ietf-ppp@merit.edu  Thu Jun  3 11:31:29 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07039
	for <pppext-archive@odin.ietf.org>; Thu, 3 Jun 1999 11:31:25 -0400 (EDT)
Received: by segue.merit.edu (Postfix, from userid 56)
	id 42E8F44432; Thu,  3 Jun 1999 11:31:08 -0400 (EDT)
To: pppext-archive@ietf.org
From: Majordomo@merit.edu
Subject: Welcome to ietf-ppp
Reply-To: Majordomo@merit.edu
Message-Id: <19990603153108.42E8F44432@segue.merit.edu>
Date: Thu,  3 Jun 1999 11:31:08 -0400 (EDT)
Sender: owner-ietf-ppp@merit.edu

--

Welcome to the ietf-ppp mailing list!

Please save this message for future reference.  Thank you.

If you ever want to remove yourself from this mailing list,
you can send mail to <Majordomo@segue.merit.edu> with the following
command in the body of your email message:

    unsubscribe ietf-ppp

or from another account, besides pppext-archive@lists.ietf.org:

    unsubscribe ietf-ppp pppext-archive@lists.ietf.org

If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-ietf-ppp@segue.merit.edu> .
This is the general rule for most mailing lists when you need
to contact a human.

 Here's the general information for the list you've subscribed to,
 in case you don't already have it:

  IETF Point-to-Point Protocol (PPP)


From owner-ietf-ppp-outgoing@merit.edu  Thu Jun  3 13:47:07 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09902
	for <pppext-archive@odin.ietf.org>; Thu, 3 Jun 1999 13:47:06 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BFF334442A; Thu,  3 Jun 1999 13:46:24 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 93AC244432; Thu,  3 Jun 1999 13:46:24 -0400 (EDT)
Received: from hotmail.com (f245.hotmail.com [207.82.251.136])
	by segue.merit.edu (Postfix) with SMTP id 3EF3B4442A
	for <ietf-ppp@merit.edu>; Thu,  3 Jun 1999 13:46:22 -0400 (EDT)
Received: (qmail 27875 invoked by uid 0); 3 Jun 1999 17:46:21 -0000
Message-ID: <19990603174621.27874.qmail@hotmail.com>
Received: from 207.20.187.199 by wy1lg.hotmail.com with HTTP;
	Thu, 03 Jun 1999 10:46:20 PDT
X-Originating-IP: [207.20.187.199]
From: Leo Huber <leo_huber@hotmail.com>
To: carlson@ironbridgenetworks.com, ietf-ppp@merit.edu
Subject: Re: granularity of PPP timers
Date: Thu, 03 Jun 1999 10:46:20 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

thx, James for your quick response.

Looking for an answer I also purchased your book "PPP design and Debugging" 
and would like to thank you for this contribution,
which I admire and find so helpfull on many other issues,
but the one discussed in this email.

I embedded some questions in the text below:

>From: James Carlson <carlson@ironbridgenetworks.com>
>To: ietf-ppp@merit.edu
>Subject: Re: granularity of PPP timers
>Date: 03 Jun 1999 06:49:09 -0400
>
>leo_huber@hotmail.com ("Leo Huber") writes:
> > does the PPP authentication require specific
> > granularity and/or absolute (= limited variablity)
> > timer value?
>
>No.  The standard recommends timers configurable in units of seconds,
>but the authentication mechanisms do not depend on timer granularity
>or variability.  If your 3 second nominal timer varies between 3 and
>10 seconds, this will not harm negotiation.
>
>(Note that most of the timers are there only to guard against packet
>loss.  In well-designed implementations, they won't actually be
>triggered.

so the adjustement granularity of ~1 sec. (+/- 0.5 sec.)
is sufficient?

My goal is a "well-designed" implementation, therefore the
consideration for the timer value and the granularity of timer ajustment.

>The two exceptions off the top of my head are the CHAP
>rechallenge and the LQM intervals -- and the exact timing of those is
>relatively unimportant, as long as they neither happen too quickly nor too 
>slowly.)

yes. I was looking for numbers to express the feelings like
"too quickly" or "too slowly". Could not find such numbers
in your PPP book or rfc 1994 (CHAP).

in the rfc 1994 I read:

"2.1.  Advantages

   The use of repeated challenges is intended to limit
   the time of exposure to any single attack.  The authenticator is in
   control of the frequency and timing of the challenges."

does this imply time limits on the authenticatee and how to make sure
these time limits are met?

I appreciate your help.

Leo


>
>--
>James Carlson, Software Architect                   <carlson@ibnets.com>
>IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
>Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
>"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp
>





_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com



From karl@extant.net  Thu Jun  3 15:52:17 1999
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12133
	for <pppext-archive@lists.ietf.org>; Thu, 3 Jun 1999 15:52:16 -0400 (EDT)
Received: from bluegill ([209.116.97.141]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA501E;
          Thu, 3 Jun 1999 15:50:00 -0400
Message-Id: <4.2.0.56.19990603154846.00c11100@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 03 Jun 1999 15:49:38 -0400
To: pppext-archive@ietf.org
From: "Karl Fox" <karl@extant.net>
Subject: Test message [2]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Just testing.  Please ignore.

[2]

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


From owner-ietf-ppp-outgoing@merit.edu  Thu Jun  3 16:34:46 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12727
	for <pppext-archive@odin.ietf.org>; Thu, 3 Jun 1999 16:34:45 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 909574443A; Thu,  3 Jun 1999 16:34:10 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 65BF34443C; Thu,  3 Jun 1999 16:34:10 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id EE8EA4443A
	for <ietf-ppp@merit.edu>; Thu,  3 Jun 1999 16:34:08 -0400 (EDT)
Received: from bluegill ([209.116.97.141]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA5078;
          Thu, 3 Jun 1999 16:34:11 -0400
Message-Id: <4.2.0.56.19990603162522.045b0550@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 03 Jun 1999 16:34:00 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: PPPEXT Charter Update
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're in the process of updating the PPPEXT charter (at 
http://www.ietf.org/html.charters/pppext-charter.html), and are changing the 
main focus (if there is one!) from enhancements to document maturation.  
This means that we will no longer welcome new encapsulations, enhancements, 
etc. with the open arms of the past without a really, REALLY good reason to 
do so.

The primary remaining task in updating the charter is laying out the 
milestones necessary to achieve our new goal.  Which protocols should be 
moved forward on the standards track?  When?  Please offer your suggestions.

To start things rolling, here are a few for which I'm sure we'll have wide 
consensus--please also suggest target dates for the various stages of 
advancement (Proposed Standard (PS), Draft Standard (DS), Standard (S)).

PPP, IPCP, CHAP, CCP, ECP, Multilink, L2TP, L2TP MIB

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



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun  3 16:57:57 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13067
	for <pppext-archive@odin.ietf.org>; Thu, 3 Jun 1999 16:57:57 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 577D64443B; Thu,  3 Jun 1999 16:57:37 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 2EBAB4443C; Thu,  3 Jun 1999 16:57:37 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id A12474443B
	for <ietf-ppp@merit.edu>; Thu,  3 Jun 1999 16:57:35 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id QAA11700;
	Thu, 3 Jun 1999 16:57:33 -0400 (EDT)
Date: Thu, 3 Jun 1999 16:57:33 -0400 (EDT)
Message-Id: <199906032057.QAA11700@ironbridgenetworks.com>
X-Authentication-Warning: helios.helios: carlson set sender to carlson@ironbridgenetworks.com using -f
From: James Carlson <carlson@ironbridgenetworks.com>
To: leo_huber@hotmail.com
Cc: ietf-ppp@merit.edu
In-reply-to: <19990603174621.27874.qmail@hotmail.com> (message from Leo Huber
	on Thu, 03 Jun 1999 10:46:20 PDT)
Subject: Re: granularity of PPP timers
References:  <19990603174621.27874.qmail@hotmail.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> >(Note that most of the timers are there only to guard against packet
> >loss.  In well-designed implementations, they won't actually be
> >triggered.
> 
> so the adjustement granularity of ~1 sec. (+/- 0.5 sec.)
> is sufficient?

Certainly.  Many well-known versions simply hard-code the timers at
the RFC defaults and allow no adjustment at all.  Others make
adjustment only by modifying obscure (and dangerous) binary databases.
If you allow timer adjustment within 1 second, you're doing well.

(Do make sure that you use a variable back-off algorithm.  This makes
a *much* bigger difference in whether or not your implementation will
be robust.)

> >The two exceptions off the top of my head are the CHAP
> >rechallenge and the LQM intervals -- and the exact timing of those is
> >relatively unimportant, as long as they neither happen too quickly nor too 
> >slowly.)
> 
> yes. I was looking for numbers to express the feelings like
> "too quickly" or "too slowly". Could not find such numbers
> in your PPP book or rfc 1994 (CHAP).

They depend on where and how your implementation is used.  Usually,
this feature is disabled by default and has to be configured by an
administrator in order to enable it.

>    The use of repeated challenges is intended to limit
>    the time of exposure to any single attack.  The authenticator is in
>    control of the frequency and timing of the challenges."
> 
> does this imply time limits on the authenticatee and how to make sure
> these time limits are met?

If I understand your question, no, it does not imply that.  It means
only that the authenticator may -- at its option and discretion --
rechallenge its peer at any interval it feels is necessary to be sure
that the peer hasn't been replaced with another.

In truth, this can be problematic.  If the peer is in use by a human
(rather than just being a stand-alone networking box), then
rechallenge probably means annoying the user with a pop-up window to
reenter the password, or it means that the PPP implementation caches a
copy of the cleartext password (!).  Either way, it's not good to do
this very often, especially where there is another, reasonably secure
means to know that the same peer is still on the line (such as modem
carrier detect).

On the other hand, some links (such as dedicated synchronous lines)
don't have positive indication when the link is severed, and thus
rechallenge is necessary to prevent an attacker from simply splicing
some equipment into the path.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 07:33:41 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03584
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 07:33:41 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 8B13844402; Fri,  4 Jun 1999 07:33:03 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 619B744419; Fri,  4 Jun 1999 07:33:03 -0400 (EDT)
Received: from stars.cisco.com (stars.cisco.com [171.71.112.28])
	by segue.merit.edu (Postfix) with ESMTP id C70AB44402
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 07:33:01 -0400 (EDT)
Received: from jaws.cisco.com (jaws.cisco.com [198.135.1.36]) by stars.cisco.com (8.8.4-Cisco.1/8.6.5) with SMTP id EAA21208 for <ietf-ppp@merit.edu>; Fri, 4 Jun 1999 04:32:30 -0700 (PDT)
Date: Fri, 4 Jun 1999 12:32:56 +0100 (BST)
From: Gerry Meyer <gemeyer@cisco.com>
To: ietf-ppp@merit.edu
Subject: Re: PPPEXT Charter Update
Message-ID: <Pine.GSO.3.96.990604120122.7623A-100000@jaws.cisco.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

>We're in the process of updating the PPPEXT charter (at
>http://www.ietf.org/html.charters/pppext-charter.html), and are changing the
>main focus (if there is one!) from enhancements to document maturation.

Talking of documentation....
While idly scanning through the on-line Assigned Numbers for PPP:

http://www.isi.edu/in-notes/iana/assignments/ppp-numbers

I notice some inconsistencies relating to LCP and CCP.

For LCP, it has:

  21       DCE-Identifier                            [SCHNEIDER]

  25       Consistent Overhead Byte Stuffing (COBS)    [Carlson]

For CCP, it has:

25              DCE                                   [RFC1976]

However RFC 1976 has option 25 an **LCP** option:

3.  PPP Link Control Protocol Extension

   The use of PPP in Compression DCE requires the use of an additional
   LCP Configuration Option:

      25  DCE-Identifier

So LCP option 25 has two contenders for the title.
 
So what is LCP Option 21?

	Gerry





From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 14:27:48 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09401
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 14:27:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B42EC4442B; Fri,  4 Jun 1999 14:27:20 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8EEF44442F; Fri,  4 Jun 1999 14:27:20 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id A4D2C4442B
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 14:27:13 -0400 (EDT)
Received: from bluegill ([209.116.97.129]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA58A1;
          Fri, 4 Jun 1999 14:27:12 -0400
Message-Id: <4.2.0.56.19990604141836.043f3140@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Fri, 04 Jun 1999 14:27:02 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Re: PPPEXT Charter Update
In-Reply-To: <Pine.GSO.3.96.990604120122.7623A-100000@jaws.cisco.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

Ok, folks, it's up to us to decide what to do, then we'll feed that
information back to the folks at IANA.

So what do we do?

1) Make LCP option 25 be DCE-Identifier as specified by RFC 1976, assign
    COBS a new LCP option number, and free up LCP option 21 and CCP option 25
    (or apply a "hold-down" timer to them).

or

2) Make LCP option 25 be COBS, assign DCE-Identifier a new LCP option
    number, and free up the others.

Before we can make reasonable decisions, though, it would help to know
what's been implemented out there.

So here's a poll:  Who has implemented DCE compression or COBS and shipped
it to customers?

Thanks,

Karl


At 12:32 PM 6/4/99 +0100, Gerry Meyer wrote:
> >We're in the process of updating the PPPEXT charter (at
> >http://www.ietf.org/html.charters/pppext-charter.html), and are changing the
> >main focus (if there is one!) from enhancements to document maturation.
>
>Talking of documentation....
>While idly scanning through the on-line Assigned Numbers for PPP:
>
>http://www.isi.edu/in-notes/iana/assignments/ppp-numbers
>
>I notice some inconsistencies relating to LCP and CCP.
>
>For LCP, it has:
>
>   21       DCE-Identifier                            [SCHNEIDER]
>
>   25       Consistent Overhead Byte Stuffing (COBS)    [Carlson]
>
>For CCP, it has:
>
>25              DCE                                   [RFC1976]
>
>However RFC 1976 has option 25 an **LCP** option:
>
>3.  PPP Link Control Protocol Extension
>
>    The use of PPP in Compression DCE requires the use of an additional
>    LCP Configuration Option:
>
>       25  DCE-Identifier
>
>So LCP option 25 has two contenders for the title.
>  
>So what is LCP Option 21?
>
>         Gerry


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



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 16:23:08 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10670
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 16:23:07 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F21F644401; Fri,  4 Jun 1999 16:22:35 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id CA8F14443F; Fri,  4 Jun 1999 16:22:34 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id A14A344401
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 16:22:33 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id QAA02619 for ietf-ppp@merit.edu; Fri, 4 Jun 1999 16:22:33 -0400 (EDT)
Received: from srv-exchange2.adtran.com (mail-exch2.adtran.com [206.166.249.116])
	by segue.merit.edu (Postfix) with ESMTP id 2DB4344401
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 15:47:27 -0400 (EDT)
Received: by srv-exchange2.adtran.com with Internet Mail Service (5.5.2232.9)
	id <LNCZDR1F>; Fri, 4 Jun 1999 14:52:17 -0500
Message-ID: <46476C008A10D311BD0A0000C0775CF9101988@srv-exchange.adtran.com>
From: KYLE FARNSWORTH <kyle.farnsworth@adtran.com>
To: Karl Fox <karl@extant.net>, ietf-ppp@merit.edu
Subject: RE: PPPEXT Charter Update
Date: Fri, 4 Jun 1999 14:47:33 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Karl,

Adtran had a DSU product that used LCP option 25.  It turns out Adtran only
sold a few of those products and has since then been discontinued.  If there
are any of those DSU's still running they are all Adtran talking to Adtran.
I don't believe any other vendor has developed the DCE compression per
RFC1976.

So unless the authors of RFC1976 tell you different I think either option is
acceptable.

Kyle

> Ok, folks, it's up to us to decide what to do, then we'll feed that
> information back to the folks at IANA.
> 
> So what do we do?
> 
> 1) Make LCP option 25 be DCE-Identifier as specified by RFC 
> 1976, assign
>     COBS a new LCP option number, and free up LCP option 21 
> and CCP option 25
>     (or apply a "hold-down" timer to them).
> 
> or
> 
> 2) Make LCP option 25 be COBS, assign DCE-Identifier a new LCP option
>     number, and free up the others.
> 
> Before we can make reasonable decisions, though, it would help to know
> what's been implemented out there.
> 
> So here's a poll:  Who has implemented DCE compression or 
> COBS and shipped
> it to customers?
 




From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 16:23:26 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10684
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 16:23:25 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C464C4443F; Fri,  4 Jun 1999 16:22:53 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5CBBD44444; Fri,  4 Jun 1999 16:22:50 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id EAC5F44443
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 16:22:47 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id QAA02624 for ietf-ppp@merit.edu; Fri, 4 Jun 1999 16:22:47 -0400 (EDT)
Received: from flipper.cisco.com (flipper.cisco.com [171.69.63.10])
	by segue.merit.edu (Postfix) with ESMTP id B543244401
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 16:09:41 -0400 (EDT)
Received: from flipper.cisco.com (flipper.cisco.com [171.69.63.10]) by flipper.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id NAA26183; Fri, 4 Jun 1999 13:09:39 -0700 (PDT)
Date: Fri, 4 Jun 1999 13:09:38 -0700 (PDT)
From: John Bray <bray@cisco.com>
To: Karl Fox <karl@extant.net>
Cc: ietf-ppp@merit.edu
Subject: Re: PPPEXT Charter Update
In-Reply-To: <4.2.0.56.19990604141836.043f3140@mail.extant.net>
Message-ID: <Pine.GSO.3.96.990604125957.22284I-100000@flipper.cisco.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


Well, I notice the *examples* in RFC 1976 (section 5.1) use 21, not 25
for the DCE-Identifier option.  So it isn't even consistent with
itself.  James Carlson's book also lists it as 21.

John

On Fri, 4 Jun 1999, Karl Fox wrote:

> Ok, folks, it's up to us to decide what to do, then we'll feed that
> information back to the folks at IANA.
> 
> So what do we do?
> 
> 1) Make LCP option 25 be DCE-Identifier as specified by RFC 1976, assign
>     COBS a new LCP option number, and free up LCP option 21 and CCP option 25
>     (or apply a "hold-down" timer to them).
> 
> or
> 
> 2) Make LCP option 25 be COBS, assign DCE-Identifier a new LCP option
>     number, and free up the others.
> 
> Before we can make reasonable decisions, though, it would help to know
> what's been implemented out there.
> 
> So here's a poll:  Who has implemented DCE compression or COBS and shipped
> it to customers?
> 
> Thanks,
> 
> Karl
> 
> 
> At 12:32 PM 6/4/99 +0100, Gerry Meyer wrote:
> > >We're in the process of updating the PPPEXT charter (at
> > >http://www.ietf.org/html.charters/pppext-charter.html), and are changing the
> > >main focus (if there is one!) from enhancements to document maturation.
> >
> >Talking of documentation....
> >While idly scanning through the on-line Assigned Numbers for PPP:
> >
> >http://www.isi.edu/in-notes/iana/assignments/ppp-numbers
> >
> >I notice some inconsistencies relating to LCP and CCP.
> >
> >For LCP, it has:
> >
> >   21       DCE-Identifier                            [SCHNEIDER]
> >
> >   25       Consistent Overhead Byte Stuffing (COBS)    [Carlson]
> >
> >For CCP, it has:
> >
> >25              DCE                                   [RFC1976]
> >
> >However RFC 1976 has option 25 an **LCP** option:
> >
> >3.  PPP Link Control Protocol Extension
> >
> >    The use of PPP in Compression DCE requires the use of an additional
> >    LCP Configuration Option:
> >
> >       25  DCE-Identifier
> >
> >So LCP option 25 has two contenders for the title.
> >  
> >So what is LCP Option 21?
> >
> >         Gerry
> 
> 
> Karl Fox <karl@extant.net>
> Key fingerprint = 5B15 7260 D55E D680 0B93  4953 8A3B AB0E C05D 77A3
> 





From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 16:51:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11002
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 16:51:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id ECBF344442; Fri,  4 Jun 1999 16:51:18 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C653B44443; Fri,  4 Jun 1999 16:51:18 -0400 (EDT)
Received: from alpha.shiva.com (eagle-ext.shiva.com [192.80.57.28])
	by segue.merit.edu (Postfix) with ESMTP id 161D944442
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 16:51:17 -0400 (EDT)
Received: from brill.shiva.com (brill.shiva.com [140.248.193.94])
	by alpha.shiva.com (8.8.8/8.8.8) with SMTP id QAA30951
	for <ietf-ppp@merit.edu>; Fri, 4 Jun 1999 16:51:15 -0400 (EDT)
Received: by brill.shiva.com (SMI-8.6/SMI-SVR4)
	id QAA13530; Fri, 4 Jun 1999 16:51:16 -0400
Date: Fri, 4 Jun 1999 16:51:16 -0400
Message-Id: <199906042051.QAA13530@brill.shiva.com>
From: John Shriver <jas@shiva.com>
To: ietf-ppp@merit.edu
Subject: headhunters using list membership for recruiting SPAM
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Could the ietf-ppp list keeper please adjust Majordomo to totally
refuse the "who" command, rather than restricting it to list members.

(Or, possibly make a extension to Majordomo to only report members @
the same domain.  Eg. jas@shiva.com only sees marty@shiva.com, etc.)
That's useful for pruning ex-employees.)

Dear ReneP@mriexec.com, who is the next to newest member of the list
as reported by Majordomo, just sent recruiting mail to some or all of
the members of the list.  It was rather obvious what she did, since
she sent it to a local exploder here that is only used for mail from
this list.

I think we also want to remove her from the list on general
principles...

(Perhaps the fact that this is happening should be forwarded to other
IETF working group mailing list managers.)



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 21:47:29 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14689
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 21:47:28 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BC50244404; Fri,  4 Jun 1999 21:46:56 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 97CBB44406; Fri,  4 Jun 1999 21:46:56 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id B00E844404
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 21:46:53 -0400 (EDT)
Received: from bluegill ([209.116.97.129]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA5B91;
          Fri, 4 Jun 1999 21:46:56 -0400
Message-Id: <4.2.0.56.19990604214121.00bd4100@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Fri, 04 Jun 1999 21:46:41 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Current PPPEXT agenda for Oslo
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

PPP Extensions Working Group Agenda
45th IETF--Oslo, Norway

Wednesday, July 14, 1999, 1530-1730 
Opposite rmonmib, deltav, rtgarea, decides

PPP over SDL for packet over dark fiber channels
         James Carlson <carlson@ironbridgenetworks.com>
         Enrique Hernandez-Valencia <enrique@lucent.com>
         Nevin Jones <nrjones@lucent.com>
[15-20 minutes]

Discussion of PPPEXT Standards Track Document Status
      Karl Fox <karl@extant.net>
[30 minutes]


P.S.  It's not too late to get your presentation on the agenda!  First come,
first served.  Send me:

1) Name of presenter 
2) Presentation (or I-D) title 
3) I-D name (draft-ietf-....txt), if any 
4) Amount of time you need

Thanks,


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



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 22:22:42 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14925
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 22:22:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9C7E144406; Fri,  4 Jun 1999 22:22:21 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 6F10D4441E; Fri,  4 Jun 1999 22:22:21 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by segue.merit.edu (Postfix) with ESMTP id C93E744406
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 22:22:19 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.0/calcite) id UAA04132
	for ietf-ppp@merit.edu  env-from <vjs>;
	Fri, 4 Jun 1999 20:22:19 -0600 (MDT)
Date: Fri, 4 Jun 1999 20:22:19 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <199906050222.UAA04132@calcite.rhyolite.com>
To: ietf-ppp@merit.edu
Subject: Re: headhunters using list membership for recruiting SPAM
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: John Shriver <jas@shiva.com>

> Dear ReneP@mriexec.com, who is the next to newest member of the list
> as reported by Majordomo, just sent recruiting mail to some or all of
> the members of the list.  It was rather obvious what she did, since
> she sent it to a local exploder here that is only used for mail from
> this list.

So that's why I got that junk!  I wondered, since it was odd.


> I think we also want to remove her from the list on general
> principles...

Seconded.

> (Perhaps the fact that this is happening should be forwarded to other
> IETF working group mailing list managers.)

Seconded.

It seems cleanest to just turn off the majordomo who command.
Ex-employees are no more likely than entire domains that go bad
as the result of mergers and so forth.

Does the main IETF still answer the who command?  I think there were
complaints about that a year or two ago after some spam, and what seemed
to me bogus responses about the list being public and therefore the
membership list needing to be public.  I don't understand that implication
from public list to public membership roll, but even if it is valid, the
membership roll need not be available by computer.  No legitimate user of
the roll would be significantly inconvenienced by having to do things the
old fashioned, pre-computer way, by asking a human.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun  4 22:45:23 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16366
	for <pppext-archive@odin.ietf.org>; Fri, 4 Jun 1999 22:45:22 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B405A4441E; Fri,  4 Jun 1999 22:44:53 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8E81844422; Fri,  4 Jun 1999 22:44:53 -0400 (EDT)
Received: from NIH2WAAF (smtp6.site1.csi.com [149.174.183.75])
	by segue.merit.edu (Postfix) with ESMTP id C14AF4441E
	for <ietf-ppp@merit.edu>; Fri,  4 Jun 1999 22:44:51 -0400 (EDT)
Received: from mail pickup service by csi.com with Microsoft SMTPSVC;
	 Fri, 4 Jun 1999 22:44:49 -0400
Received: from mikewinslow (max3-21.newyork.corecomm.net [209.81.239.149])
	by hil-img-ims-5.compuserve.com (8.8.6/8.8.6/IMS-1.7) with SMTP id WAA12126;
	Fri, 4 Jun 1999 22:44:11 -0400 (EDT)
Reply-To: <mike_winslow@compuserve.com>
From: "mike winslow" <mike_winslow@csi.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, <ietf-ppp@merit.edu>
Subject: RE: headhunters using list membership for recruiting SPAM
Date: Fri, 4 Jun 1999 22:38:58 -0400
Message-ID: <000801beaefc$90d01460$c22dfea9@compuserve.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
In-Reply-To: <199906042223_MC2-7849-D4E6@compuserve.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

hmm.. far too complex..

I just replied that the 'six digit salary' needed to start off with the
number '2' (or more)..  Didn't hear back on it.
:)



-----Original Message-----
From: owner-ietf-ppp-outgoing@merit.edu
[mailto:owner-ietf-ppp-outgoing@merit.edu]On Behalf Of Vernon Schryver
Sent: Friday, June 04, 1999 10:23 PM
To: ietf-ppp@merit.edu
Subject: Re: headhunters using list membership for recruiting SPAM

To: ietf-ppp@merit.edu
Subject: Re: headhunters using list membership for recruiting SPAM
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: John Shriver <jas@shiva.com>

> Dear ReneP@mriexec.com, who is the next to newest member of the list
> as reported by Majordomo, just sent recruiting mail to some or all of
> the members of the list.  It was rather obvious what she did, since
> she sent it to a local exploder here that is only used for mail from
> this list.

So that's why I got that junk!  I wondered, since it was odd.


> I think we also want to remove her from the list on general
> principles...

Seconded.

> (Perhaps the fact that this is happening should be forwarded to other
> IETF working group mailing list managers.)

Seconded.

It seems cleanest to just turn off the majordomo who command.
Ex-employees are no more likely than entire domains that go bad
as the result of mergers and so forth.

Does the main IETF still answer the who command?  I think there were
complaints about that a year or two ago after some spam, and what seemed
to me bogus responses about the list being public and therefore the
membership list needing to be public.  I don't understand that implication
from public list to public membership roll, but even if it is valid, the
membership roll need not be available by computer.  No legitimate user of
the roll would be significantly inconvenienced by having to do things the
old fashioned, pre-computer way, by asking a human.


Vernon Schryver    vjs@rhyolite.com







From owner-ietf-ppp-outgoing@merit.edu  Sun Jun  6 10:12:38 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27286
	for <pppext-archive@odin.ietf.org>; Sun, 6 Jun 1999 10:12:38 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7ED7A44408; Sun,  6 Jun 1999 10:12:06 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 57AA644409; Sun,  6 Jun 1999 10:12:06 -0400 (EDT)
Received: from srv-exchange2.adtran.com (mail-exch2.adtran.com [206.166.249.116])
	by segue.merit.edu (Postfix) with ESMTP id 304BE44408
	for <ietf-ppp@merit.edu>; Sun,  6 Jun 1999 10:12:05 -0400 (EDT)
Received: by srv-exchange2.adtran.com with Internet Mail Service (5.5.2232.9)
	id <LNCZDVKV>; Sun, 6 Jun 1999 09:17:39 -0500
Message-ID: <20130E7A0510D311942D00E02900DD2411FA65@srv-exchange1.adtran.com>
From: KEVIN SCHNEIDER <kevin.schneider@adtran.com>
To: ietf-ppp@merit.edu
Subject: FW: PPPEXT Charter Update
Date: Sun, 6 Jun 1999 09:12:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> As the authors of the RFC in question, I figure we ought to chime in.
> 
> I believe this issue came up about a year ago.   At that time we
> determined that RFC 1976 is in error, and the correct LCP option for DCE
> Identifier is indeed 21.   (In fact, all of the drafts of the document
> that I can find on my computer list the option as 21 -- I don't know when
> or where it was changed.)  At that time,  I think I said that the RFC
> needed to be corrected, someone said that RFCs are never corrected, only
> superceded, and that was how it ended.
> 
> We occasionally ship DSU's with compression.  When a pair of these units
> are connected to a DDS line, the protocol on the line looks like a router
> bringing up LCP and CCP but it is not.  Instead, it is a session between
> the two DSU's.  The DCE identifier is included in the LCP negotiation to
> prevent
> confusion in case one end is connected directly to a router instead of to
> a compression DSU.  We believe that 21 is the proper option used for this
> purpose.
> 
> I have no idea why 25 is listed under CCP.  (Perhaps IANA was confused by
> the presence of 25 in RFC 1976 as well, or someone didn't realize that RFC
> 1976 superceded the SCHNEIDER reference.)   23 is the number for LZS-DCP,
> and I think that is the only number from the DSU application that applies
> to CCP.  RFC 1963 and 1967 are the other two RFCs that apply to this
> application.  One describes SDTP/SDCP and the other LZS-DCP.
> 
The right thing to do is fix RFC 1976 to match Assigned Numbers and
implementation, change LCP option 21 to reference the fixed version of RFC
1976 in the Assigned numbers  and remove the Assigned numbers reference to
25 in the CCP section. 

I will also note that these were some of the documents that stayed in the
draft stage well beyond their expiration date due to the CCP patent mess.
The long delay between their submission and publication may have contributed
to this problem.

> I hope that this clears things up.
> 
> Kevin
> >
> > > ----------
> > > From:         John Bray[SMTP:bray@cisco.com]
> > > Sent:         Friday, June 4, 1999 3:09 PM
> > > To:   Karl Fox
> > > Cc:   ietf-ppp@merit.edu
> > > Subject:      Re: PPPEXT Charter Update
> > > 
> > > 
> > > Well, I notice the *examples* in RFC 1976 (section 5.1) use 21, not 25
> > > for the DCE-Identifier option.  So it isn't even consistent with
> > > itself.  James Carlson's book also lists it as 21.
> > > 
> > > John
> > > 
> > > On Fri, 4 Jun 1999, Karl Fox wrote:
> > > 
> > > > Ok, folks, it's up to us to decide what to do, then we'll feed that
> > > > information back to the folks at IANA.
> > > > 
> > > > So what do we do?
> > > > 
> > > > 1) Make LCP option 25 be DCE-Identifier as specified by RFC 1976,
> assign
> > > >     COBS a new LCP option number, and free up LCP option 21 and CCP
> > > option 25
> > > >     (or apply a "hold-down" timer to them).
> > > > 
> > > > or
> > > > 
> > > > 2) Make LCP option 25 be COBS, assign DCE-Identifier a new LCP
> option
> > > >     number, and free up the others.
> > > > 
> > > > Before we can make reasonable decisions, though, it would help to
> know
> > > > what's been implemented out there.
> > > > 
> > > > So here's a poll:  Who has implemented DCE compression or COBS and
> > > shipped
> > > > it to customers?
> > > > 
> > > > Thanks,
> > > > 
> > > > Karl
> > > > 
> > > > 
> > > > At 12:32 PM 6/4/99 +0100, Gerry Meyer wrote:
> > > > > >We're in the process of updating the PPPEXT charter (at
> > > > > >http://www.ietf.org/html.charters/pppext-charter.html), and are
> > > changing the
> > > > > >main focus (if there is one!) from enhancements to document
> > > maturation.
> > > > >
> > > > >Talking of documentation....
> > > > >While idly scanning through the on-line Assigned Numbers for PPP:
> > > > >
> > > > >http://www.isi.edu/in-notes/iana/assignments/ppp-numbers
> > > > >
> > > > >I notice some inconsistencies relating to LCP and CCP.
> > > > >
> > > > >For LCP, it has:
> > > > >
> > > > >   21       DCE-Identifier                            [SCHNEIDER]
> > > > >
> > > > >   25       Consistent Overhead Byte Stuffing (COBS)    [Carlson]
> > > > >
> > > > >For CCP, it has:
> > > > >
> > > > >25              DCE                                   [RFC1976]
> > > > >
> > > > >However RFC 1976 has option 25 an **LCP** option:
> > > > >
> > > > >3.  PPP Link Control Protocol Extension
> > > > >
> > > > >    The use of PPP in Compression DCE requires the use of an
> additional
> > > > >    LCP Configuration Option:
> > > > >
> > > > >       25  DCE-Identifier
> > > > >
> > > > >So LCP option 25 has two contenders for the title.
> > > > >  
> > > > >So what is LCP Option 21?
> > > > >
> > > > >         Gerry
> > > > 
> > > > 
> > > > Karl Fox <karl@extant.net>
> > > > Key fingerprint = 5B15 7260 D55E D680 0B93  4953 8A3B AB0E C05D 77A3
> > > > 
> > > 
> > > 
> > > 
> 
> 
> Karl Fox <karl@extant.net>
> Key fingerprint = 5B15 7260 D55E D680 0B93  4953 8A3B AB0E C05D 77A3
> 



From owner-ietf-ppp-outgoing@merit.edu  Mon Jun  7 08:01:51 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19759
	for <pppext-archive@odin.ietf.org>; Mon, 7 Jun 1999 08:01:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9F2A24440F; Mon,  7 Jun 1999 08:01:09 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7A19944414; Mon,  7 Jun 1999 08:01:09 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id BDADF4440F
	for <ietf-ppp@merit.edu>; Mon,  7 Jun 1999 08:01:07 -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 IAA19716;
	Mon, 7 Jun 1999 08:01:04 -0400 (EDT)
Message-Id: <199906071201.IAA19716@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-sdl-02.txt
Date: Mon, 07 Jun 1999 08:01:04 -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 over Simple Data Link (SDL) using SONET/SDH with 
                          ATM-like framing
	Author(s)	: J. Carlson, C.Langner, E. Hernandez-Valencia,  
                          J. Manchester 
	Filename	: draft-ietf-pppext-sdl-02.txt
	Pages		: 27
	Date		: 04-Jun-99
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links, and
RFCs 1662 [2] and 1619 [3] provide a means to carry PPP over
Synchronous Optical Network (SONET) [5] and Synchronous Digital
Hierarchy (SDH) [6] circuits.  This document extends these standards
to include a new encapsulation for PPP called Simple Data Link (SDL)
[7].  SDL provides a very low overhead alternative to standard HDLC
encapsulation for SONET/SDH links.
 
   This document is the product of the Point-to-Point Protocol Working
   Group of the Internet Engineering Task Force (IETF).  Comments should
   be submitted to the ietf-ppp@merit.edu mailing list.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-sdl-02.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Mon Jun  7 19:07:52 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02605
	for <pppext-archive@odin.ietf.org>; Mon, 7 Jun 1999 19:07:52 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id ECA2D44403; Mon,  7 Jun 1999 19:07:14 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C24A74440B; Mon,  7 Jun 1999 19:07:14 -0400 (EDT)
Received: from hotmail.com (f129.hotmail.com [207.82.251.8])
	by segue.merit.edu (Postfix) with SMTP id 08D9244403
	for <ietf-ppp@merit.edu>; Mon,  7 Jun 1999 19:07:13 -0400 (EDT)
Received: (qmail 62496 invoked by uid 0); 7 Jun 1999 23:07:11 -0000
Message-ID: <19990607230711.62495.qmail@hotmail.com>
Received: from 207.20.187.199 by wy1lg.hotmail.com with HTTP;
	Mon, 07 Jun 1999 16:07:11 PDT
X-Originating-IP: [207.20.187.199]
From: Leo Huber <leo_huber@hotmail.com>
To: ietf-ppp@merit.edu
Subject: IP packet forward from one POS link into another
Date: Mon, 07 Jun 1999 16:07:11 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

hi all,

is this a correct encapsulation sequence?:


         |<-payload->|  |<------ transport ------->|

POS in:     UDP2/IP2/   PPP2/L2TP/UDP1/IP1/PPP1/SDH/-> router ->

POS out:    UDP2/IP2/   PPP3/SDH (POS) ->

1. PPP1, PPP2, IP1 and L2TP terminate in the router.
2. PPP3 originates in the router.
3. UDP2/IP2 represent a payload to forward from one POS link
into another POS link.

thx for you help

leo huber


_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun  8 06:48:15 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22859
	for <pppext-archive@odin.ietf.org>; Tue, 8 Jun 1999 06:48:14 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F356844412; Tue,  8 Jun 1999 06:47:40 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id CD2AF44413; Tue,  8 Jun 1999 06:47:40 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 3F52C44412
	for <ietf-ppp@merit.edu>; Tue,  8 Jun 1999 06:47:39 -0400 (EDT)
Received: (from news@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id GAA07193
	for ietf-ppp@merit.edu; Tue, 8 Jun 1999 06:47:38 -0400 (EDT)
To: ietf-ppp@merit.edu
From: James Carlson <carlson@ironbridgenetworks.com>
Newsgroups: lists.ietf.ppp
Subject: Re: IP packet forward from one POS link into another
Date: 08 Jun 1999 06:47:38 -0400
Organization: IronBridge Networks
Lines: 30
Message-ID: <864skj55px.fsf@ironbridgenetworks.com>
References: <19990607230711.62495.qmail@hotmail.com>
NNTP-Posting-Host: helios.ibnets.com
X-Newsreader: Gnus v5.5/Emacs 20.3
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

leo_huber@hotmail.com (Leo Huber) writes:
>          |<-payload->|  |<------ transport ------->|
> 
> POS in:     UDP2/IP2/   PPP2/L2TP/UDP1/IP1/PPP1/SDH/-> router ->
> 
> POS out:    UDP2/IP2/   PPP3/SDH (POS) ->
> 
> 1. PPP1, PPP2, IP1 and L2TP terminate in the router.
> 2. PPP3 originates in the router.

I would say that PPP3 also terminates on this router; but it's just a
semantic thing.

> 3. UDP2/IP2 represent a payload to forward from one POS link
> into another POS link.

That should be "IP2'" -- any router should be modifying at least the
TTL and checksum, if nothing else.

Note that "SDH" isn't an encapsulation like any of the others in your
diagram.  All of the other encapsulations prepend a few bytes to the
PDU or do some data translation (or both).  SDH has a completely
separate framing mechanism running and looks like a byte-at-a-time
(not a packet at a time) pipe to PPP.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun  8 12:27:44 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28897
	for <pppext-archive@odin.ietf.org>; Tue, 8 Jun 1999 12:27:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7CC694440E; Tue,  8 Jun 1999 12:27:09 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 53DCD44428; Tue,  8 Jun 1999 12:27:09 -0400 (EDT)
Received: from hotmail.com (f42.hotmail.com [207.82.250.53])
	by segue.merit.edu (Postfix) with SMTP id 9BFA24440E
	for <ietf-ppp@merit.edu>; Tue,  8 Jun 1999 12:27:07 -0400 (EDT)
Received: (qmail 7263 invoked by uid 0); 8 Jun 1999 16:27:02 -0000
Message-ID: <19990608162701.7260.qmail@hotmail.com>
Received: from 207.20.187.199 by wy1lg.hotmail.com with HTTP;
	Tue, 08 Jun 1999 09:26:56 PDT
X-Originating-IP: [207.20.187.199]
From: Leo Huber <leo_huber@hotmail.com>
To: carlson@ironbridgenetworks.com, ietf-ppp@merit.edu
Subject: Re: IP packet forward from one POS link into another
Date: Tue, 08 Jun 1999 09:26:56 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

thx, James.

could I forward a PPP session into L2TP over POS in
the following way?

POS in:   UDP2/IP2/PPP2/SDH (POS) -> router ->
POS out:  UDP2/IP2/PPP2     /L2TP/UDP1/IP1/PPP1/SDH/->
          | forwarded |     |<--added L2TP encapsu-|
          |<---PPP2-->|     |lation over POS ----->|

Regards,

Leo

>leo_huber@hotmail.com (Leo Huber) writes:
> >          |<-payload->|  |<------ transport ------->|
> >
> > POS in:     UDP2/IP2/   PPP2/L2TP/UDP1/IP1/PPP1/SDH/-> router ->
> >
> > POS out:    UDP2/IP2/   PPP3/SDH (POS) ->
> >
> > 1. PPP1, PPP2, IP1 and L2TP terminate in the router.
> > 2. PPP3 originates in the router.
>
>I would say that PPP3 also terminates on this router; but it's just a
>semantic thing.
>
> > 3. UDP2/IP2 represent a payload to forward from one POS link
> > into another POS link.
>
>That should be "IP2'" -- any router should be modifying at least the
>TTL and checksum, if nothing else.
>
>Note that "SDH" isn't an encapsulation like any of the others in your
>diagram.  All of the other encapsulations prepend a few bytes to the
>PDU or do some data translation (or both).  SDH has a completely
>separate framing mechanism running and looks like a byte-at-a-time
>(not a packet at a time) pipe to PPP.
>
>--
>James Carlson, Software Architect                   <carlson@ibnets.com>
>IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
>Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
>"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp
>


_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun  8 12:53:30 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29330
	for <pppext-archive@odin.ietf.org>; Tue, 8 Jun 1999 12:53:29 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 19E8B44428; Tue,  8 Jun 1999 12:53:07 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E932544437; Tue,  8 Jun 1999 12:53:06 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 5309344428
	for <ietf-ppp@merit.edu>; Tue,  8 Jun 1999 12:53:05 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id MAA13375;
	Tue, 8 Jun 1999 12:53:03 -0400 (EDT)
Date: Tue, 8 Jun 1999 12:53:03 -0400 (EDT)
Message-Id: <199906081653.MAA13375@ironbridgenetworks.com>
X-Authentication-Warning: helios.helios: carlson set sender to carlson@ironbridgenetworks.com using -f
From: James Carlson <carlson@ironbridgenetworks.com>
To: leo_huber@hotmail.com
Cc: ietf-ppp@merit.edu
In-reply-to: <19990608162701.7260.qmail@hotmail.com> (message from Leo Huber
	on Tue, 08 Jun 1999 09:26:56 PDT)
Subject: Re: IP packet forward from one POS link into another
References:  <19990608162701.7260.qmail@hotmail.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> could I forward a PPP session into L2TP over POS in
> the following way?
> 
> POS in:   UDP2/IP2/PPP2/SDH (POS) -> router ->
> POS out:  UDP2/IP2/PPP2     /L2TP/UDP1/IP1/PPP1/SDH/->
>           | forwarded |     |<--added L2TP encapsu-|
>           |<---PPP2-->|     |lation over POS ----->|

Sure.  But now you're not really behaving as a router -- you're
behaving as a LAC.  Routers do forwarding based on layer 3 data; this
is bridging (layer 2 forwarding).

(Note, of course, that if you did that, you'd have exactly *one* user
session over each SDH channel.  These would have to be some pretty
heavy-duty users.)

(Unless, of course, you're doing PPP over Frame Relay on that "input"
side above.  Then you could terminate the Frame Relay locally, use the
DLCI to select the outbound L2TP tunnel, and forward away.  You still
wouldn't be routing in this case.  You'd still be forwarding on layer
2 data, and you'd still be an L2TP LAC.)

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun  9 12:48:13 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28871
	for <pppext-archive@odin.ietf.org>; Wed, 9 Jun 1999 12:48:12 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6D7CD44413; Wed,  9 Jun 1999 12:47:37 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 4744744419; Wed,  9 Jun 1999 12:47:37 -0400 (EDT)
Received: from hotmail.com (f140.hotmail.com [207.82.251.19])
	by segue.merit.edu (Postfix) with SMTP id 8D0FB44413
	for <ietf-ppp@merit.edu>; Wed,  9 Jun 1999 12:47:35 -0400 (EDT)
Received: (qmail 90264 invoked by uid 0); 9 Jun 1999 16:47:34 -0000
Message-ID: <19990609164734.90263.qmail@hotmail.com>
Received: from 207.20.187.199 by wy1lg.hotmail.com with HTTP;
	Wed, 09 Jun 1999 09:47:34 PDT
X-Originating-IP: [207.20.187.199]
From: Leo Huber <leo_huber@hotmail.com>
To: carlson@ironbridgenetworks.com
Cc: ietf-ppp@merit.edu
Subject: Re: IP packet forward from one POS link into another
Date: Wed, 09 Jun 1999 09:47:34 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

thx, James.

one more question:

[leo]:
> > could I forward a PPP session into L2TP over POS in
> > the following way?
> >
> > POS in:   UDP2/IP2/PPP2/SDH2 (POS2) -> LAC ->
> > POS out:  UDP2/IP2/PPP2     /L2TP/UDP1/IP1/PPP1/SDH1/ (POS1)->
> >           | forwarded |     |<--added L2TP encapsu-|
> >           |<---PPP2-->|     |lation over POS ----->|
>
[james]:
>Sure.

[leo]:
it means, that the PPP2 is a fully blown PPP session (which
went through the LCP, authentication and NCP phases), not a frame
structure used instead of HDLC to carry payload over POS2?

regards,

leo huber



_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun  9 13:21:10 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29416
	for <pppext-archive@odin.ietf.org>; Wed, 9 Jun 1999 13:21:09 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DBA2A44419; Wed,  9 Jun 1999 13:20:44 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B4E1C4444B; Wed,  9 Jun 1999 13:20:44 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id E12BE44419
	for <ietf-ppp@merit.edu>; Wed,  9 Jun 1999 13:20:42 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id NAA01802;
	Wed, 9 Jun 1999 13:20:39 -0400 (EDT)
Date: Wed, 9 Jun 1999 13:20:39 -0400 (EDT)
Message-Id: <199906091720.NAA01802@ironbridgenetworks.com>
X-Authentication-Warning: helios.helios: carlson set sender to carlson@ironbridgenetworks.com using -f
From: James Carlson <carlson@ironbridgenetworks.com>
To: leo_huber@hotmail.com
Cc: ietf-ppp@merit.edu
In-reply-to: <19990609164734.90263.qmail@hotmail.com> (message from Leo Huber
	on Wed, 09 Jun 1999 09:47:34 PDT)
Subject: Re: IP packet forward from one POS link into another
References:  <19990609164734.90263.qmail@hotmail.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> > > POS in:   UDP2/IP2/PPP2/SDH2 (POS2) -> LAC ->
> > > POS out:  UDP2/IP2/PPP2     /L2TP/UDP1/IP1/PPP1/SDH1/ (POS1)->
> > >           | forwarded |     |<--added L2TP encapsu-|
> > >           |<---PPP2-->|     |lation over POS ----->|
> >
> it means, that the PPP2 is a fully blown PPP session (which
> went through the LCP, authentication and NCP phases), not a frame
> structure used instead of HDLC to carry payload over POS2?

I don't think I understand that question.  PPP uses HDLC as a framing
mechanism.  There's no obvious distinction here between a "full blown
PPP session" and an HDLC link.

Given the diagram above, here's how I understand you might use such a
thing:

	RouterA <--STS-3c--> LAC <--STS-48c--> network <--> LNS

"RouterA" here is running PPP with the LNS.  As far as it can tell, it
is negotiating with the LNS, and all of the data goes straight there,
as if this were a leased point-to-point STS-3c channel.

The LAC wraps this data in L2TP/UDP/IP/PPP and routes it through a
separate network.  That's how the tunnel is established and used
between the LAC and the LNS.

If, on the other hand, you're implying (by "fully blown") that session
PPP2 is handled and regenerated locally, well, yes, that can be done.
Whether and how you do that is strictly outside the standards (though
draft-ietf-pppext-conversion-01.txt will probably be helpful, and
doing so solves some of L2TP's option-related problems).

Of course, I think that all of this probably silly.  MPLS plus either
RSVP or CR-LDP (or both) isn't a great answer, but it's better than
L2TP here -- in terms of overhead, functionality, and likelihood that
any equipment will support the protocol at the data rates you're
talking about.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 10 06:29:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25288
	for <pppext-archive@odin.ietf.org>; Thu, 10 Jun 1999 06:29:15 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BDF3C4441E; Thu, 10 Jun 1999 06:28:39 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 96B6644422; Thu, 10 Jun 1999 06:28:39 -0400 (EDT)
Received: from spine.adsl.duke.edu (spine.adsl.duke.edu [152.16.67.45])
	by segue.merit.edu (Postfix) with ESMTP id 152DF4441E
	for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 06:28:38 -0400 (EDT)
Received: from hygro.adsl.duke.edu (hygro.adsl.duke.edu [152.16.67.44])
	by spine.adsl.duke.edu (8.8.7/8.8.7) with ESMTP id GAA01984
	for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 06:24:31 -0400
Received: from hygro.adsl.duke.edu (localhost [127.0.0.1]) by hygro.adsl.duke.edu (8.8.7/8.7.3) with ESMTP id GAA01440 for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 06:30:20 -0400
Message-Id: <199906101030.GAA01440@hygro.adsl.duke.edu>
To: ietf-ppp@merit.edu
Subject: FWD: Last Call: The Multi-Class Extension to Multi-Link PPP to 	 Proposed Standard
Date: Thu, 10 Jun 1999 06:30:20 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

------- Forwarded Message

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce: ;
Cc: issll@mercury.lcs.mit.edu
Date: Wed, 09 Jun 1999 16:41:20 -0400
SUBJECT: Last Call: The Multi-Class Extension to Multi-Link PPP to 	 Proposed Standard
Reply-to: iesg@ietf.org


The IESG has received a request from the Integrated Services over
Specific Link Layers Working Group to consider the following documents
as Proposed Standards:


o The Multi-Class Extension to Multi-Link PPP
	<draft-ietf-issll-isslow-mcml-06.txt>

o PPP in a real-time oriented HDLC-like framing 
	<draft-ietf-issll-isslow-rtf-05.txt>

o Integrated Services Mappings for Low Speed Networks 
	<draft-ietf-issll-isslow-svcmap-08.txt>


The IESG will also consider publication of  Providing integrated
services over low-bitrate links <draft-ietf-issll-isslow-06.txt> as an
Informational RFC.



The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by June 23, 1999.

Files can be obtained via:
http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-mcml-06.txt
http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-rtf-05.txt
http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-svcmap-08.txt
http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-06.txt

------- End of Forwarded Message



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 10 10:18:48 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28583
	for <pppext-archive@odin.ietf.org>; Thu, 10 Jun 1999 10:18:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B8BCC44431; Thu, 10 Jun 1999 10:16:52 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 902D044434; Thu, 10 Jun 1999 10:16:52 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id 2042C44431
	for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 10:16:51 -0400 (EDT)
Received: from bluegill ([216.28.121.202]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA4904;
          Thu, 10 Jun 1999 10:16:54 -0400
Message-Id: <4.2.0.56.19990610101441.049d14e0@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 10 Jun 1999 10:16:46 -0400
To: Thomas Narten <narten@raleigh.ibm.com>, ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Re: FWD: Last Call: The Multi-Class Extension to Multi-Link
  PPP to 	 Proposed Standard
In-Reply-To: <199906101030.GAA01440@hygro.adsl.duke.edu>
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

Hi Folks,

What Thomas is implying by forwarding this announcement is that the ISSLL 
working group has proposed some documents that should be examined by a bunch 
of PPP experts, and YOU are those experts.  Please take some time soon and 
look these over.

Thanks (and thanks to Thomas for drawing our attention to this),

Karl

At 06:30 AM 6/10/99 -0400, Thomas Narten wrote:
>------- Forwarded Message
>
>From: The IESG <iesg-secretary@ietf.org>
>To: IETF-Announce: ;
>Cc: issll@mercury.lcs.mit.edu
>Date: Wed, 09 Jun 1999 16:41:20 -0400
>SUBJECT: Last Call: The Multi-Class Extension to Multi-Link PPP to      Proposed Standard
>Reply-to: iesg@ietf.org
>
>
>The IESG has received a request from the Integrated Services over
>Specific Link Layers Working Group to consider the following documents
>as Proposed Standards:
>
>
>o The Multi-Class Extension to Multi-Link PPP
>         <draft-ietf-issll-isslow-mcml-06.txt>
>
>o PPP in a real-time oriented HDLC-like framing 
>         <draft-ietf-issll-isslow-rtf-05.txt>
>
>o Integrated Services Mappings for Low Speed Networks 
>         <draft-ietf-issll-isslow-svcmap-08.txt>
>
>
>The IESG will also consider publication of  Providing integrated
>services over low-bitrate links <draft-ietf-issll-isslow-06.txt> as an
>Informational RFC.
>
>
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by June 23, 1999.
>
>Files can be obtained via:
>http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-mcml-06.txt
>http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-rtf-05.txt
>http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-svcmap-08.txt
>http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-06.txt
>
>------- End of Forwarded Message


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



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 10 11:20:06 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29748
	for <pppext-archive@odin.ietf.org>; Thu, 10 Jun 1999 11:20:05 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 35E1544450; Thu, 10 Jun 1999 11:19:42 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0CF5244452; Thu, 10 Jun 1999 11:19:42 -0400 (EDT)
Received: from Mitel.COM (newgate.mitel.com [198.53.180.100])
	by segue.merit.edu (Postfix) with ESMTP id 3FB3644450
	for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 11:19:40 -0400 (EDT)
Received: from kanmta01.software.mitel.com (kanmta01.software.mitel.com [134.199.37.58]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with SMTP id LAA25943
	for <ietf-ppp@merit.edu>; Thu, 10 Jun 1999 11:19:39 -0400 (EDT)
Received: by kanmta01.software.mitel.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997))  id 8525678C.005430F0 ; Thu, 10 Jun 1999 11:19:35 -0400
X-Lotus-FromDomain: MITEL
From: Connie_Blanchard@Mitel.COM
To: ietf-ppp@merit.edu
Message-ID: <8525678C.00534FD6.00@kanmta01.software.mitel.com>
Date: Thu, 10 Jun 1999 11:20:15 -0400
Subject: Re: Comments on mcml-06 and rtf-05
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



My only comment (as shown in the exchange below from yesterday) is that
both documents assume the implementor of mcml or rtf knows that MP must be
negotiated by using MRRU.  Is it standard practice to leave "assumptions"
like?   RFC1994 for CHAP specifically states that the
Authentication-Protocol Configuration Option  MUST be specified during Link
Establishment Phase. So if a protocol that is developed within the PPP
group has to explicitely state it, I really think that one that is
developed outside of it should.

Just my Canadian 2cents worth........(Canadian at that)

Connie




cabo@informatik.uni-bremen.de on 06/08/99 12:32:05 PM

To:   Connie Blanchard/Kan/Mitel
cc:   issll@mercury.lcs.mit.edu

Subject:  Re: Comments on mcml-06




Connie Blanchard writes:
> To allow multi-class MP to be used, MP must first be negotiated using the
> MRRU option in LCP.
Without the "first": Yes.
(MRRU and the MCML options of course must be present at the same time
in one Configure Request.)
> This draft only states what other MP options are
> available, should it not make reference to the fact that MRRU must be
> negotiated to be able to use the new options? Or is it just assumed that
> the implementor already knows PPP MP?
Since MCML is an extension of RFC1990 and there is no provision that
lifts this requirement from RFC1990, I considered it unnecessary to
repeat it.  Maybe this is an editorial comment that MCML should make
it more explicit that all the provisions of RFC1990 apply -- but as
the document already passed WG last call, this is a bit hard to add at
this point (I would be glad to make such a change otherwise).
> Since it states that short sequence number must not be present if
> MCML code 2 is presented, we should also state the MRRU must be.
This is because the Multilink header format option supersedes the
Short sequence number option, so it is a bad idea to have both in one
Configure Request -- this needs to be stated in the definition of the
Multilink header format option.  The MRRU option is not superseded, so
it (and the requirements on it) remain as is.
Gruesse, Carsten















From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 15 10:40:46 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19050
	for <pppext-archive@odin.ietf.org>; Tue, 15 Jun 1999 10:40:45 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DBDC64442E; Tue, 15 Jun 1999 10:40:05 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B01DE44431; Tue, 15 Jun 1999 10:40:05 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id 3B0B34442E
	for <ietf-ppp@merit.edu>; Tue, 15 Jun 1999 10:40:04 -0400 (EDT)
Received: from bluegill ([209.116.97.145]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA30DC;
          Tue, 15 Jun 1999 10:40:08 -0400
Message-Id: <4.2.0.56.19990615103919.044e8a40@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Tue, 15 Jun 1999 10:39:59 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Fwd: I-D ACTION:draft-lefaucheur-mpls-diff-ppp-00.txt
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

Hi folks,

Please look over this draft and make sure the PPP-related stuff seems reasonable.

Thanks,

Karl Fox

>To: IETF-Announce: ;
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-lefaucheur-mpls-diff-ppp-00.txt
>Date: Tue, 15 Jun 1999 09:19:23 -0400
>Sender: nsyracus@ns.cnri.reston.va.us
>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>         Title           : MPLS Support of Differentiated Services over PPP links
>         Author(s)       : F.Le Faucheur,S.Davari, R.Krishnan, P.Vaananen,
>                           B.Davie
>         Filename        : draft-lefaucheur-mpls-diff-ppp-00.txt
>         Pages           : 19
>         Date            : 14-Jun-99
>         
>This document proposes a flexible solution for MPLS to support
>Differentiated Services (Diff-Serv) over PPP links.
>This solution allows the service provider to flexibly define how
>Diff-Serv Behavior Aggregates (BAs) are mapped onto LSPs so that
>he/she can best match the Diff-Serv and Traffic Engineering
>objectives within his/her particular network. For instance, this
>solution allows the service provider to decide whether sets of BAs
>are to be mapped onto the same LSP or mapped onto separate LSPs.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-lefaucheur-mpls-diff-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-lefaucheur-mpls-diff-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-lefaucheur-mpls-diff-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.
>Content-Type: text/plain
>Content-ID:     <19990614112345.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-lefaucheur-mpls-diff-ppp-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-lefaucheur-mpls-diff-ppp-00.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 Jun 15 14:19:21 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25638
	for <pppext-archive@odin.ietf.org>; Tue, 15 Jun 1999 14:19:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 132154444C; Tue, 15 Jun 1999 14:15:32 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id DD3FD44468; Tue, 15 Jun 1999 14:15:31 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id EB8E44444C
	for <ietf-ppp@merit.edu>; Tue, 15 Jun 1999 14:15:28 -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 OAA25515;
	Tue, 15 Jun 1999 14:15:23 -0400 (EDT)
Message-Id: <199906151815.OAA25515@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-l2tp-16.txt
Date: Tue, 15 Jun 1999 14:15:23 -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		: Layer Two Tunneling Protocol 'L2TP'
	Author(s)	: W. Townsley,  A. Valencia, A. Rubens,  G. Pall,
                          G. Zorn, W. Palter
	Filename	: draft-ietf-pppext-l2tp-16.txt
	Pages		: 75
	Date		: 14-Jun-99
	
This document describes the Layer Two Tunneling Protocol (L2TP).  RFC
1661 specifies multi-protocol access via PPP [RFC1661].  L2TP
facilitates the tunneling of PPP packets across an intervening
network in a way that is as transparent as possible to both end-users
and applications.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-l2tp-16.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 15 17:06:18 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00546
	for <pppext-archive@odin.ietf.org>; Tue, 15 Jun 1999 17:06:17 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0343B44443; Tue, 15 Jun 1999 17:05:45 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D2C3444444; Tue, 15 Jun 1999 17:05:44 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id E955E44443
	for <ietf-ppp@merit.edu>; Tue, 15 Jun 1999 17:05:43 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id RAA22563 for ietf-ppp@merit.edu; Tue, 15 Jun 1999 17:05:43 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id C130A44442
	for <ietf-ppp@merit.edu>; Tue, 15 Jun 1999 16:50:47 -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 QAA00061;
	Tue, 15 Jun 1999 16:50:08 -0400 (EDT)
Message-Id: <199906152050.QAA00061@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ietf-ppp@merit.edu
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Layer Two Tunneling Protocol 'L2TP' to
	 Proposed Standard
Date: Tue, 15 Jun 1999 16:50:08 -0400
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu



The IESG has approved the Internet-Draft Layer Two Tunneling Protocol
'L2TP' <draft-ietf-pppext-l2tp-16.txt> as a Proposed Standard.  This
document is the product of the Point-to-Point Protocol Extensions
Working Group.  The IESG contact persons are Thomas Narten and Erik
Nordmark.


Technical Summary

PPP [RFC1661] defines an encapsulation mechanism for transporting
multiprotocol packets across layer 2 (L2) point-to-point links.
Typically, a user obtains a L2 connection to a Network Access Server
(NAS) using one of a number of techniques (e.g., dialup POTS, ISDN,
ADSL, etc.)  and then runs PPP over that connection. In such a
configuration, the L2 termination point and PPP session endpoint reside
on the same physical device (i.e., the NAS).

The Layer Two Tunneling Protocol (L2TP) extends the PPP model by
allowing the L2 and PPP endpoints to reside on different devices
interconnected by a packet-switched network.  With L2TP, a user has an
L2 connection to an access concentrator (e.g., modem bank, ADSL DSLAM,
etc.), and the concentrator then tunnels individual PPP frames to the
NAS. This allows the actual processing of PPP packets to be divorced
from the termination of the L2 circuit.  From the client's perspective,
L2TP is invisible. No client changes are needed.

This document defines the L2TP protocol and its operation.

Working Group Summary

This document has a long history. L2TP is a merging of two earlier
protocols, Cisco's L2F and PPTP (the product of a vendor consortium).
Implementations of L2TP were made as the document was being written.
Consequently, at the time L2TP was forwarded to the IESG (Spring 1998),
multiple implementations already existed. From the begining, however,
the IESG had concerns about certain aspects of the protocol (e.g., an
aggressive retransmission strategy) as well as the overall readability
of the document. After much back-and-forth (and several iterations of
the draft) the IESG remanded the document back to the Working Group
with specific instructions to rewrite the document (November 1998). The
IESG's overall concern was that the protocol was not implementable from
the document itself.

At the Orlando IETF, a set of interested parties had "reading party"
and started reworking the draft. After a concerted effort that lasted
almost two months, the document was redone, with much of the text
completely rewritten from scratch. In addition, aspects related to flow
control (optional to implement in the original documunt) were removed
from the document. The current document is the result of the rewrite.

There was strong consensus in the WG for the final version of this
document. During the IETF Last Call, three issues were raised. The
first had to do with design choices that were made early on, but the WG
did not want to revisit those decisions and indeed argued that they had
made the right decision. That is, the specific issues raised did not
point to incorrectness in the protocol, so much as perhaps less
efficient operations in some circumstances.

The second issue had to do with the use of IPSec and the role of the
L2TP NAS as a security gateway. It was pointed out that in IPSec, a
security gateway is required to have number of filters with fine
granualarity to control which packets are let through once they are
authenticated. However, L2TP carries PPP traffic, which can carry any
arbitrary higher layer protocol, including IP. No such filter rules are
specified.  The WG felt that the L2TP wasn't attempting to be a
security gateway in the same sense as IPSec. Rather, IPSec is used to
protect the basic integrity of the L2TP packets themselves. A revised
Security Considerations section captures this issue.

The final issue was the disclosure that one of the co-authors of the
document had filed a patent that may cover aspects of L2TP. After much
discussion on the mailing list and at the Minneapolis meeting, the
overwhelming consensus of the WG was to advance the document.

Protocol Quality

This spec has been reviewed for the IESG by Thomas Narten.





From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 15 22:59:51 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07060
	for <pppext-archive@odin.ietf.org>; Tue, 15 Jun 1999 22:59:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 324CB44453; Tue, 15 Jun 1999 22:59:18 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0B87344454; Tue, 15 Jun 1999 22:59:18 -0400 (EDT)
Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.58.198])
	by segue.merit.edu (Postfix) with ESMTP id 6080E44453
	for <ietf-ppp@merit.edu>; Tue, 15 Jun 1999 22:59:16 -0400 (EDT)
Received: from ProLanSys.Com (SNFCB703-43.splitrock.net [209.252.7.242])
	by pimout4-int.prodigy.net (8.8.5/8.8.5) with ESMTP id WAA78800;
	Tue, 15 Jun 1999 22:59:10 -0400
Message-ID: <37671228.598DC50B@ProLanSys.Com>
Date: Tue, 15 Jun 1999 19:55:36 -0700
From: "Naveen.P.N." <NaveenPN@ProLanSys.Com>
Reply-To: NaveenPN@ProLanSys.Com
Organization: ProLanSys, Inc.
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: PPP MAILING LIST <ietf-ppp@merit.edu>,
        Murali Sarjapuram <muralis@ProLanSys.Com>, naveenpn@ProLanSys.Com
Subject: PPTP AUTHENTICATION
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Hi,
    Is MS-CHAP a must to logon to Windows-NT (Ver 4.0) PPTP Server ?
    Is it possible to use CHAP (MD5) or PAP for the above purpose ? If
Yes,
    Please suggest me the means.

    Thanks in advance.
Regards,
Naveen






From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 00:56:44 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08144
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 00:56:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 759CC44454; Wed, 16 Jun 1999 00:56:22 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5217D44455; Wed, 16 Jun 1999 00:56:22 -0400 (EDT)
Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7])
	by segue.merit.edu (Postfix) with ESMTP id 0B68544454
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 00:56:21 -0400 (EDT)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id VAA56252;
	Tue, 15 Jun 1999 21:55:49 -0700 (PDT)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199906160455.VAA56252@bubba.whistle.com>
Subject: Re: PPTP AUTHENTICATION
In-Reply-To: <37671228.598DC50B@ProLanSys.Com> from "Naveen.P.N." at "Jun 15, 99 07:55:36 pm"
To: NaveenPN@ProLanSys.Com
Date: Tue, 15 Jun 1999 21:55:49 -0700 (PDT)
Cc: ietf-ppp@merit.edu, muralis@ProLanSys.Com
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Naveen.P.N. writes:
>     Is MS-CHAP a must to logon to Windows-NT (Ver 4.0) PPTP Server ?

Yes, because MPPE encryption uses the challenge sequence from the
MS-CHAP login. Also, NT servers store the password as hashes instead
of in cleartext (I'm pretty sure about that but don't quote me) so
they can't even do MD5 CHAP if they wanted to.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 01:26:13 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11556
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 01:26:12 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3294444455; Wed, 16 Jun 1999 01:25:39 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0B6FE44456; Wed, 16 Jun 1999 01:25:39 -0400 (EDT)
Received: from fsnt.future.futsoft.com (future.futsoft.com [38.242.192.5])
	by segue.merit.edu (Postfix) with ESMTP id 64D9544455
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 01:25:30 -0400 (EDT)
Received: from kailash.future.futsoft.com (unverified [38.242.192.4]) by fsnt.future.futsoft.com
 (Integralis SMTPRS 2.04) with ESMTP id <B0000668237@fsnt.future.futsoft.com>;
 Wed, 16 Jun 1999 10:56:52 +0530
Received: from alpine.future.futsoft.com (alpine.future.futsoft.com [10.0.4.69]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id KAA12428 for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 10:50:33 +0530
Received: by alpine.future.futsoft.com with Microsoft Mail
	id <01BEB7E6.052F4E60@alpine.future.futsoft.com>; Wed, 16 Jun 1999 10:50:17 +0530
Message-Id: <01BEB7E6.052F4E60@alpine.future.futsoft.com>
From: T Manidhar <manidhart@future.futsoft.com>
To: "ietf-ppp@merit.edu" <ietf-ppp@merit.edu>
Subject:  PPP AUTHENTICATION
Date: Wed, 16 Jun 1999 10:50:15 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Hi,

Any body knows how to configure the RAS service in NT client and server to use the CHAP as a authentication protocol. 

Thanks 
Mani.

-----Original Message-----
From:	Archie Cobbs [SMTP:archie@whistle.com]
Sent:	Wednesday, June 16, 1999 10:26 AM
To:	NaveenPN@ProLanSys.Com
Cc:	ietf-ppp@merit.edu; muralis@ProLanSys.Com
Subject:	Re: PPTP AUTHENTICATION

Naveen.P.N. writes:
>     Is MS-CHAP a must to logon to Windows-NT (Ver 4.0) PPTP Server ?

Yes, because MPPE encryption uses the challenge sequence from the
MS-CHAP login. Also, NT servers store the password as hashes instead
of in cleartext (I'm pretty sure about that but don't quote me) so
they can't even do MD5 CHAP if they wanted to.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 13:11:48 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29699
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 13:11:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 20AF144411; Wed, 16 Jun 1999 13:11:11 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id EB1304442B; Wed, 16 Jun 1999 13:11:10 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 6359544411
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 13:11:09 -0400 (EDT)
Received: (from news@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id NAA01681
	for ietf-ppp@merit.edu; Wed, 16 Jun 1999 13:11:08 -0400 (EDT)
To: ietf-ppp@merit.edu
From: James Carlson <carlson@ironbridgenetworks.com>
Newsgroups: lists.ietf.ppp
Subject: Re: PPTP AUTHENTICATION
Date: 16 Jun 1999 13:11:08 -0400
Organization: IronBridge Networks
Lines: 41
Message-ID: <86u2s8nk9f.fsf@ironbridgenetworks.com>
References: <199906160455.VAA56252@bubba.whistle.com>
NNTP-Posting-Host: helios.ibnets.com
X-Newsreader: Gnus v5.5/Emacs 20.3
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

archie@whistle.com (Archie Cobbs) writes:
> Yes, because MPPE encryption uses the challenge sequence from the
> MS-CHAP login.

They are doing this, but the rationale is weak.  The same procedure
described in draft-ietf-pppext-mschapv2-keys-02.txt could be applied
to standard CHAP, if they desired to be compatible with others.

> Also, NT servers store the password as hashes instead
> of in cleartext (I'm pretty sure about that but don't quote me) so
> they can't even do MD5 CHAP if they wanted to.

That's not at all an impediment.  The NT server stores what is
effectively a cleartext (if not plaintext) password.  The password
just happens to be an MD4 hash of the what the *user* thinks of as his
password.  That the hash itself is the MS-CHAP shared secret doesn't
affect the problem.

So, the behavior expected here by the dial-up user's implementation
(aka the "client") would be to prompt the user for a password with a
fancy dialog box, hash that password using MD4, and then proceed to
use the result of the hash as the shared secret for industry-standard
CHAP authentication.  Et voila.  Standard CHAP authentication.

In fact, since NT dial-in server boxes never bother to authenticate
themselves to anyone (nobody wants to be certain he is always reaching
his actual ISP and isn't being spoofed, does he?), you could have the
CHAP peer name issued by the NT system include a distinguished string
(like "NT-RAS" or some such) so that the "client" machine can
correctly determine whether to do the bogus MD4 hash before using the
password value or not.  That would make it as invisible as any
marketeer would like.

There's nothing in the standard protocols that would prevent them from
doing that and eliminating MS-CHAP-v-anything.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 14:55:26 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12216
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 14:54:55 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 85F1D4445F; Wed, 16 Jun 1999 14:44:42 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5F39344460; Wed, 16 Jun 1999 14:44:42 -0400 (EDT)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by segue.merit.edu (Postfix) with SMTP id 2B07F4445F
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 14:44:41 -0400 (EDT)
Received: from 157.54.9.121 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 16 Jun 1999 11:43:04 -0700 (Pacific Daylight Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2524.0)
	id <NB3YS4CG>; Wed, 16 Jun 1999 11:43:03 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F17@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'James Carlson'" <carlson@ironbridgenetworks.com>, ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Wed, 16 Jun 1999 11:42:56 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

James, how do you do change password (a feature in ms-chap-v-anything) with
a "standard" protocol?

-----Original Message-----
From: James Carlson [mailto:carlson@ironbridgenetworks.com]
Sent: Wednesday, June 16, 1999 10:11 AM
To: ietf-ppp@merit.edu
Subject: Re: PPTP AUTHENTICATION


There's nothing in the standard protocols that would prevent them from
doing that and eliminating MS-CHAP-v-anything.



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 15:23:02 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23259
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 15:22:29 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 7984144488; Wed, 16 Jun 1999 15:10:14 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 4F6914448E; Wed, 16 Jun 1999 15:10:14 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by segue.merit.edu (Postfix) with ESMTP id A500D44488
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 15:10:11 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.0/calcite) id NAA09986
	for ietf-ppp@merit.edu  env-from <vjs>;
	Wed, 16 Jun 1999 13:10:10 -0600 (MDT)
Date: Wed, 16 Jun 1999 13:10:10 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <199906161910.NAA09986@calcite.rhyolite.com>
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> ] There's nothing in the standard protocols that would prevent them from
> ] doing that and eliminating MS-CHAP-v-anything.

> James, how do you do change password (a feature in ms-chap-v-anything) with
> a "standard" protocol?

It is a serious mistake to try to cram all possible interactions between
computers into PPP.  We have more than one protocol, because as with
programs, spaghetti protocols are unmaintainable and do not work well if
at all.

It is also widely considered a serious security error or at best very
dangerous to allow the protocol or mechanism that performs identity checks
(i.e. "authorization") to also change the authenicating data.  That common
wisdom has been learned the hard way in many places and times.  If you
think about it for a few minutes from the point of view of a bad guy, it's
obvious why that is the common wisdom.

Nevertheless, there are many ways that ms-chap-v-something could
interoperate with standard CHAP and also support changes in the CHAP shared
secret.  (Note that there is no password in the standard CHAP protocol.
Instead there is a shared secret.  That distinction is important.)
One way that ms-chap-v-something could support changing the password would
be to use some vendor PPP packets to do Diffie-Hellman exchange, first
establishing a temporary shared secret than then communicating the new
CHAP secret.   That would be secure against eavesdroppers, and would
require no more than 1.5 round trips in the absense of packet loss.  
Again, that protocol, like many others, could be entirely compatible and
interoperable with standard CHAP.



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 15:45:06 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02335
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 15:44:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 357DC444EB; Wed, 16 Jun 1999 15:22:21 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 360F9444E4; Wed, 16 Jun 1999 15:22:13 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 5BE18444DA
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 15:20:16 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id PAA00390;
	Wed, 16 Jun 1999 15:20:14 -0400 (EDT)
Date: Wed, 16 Jun 1999 15:20:14 -0400 (EDT)
Message-Id: <199906161920.PAA00390@ironbridgenetworks.com>
X-Authentication-Warning: helios.helios: carlson set sender to carlson@ironbridgenetworks.com using -f
From: James Carlson <carlson@ironbridgenetworks.com>
To: gurdeep@MICROSOFT.com
Cc: ietf-ppp@merit.edu
In-reply-to: <C35556591D34D111BB5600805F1961B910499F17@RED-MSG-47> (message
	from Gurdeep Singh Pall on Wed, 16 Jun 1999 11:42:56 -0700)
Subject: Re: PPTP AUTHENTICATION
References:  <C35556591D34D111BB5600805F1961B910499F17@RED-MSG-47>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> James, how do you do change password (a feature in ms-chap-v-anything) with
> a "standard" protocol?

You do it via a separate mechanism; any that is validated by the
administrator of the authenticating system will do.  Some security
folks may want physical identifiers to do this; some may do it with a
script.

I view the ability to set the password as a bug, not a feature, in
MS-CHAP.  The bug here is that I can use this security hole to break
into an NT system.  To break in, I first steal a copy of the MD4-
hashed registry.  Then, I use this with a modified implementation of
MS-CHAP (note that the Unix version of this is available as free
source code) that doesn't bother doing the meaningless MD4-hash step
-- it just authenticates using the stolen hash value.  Next, I use
MS-CHAP to change the compromised user's *actual* password.  Now I can
both connect to the network and authenticate as that user for access
to systems on the network as well, since NT is reusing this
authentication mechanism to validate user access.

If this hole weren't designed into MS-CHAP, as it isn't in standards-
compliant CHAP, then stealing the registry wouldn't help much.  I
would be able to connect to the network and pass packets, but I
wouldn't have access to any of the nodes on the network, since they
would each want to challenge me for my knowledge of the true password
(which I don't have), or, if the administrator had any smarts at all,
for a *different* password.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 15:52:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05603
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 15:52:45 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id D633C444AD; Wed, 16 Jun 1999 15:48:44 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B462444492; Wed, 16 Jun 1999 15:48:33 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 82F4244559
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 15:47:57 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id PAA14332;
	Wed, 16 Jun 1999 15:47:52 -0400 (EDT)
Date: Wed, 16 Jun 1999 15:47:52 -0400 (EDT)
Message-Id: <199906161947.PAA14332@ironbridgenetworks.com>
X-Authentication-Warning: helios.helios: carlson set sender to carlson@ironbridgenetworks.com using -f
From: James Carlson <carlson@ironbridgenetworks.com>
To: gurdeep@MICROSOFT.com
Cc: ietf-ppp@merit.edu
In-reply-to: <C35556591D34D111BB5600805F1961B910499F1A@RED-MSG-47> (message
	from Gurdeep Singh Pall on Wed, 16 Jun 1999 12:33:51 -0700)
Subject: Re: PPTP AUTHENTICATION
References:  <C35556591D34D111BB5600805F1961B910499F1A@RED-MSG-47>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> So there is *no* standard protocol that supports change password. 

Not for PPP, no.

> Thanks for clarifying that you made a mistake in your somewhat loose
> comment.
> 
> Gurdeep
> =======
> 
> PS: your plausible attempt to show change password as a "bug" is sure to
> impress some folks. I stopped reading after the small leap "first I steal a
> copy of MD4 hashed registry...." 

I figured as well.  Of course, the registry is perfectly secure and
cannot be compromised.

http://www.martnet.com/~johnny/exploits/microsoft/NT/WinNT.passwordhashes.deobfuscation.html
http://www.kull.ch/Bauersachs/cracknt_e.asp

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 16:25:34 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01593
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 15:42:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 9310044525; Wed, 16 Jun 1999 15:41:07 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A769944513; Wed, 16 Jun 1999 15:41:05 -0400 (EDT)
Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123])
	by segue.merit.edu (Postfix) with SMTP id 4B001444E6
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 15:38:50 -0400 (EDT)
Received: from 157.54.9.123 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 16 Jun 1999 12:33:57 -0700 (Pacific Daylight Time)
Received: by INET-IMC-03 with Internet Mail Service (5.5.2524.0)
	id <NB3ZSXDM>; Wed, 16 Jun 1999 12:33:57 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F1A@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'James Carlson'" <carlson@ironbridgenetworks.com>
Cc: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Wed, 16 Jun 1999 12:33:51 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

So there is *no* standard protocol that supports change password. 

Thanks for clarifying that you made a mistake in your somewhat loose
comment.

Gurdeep
=======

PS: your plausible attempt to show change password as a "bug" is sure to
impress some folks. I stopped reading after the small leap "first I steal a
copy of MD4 hashed registry...." 

-----Original Message-----
From: James Carlson [mailto:carlson@ironbridgenetworks.com]
Sent: Wednesday, June 16, 1999 12:20 PM
To: Gurdeep Singh Pall
Cc: ietf-ppp@merit.edu
Subject: Re: PPTP AUTHENTICATION


> James, how do you do change password (a feature in ms-chap-v-anything)
with
> a "standard" protocol?

You do it via a separate mechanism; any that is validated by the
administrator of the authenticating system will do.  Some security
folks may want physical identifiers to do this; some may do it with a
script.

I view the ability to set the password as a bug, not a feature, in
MS-CHAP.  The bug here is that I can use this security hole to break
into an NT system.  To break in, I first steal a copy of the MD4-
hashed registry.  Then, I use this with a modified implementation of
MS-CHAP (note that the Unix version of this is available as free
source code) that doesn't bother doing the meaningless MD4-hash step
-- it just authenticates using the stolen hash value.  Next, I use
MS-CHAP to change the compromised user's *actual* password.  Now I can
both connect to the network and authenticate as that user for access
to systems on the network as well, since NT is reusing this
authentication mechanism to validate user access.

If this hole weren't designed into MS-CHAP, as it isn't in standards-
compliant CHAP, then stealing the registry wouldn't help much.  I
would be able to connect to the network and pass packets, but I
wouldn't have access to any of the nodes on the network, since they
would each want to challenge me for my knowledge of the true password
(which I don't have), or, if the administrator had any smarts at all,
for a *different* password.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 16:25:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19058
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 16:25:47 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 05C8D44472; Wed, 16 Jun 1999 16:18:29 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id CA68B44490; Wed, 16 Jun 1999 16:18:28 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by segue.merit.edu (Postfix) with ESMTP id E60C044472
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 16:18:26 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.0/calcite) id OAA11487
	for ietf-ppp@merit.edu  env-from <vjs>;
	Wed, 16 Jun 1999 14:18:26 -0600 (MDT)
Date: Wed, 16 Jun 1999 14:18:26 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <199906162018.OAA11487@calcite.rhyolite.com>
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> So there is *no* standard protocol that supports change password. 
>
> Thanks for clarifying that you made a mistake in your somewhat loose
> comment.

As you know, his comment was not loose and he made no mistake.


> PS: your plausible attempt to show change password as a "bug" is sure to
> impress some folks. I stopped reading after the small leap "first I steal a
> copy of MD4 hashed registry...." 

As you know, the reason why the NT designers followed UNIX and chose to
not put the cleartext version of the user's password in the registery is
that no file is secure.  You must assume that the bad guys can use any of
the familiar ways to get the contents of any particular file.  That is
why except for network things, the NT registry password scheme is
reasonably secure.

For your implication that the contents of the registery are unlike other
data and magically secure, there is also the problem of snooping for the
old clear-text passwords on any LAN running previous versions of Microsoft
software.  As far as I can tell, those clear text passwords can be hashed
by a bad guy, and then fed into MS-CHAP.  Am I wrong?  True, if I'm right,
then the bad guy would need access to a wire on the target network.  As
you know, there are few places in the world where a bad guy cannot
"social-engineer" access a LAN, and most security problems involve insiders
who start with at least access to the company intranet.

There's something related with the new "encrypted passwords" of SMB that
no one I've asked has taken the time to explain to me.  How does the new
encrypted password required for mounting a share differ from the old NT
registery hash value?  If I put a network snooper (especially any of the
many software products that run on Windows 95, Windows 98, NT, or UNIX)
on a LAN and watch shares mounted, can I use the "encrypted passwords"
what I will see?  My guess is that the so called encrypted passwords are
only a hash of user's password in the grossly insecure style of MS-CHAP,
telnet, and rlogin, and so can be replayed in the time honored fashion.
In other words, I guess that SMB ships cleartext passwords over the wire.
Is that a valid guess?  Actually, my guess is that I could use those
"encrypted passwords" with MS-CHAP, without access to the machine running
the registry or anyone noticing.  Is that the case?

If my guesses are true, what about your implication about security of the
contents of the registry?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 16 22:06:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06832
	for <pppext-archive@odin.ietf.org>; Wed, 16 Jun 1999 22:06:01 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5036344465; Wed, 16 Jun 1999 22:05:29 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 283D644469; Wed, 16 Jun 1999 22:05:29 -0400 (EDT)
Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by segue.merit.edu (Postfix) with SMTP id F0FCE44465
	for <ietf-ppp@merit.edu>; Wed, 16 Jun 1999 22:05:27 -0400 (EDT)
Received: from 157.54.9.124 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 16 Jun 1999 19:04:23 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2524.0)
	id <NB0YM8L7>; Wed, 16 Jun 1999 19:04:24 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F1F@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Wed, 16 Jun 1999 19:04:23 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

The point (I'll spell it out this time) is that once the shared secret is
stolen (by stealing the registry, reading clear text password files, etc)
any shared secret based authentication method (CHAP, MS-CHAP) is compromised
and all bets are off. 

I agree that one-way-hashed secret is no more secure on the wire than the
secret itself since it too has the time invariant property. I dont recall
anyone claiming otherwise.

I'll have one of our security guys respond to questions re: SMBs below.

Gurdeep
-----Original Message-----
From: Vernon Schryver [mailto:vjs@calcite.rhyolite.com]
Sent: Wednesday, June 16, 1999 1:18 PM
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION


> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> So there is *no* standard protocol that supports change password. 
>
> Thanks for clarifying that you made a mistake in your somewhat loose
> comment.

As you know, his comment was not loose and he made no mistake.


> PS: your plausible attempt to show change password as a "bug" is sure to
> impress some folks. I stopped reading after the small leap "first I steal
a
> copy of MD4 hashed registry...." 

As you know, the reason why the NT designers followed UNIX and chose to
not put the cleartext version of the user's password in the registery is
that no file is secure.  You must assume that the bad guys can use any of
the familiar ways to get the contents of any particular file.  That is
why except for network things, the NT registry password scheme is
reasonably secure.

For your implication that the contents of the registery are unlike other
data and magically secure, there is also the problem of snooping for the
old clear-text passwords on any LAN running previous versions of Microsoft
software.  As far as I can tell, those clear text passwords can be hashed
by a bad guy, and then fed into MS-CHAP.  Am I wrong?  True, if I'm right,
then the bad guy would need access to a wire on the target network.  As
you know, there are few places in the world where a bad guy cannot
"social-engineer" access a LAN, and most security problems involve insiders
who start with at least access to the company intranet.

There's something related with the new "encrypted passwords" of SMB that
no one I've asked has taken the time to explain to me.  How does the new
encrypted password required for mounting a share differ from the old NT
registery hash value?  If I put a network snooper (especially any of the
many software products that run on Windows 95, Windows 98, NT, or UNIX)
on a LAN and watch shares mounted, can I use the "encrypted passwords"
what I will see?  My guess is that the so called encrypted passwords are
only a hash of user's password in the grossly insecure style of MS-CHAP,
telnet, and rlogin, and so can be replayed in the time honored fashion.
In other words, I guess that SMB ships cleartext passwords over the wire.
Is that a valid guess?  Actually, my guess is that I could use those
"encrypted passwords" with MS-CHAP, without access to the machine running
the registry or anyone noticing.  Is that the case?

If my guesses are true, what about your implication about security of the
contents of the registry?


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 06:47:20 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26150
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 06:47:19 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id D40084440A; Thu, 17 Jun 1999 06:46:41 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B00DF4446C; Thu, 17 Jun 1999 06:46:41 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id EABB84440A
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 06:46:33 -0400 (EDT)
Received: (from news@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id GAA02999
	for ietf-ppp@merit.edu; Thu, 17 Jun 1999 06:46:33 -0400 (EDT)
To: ietf-ppp@merit.edu
From: James Carlson <carlson@ironbridgenetworks.com>
Newsgroups: lists.ietf.ppp
Subject: Re: PPTP AUTHENTICATION
Date: 17 Jun 1999 06:46:33 -0400
Organization: IronBridge Networks
Lines: 33
Message-ID: <86yahj5cl2.fsf@ironbridgenetworks.com>
References: <C35556591D34D111BB5600805F1961B910499F1F@RED-MSG-47>
NNTP-Posting-Host: helios.ibnets.com
X-Newsreader: Gnus v5.5/Emacs 20.3
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

gurdeep@MICROSOFT.com (Gurdeep Singh Pall) writes:
> The point (I'll spell it out this time) is that once the shared secret is
> stolen (by stealing the registry, reading clear text password files, etc)
> any shared secret based authentication method (CHAP, MS-CHAP) is compromised
> and all bets are off. 

Absolutely true, at least for PPP authentication.  Of course, systems
that permit use of a *separate* shared secret for CHAP and a password
for authentication to network nodes can be more secure than those that
promiscuously use a single 'password' for all access.

> I agree that one-way-hashed secret is no more secure on the wire than the
> secret itself since it too has the time invariant property. I dont recall
> anyone claiming otherwise.

Really?  Then why does RFC 2433 say this on page 2:

      * The MS-CHAP Response packet is in a format designed for
        compatibility with Microsoft's Windows NT 3.5, 3.51 and 4.0, and
        Windows95 networking products.  The MS-CHAP format does not
        require the authenticator to store a clear-text or reversibly
        encrypted password.

In fact, MS-CHAP *does* require the authenticator to store a
"clear-text password" in exactly the same manner as standard CHAP.
That this "password," or secret, is a hard-to-remember string of bytes
produced automatically by some algorithm is completely irrelevant.

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 12:28:25 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00156
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 12:28:24 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B88794440F; Thu, 17 Jun 1999 12:27:47 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 918A044418; Thu, 17 Jun 1999 12:27:47 -0400 (EDT)
Received: from tibet.coppermountain.com (tibet.coppermountain.com [206.71.190.235])
	by segue.merit.edu (Postfix) with ESMTP id F1C614440F
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 12:27:45 -0400 (EDT)
Received: by tibet.coppermountain.com with Internet Mail Service (5.5.2448.0)
	id <MLA3JY8H>; Thu, 17 Jun 1999 09:27:42 -0700
Message-ID: <47FEF5D2BE22D311AA8600508B10891503F5A4@FS-SD-EXCH1>
From: Eric Michelsen <emichelsen@coppermountain.com>
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Thu, 17 Jun 1999 09:25:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

I'm almost afraid to get into this, but I want to acknowledge a small
observation that was made a year or two ago about this.  There are two
small, but non-zero, benefits to using a "hard-to-remember" string of bytes
instead of the user-visible "easy-to-remember" string of bytes as the
password.  

1. If someone is idly using a sniffer to investigate a network problem
(which I have done in the normal line of duty), and they see all kinds of
simple "easy-to-remember" passwords flashing by on the monitor, they can
easily pick out and remember several of the passwords.  And so can anyone
with virtually no technical knowledge who happens to walk by the sniffer,
thus slightly degrading security.

2. Human beings often choose passwords that are related.  Right or wrong, it
is a fact.  If I know your password on one machine is "benson", then I may
well guess that your password on another machine is "hedges".  In a perfect
world, this wouldn't be true.  But in a perfect world, we wouldn't need
security.

I'm not defending anyone's practice, and I'm not saying these benefits are
intentional or worth any particular amount.  But they are real.
-------------------------------------------
Eric L. Michelsen, Copper Mountain Networks 

> -----Original Message-----
> From: James Carlson [mailto:carlson@ironbridgenetworks.com]
> Sent: Thursday, June 17, 1999 3:47
> To: ietf-ppp@merit.edu
> Subject: Re: PPTP AUTHENTICATION
> 
> 
> gurdeep@MICROSOFT.com (Gurdeep Singh Pall) writes:
> > The point (I'll spell it out this time) is that once the 
> shared secret is
> > stolen (by stealing the registry, reading clear text 
> password files, etc)
> > any shared secret based authentication method (CHAP, 
> MS-CHAP) is compromised
> > and all bets are off. 
> 
> Absolutely true, at least for PPP authentication.  Of course, systems
> that permit use of a *separate* shared secret for CHAP and a password
> for authentication to network nodes can be more secure than those that
> promiscuously use a single 'password' for all access.
> 
> > I agree that one-way-hashed secret is no more secure on the 
> wire than the
> > secret itself since it too has the time invariant property. 
> I dont recall
> > anyone claiming otherwise.
> 
> Really?  Then why does RFC 2433 say this on page 2:
> 
>       * The MS-CHAP Response packet is in a format designed for
>         compatibility with Microsoft's Windows NT 3.5, 3.51 
> and 4.0, and
>         Windows95 networking products.  The MS-CHAP format does not
>         require the authenticator to store a clear-text or reversibly
>         encrypted password.
> 
> In fact, MS-CHAP *does* require the authenticator to store a
> "clear-text password" in exactly the same manner as standard CHAP.
> That this "password," or secret, is a hard-to-remember string of bytes
> produced automatically by some algorithm is completely irrelevant.
> 
> -- 
> James Carlson, Software Architect                   
> <carlson@ibnets.com>
> IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 
> 781 372 8132
> Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 
> 781 372 8090
> "PPP Design and Debugging" --- 
http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 13:55:58 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01247
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 13:55:57 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 27B7644441; Thu, 17 Jun 1999 13:55:31 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id EE67C4447A; Thu, 17 Jun 1999 13:55:30 -0400 (EDT)
Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123])
	by segue.merit.edu (Postfix) with SMTP id C5C1E44441
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 13:55:29 -0400 (EDT)
Received: from 157.54.9.123 by mail3.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 17 Jun 1999 10:36:21 -0700 (Pacific Daylight Time)
Received: by INET-IMC-03 with Internet Mail Service (5.5.2524.0)
	id <NDVFDYWR>; Thu, 17 Jun 1999 10:36:21 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F31@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'James Carlson'" <carlson@ironbridgenetworks.com>, ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Thu, 17 Jun 1999 10:36:19 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu



-----Original Message-----
From: James Carlson [mailto:carlson@ironbridgenetworks.com]

> I agree that one-way-hashed secret is no more secure on the wire than the
> secret itself since it too has the time invariant property. I dont recall
> anyone claiming otherwise.

Really?  Then why does RFC 2433 say this on page 2:

      * The MS-CHAP Response packet is in a format designed for
        compatibility with Microsoft's Windows NT 3.5, 3.51 and 4.0, and
        Windows95 networking products.  The MS-CHAP format does not
        require the authenticator to store a clear-text or reversibly
        encrypted password.

gurdeep> This comment in RFC 2433 is absolutely accurate. You can implement
MS-CHAP if you all you have is the hash instead of the clear text password
stored. 

In fact, MS-CHAP *does* require the authenticator to store a
"clear-text password" in exactly the same manner as standard CHAP.
That this "password," or secret, is a hard-to-remember string of bytes
produced automatically by some algorithm is completely irrelevant.

gurdeep> Wrong. Just so that we align our definition - "clear text password"
is what the user typed in. This is NOT stored as is. The fact that there may
or may not be any value in one-way-obfuscating this "clear text password"
before storing it is not in debate.



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 14:39:47 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01648
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 14:39:46 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0C71944477; Thu, 17 Jun 1999 14:39:10 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D8A0D44473; Thu, 17 Jun 1999 14:39:09 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by segue.merit.edu (Postfix) with ESMTP id D95F844477
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 14:39:07 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.0/calcite) id MAA12583
	for ietf-ppp@merit.edu  env-from <vjs>;
	Thu, 17 Jun 1999 12:39:07 -0600 (MDT)
Date: Thu, 17 Jun 1999 12:39:07 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <199906171839.MAA12583@calcite.rhyolite.com>
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> ...
>       * The MS-CHAP Response packet is in a format designed for
>         compatibility with Microsoft's Windows NT 3.5, 3.51 and 4.0, and
>         Windows95 networking products.  The MS-CHAP format does not
>         require the authenticator to store a clear-text or reversibly
>         encrypted password.
>
> gurdeep> This comment in RFC 2433 is absolutely accurate. You can implement
> MS-CHAP if you all you have is the hash instead of the clear text password
> stored. 

Not so!  The string on the wire may look like gobbledegook, but it is a
cleartext password as the term is understood among the technically
literate.  See for example, page 1 of "Applied Cryptography" by Schneier.

Putting a front-end on PAP that converts (e.g. by hashing) what the user
thinks is the password to something else that goes over the wire would
not change PAP to not use a cleartext password.  If MS-CHAP does not use
a cleartext password, then neither does PAP.  If PAP does use a cleartext
password, then so does MS-CHAP.

That text from RFC 2433 might be literally true in a contorted, user
interface sense, but it conveys a notion that we all (including Microsoft)
in the IETF PPP WG have agreed is false for the last few years.  (Recall
or check the archives for the long discussion in this mailinglist.)  I
wonder what the lawyers at Microsoft or any outfit with deep pockets
would say about the false assurance of security that text conveys if they
knew about it.


> In fact, MS-CHAP *does* require the authenticator to store a
> "clear-text password" in exactly the same manner as standard CHAP.
> That this "password," or secret, is a hard-to-remember string of bytes
> produced automatically by some algorithm is completely irrelevant.
>
> gurdeep> Wrong. Just so that we align our definition - "clear text password"
> is what the user typed in. This is NOT stored as is. The fact that there may
> or may not be any value in one-way-obfuscating this "clear text password"
> before storing it is not in debate.

The password used by MS-CHAP is a cleartext password as far as the
authentication protocol is concerned and in the eyes of the technically
knowledgable.  What the user types is irrelevant.  Whether the translation
from what the user types to what goes over the wire is the identity map,
hashing, a look-up in a disk file, a conversion of mixed upper and lower
case to upper case, conversion from ASCII to EBCDIC, or something else or
is irrelevant to whether what goes over the wire is a cleartext password.
User-intefaces issues are important, but they have long been outside the
scope of the IETF PPP WG.  Reasonable people might say that's bad, but it
is a fact.


Separately, the value of cleartext goobledygook passwords compared to
easily remembered (by humans) cleartext passwords is overrated.  It might
be harder for someone who does not care to break into a system to remember
cybercrud, but those people are not a threat, since by definition they
don't care.  The people you need to worry about are those who will set
their sniffers to capture the right bits, and then right them down.
Passwords that are vulerable to dictionary attacks are not made
significantly worse by the use of other vulnerable passwords.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 16:08:57 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02246
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 16:08:57 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 33EFF44470; Thu, 17 Jun 1999 16:08:35 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0C04F44478; Thu, 17 Jun 1999 16:08:35 -0400 (EDT)
Received: from databus.databus.com (databus.databus.com [198.186.154.34])
	by segue.merit.edu (Postfix) with SMTP id 5641844470
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 16:08:33 -0400 (EDT)
From: Barney Wolff <barney@databus.com>
To: ietf-ppp@merit.edu
Date: Thu, 17 Jun 1999 15:57 EDT
Subject: RE: PPTP AUTHENTICATION
Content-Type: text/plain
Message-ID: <376955b70.42ef@databus.databus.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Are you folks debating the cleartext-ness of the password as stored by
the authenticator, or what goes over the wire?  I believe that what is
stored is equivalent to cleartext, but unless I'm sadly mistaken,
MS-CHAP is CHAP-like in that what goes over the wire is not the actual
password or a fixed hash of it and does depend on the challenge.

Barney Wolff  <barney@databus.com>

> Date: Thu, 17 Jun 1999 12:39:07 -0600 (MDT)
> From: Vernon Schryver <vjs@calcite.rhyolite.com>
> 
> The password used by MS-CHAP is a cleartext password as far as the
> authentication protocol is concerned and in the eyes of the technically
> knowledgable.  What the user types is irrelevant.  Whether the translation
> from what the user types to what goes over the wire is the identity map,
> hashing, a look-up in a disk file, a conversion of mixed upper and lower
> case to upper case, conversion from ASCII to EBCDIC, or something else or
> is irrelevant to whether what goes over the wire is a cleartext password.
> User-intefaces issues are important, but they have long been outside the
> scope of the IETF PPP WG.  Reasonable people might say that's bad, but it
> is a fact.



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 17:06:09 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02713
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 17:06:09 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BA29144421; Thu, 17 Jun 1999 17:05:38 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9138744473; Thu, 17 Jun 1999 17:05:38 -0400 (EDT)
Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by segue.merit.edu (Postfix) with SMTP id 65CF944421
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 17:05:37 -0400 (EDT)
Received: from 157.54.9.124 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 17 Jun 1999 14:04:23 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2524.0)
	id <ND0B78ZG>; Thu, 17 Jun 1999 14:04:11 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F3C@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'Barney Wolff'" <barney@databus.com>, ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Thu, 17 Jun 1999 13:30:46 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

You are not mistaken. On the wire CHAP and MS-CHAP are equivalent in that
both produce a response that is a fucntion of the secret and the challenge. 

As far as stored "secrets" are concerned there is no claim that storing
"user password" is significantly worse than storing its one-way-hash if both
are treated as "first order" secrets (as in CHAP or MS-CHAP). But this isnt
the first time on the ppp list that non-issues have been debated ad nauseam
:-)

Gurdeep
-----Original Message-----
From: Barney Wolff [mailto:barney@databus.com]
Sent: Thursday, June 17, 1999 12:57 PM
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION


Are you folks debating the cleartext-ness of the password as stored by
the authenticator, or what goes over the wire?  I believe that what is
stored is equivalent to cleartext, but unless I'm sadly mistaken,
MS-CHAP is CHAP-like in that what goes over the wire is not the actual
password or a fixed hash of it and does depend on the challenge.

Barney Wolff  <barney@databus.com>

> Date: Thu, 17 Jun 1999 12:39:07 -0600 (MDT)
> From: Vernon Schryver <vjs@calcite.rhyolite.com>
> 
> The password used by MS-CHAP is a cleartext password as far as the
> authentication protocol is concerned and in the eyes of the technically
> knowledgable.  What the user types is irrelevant.  Whether the translation
> from what the user types to what goes over the wire is the identity map,
> hashing, a look-up in a disk file, a conversion of mixed upper and lower
> case to upper case, conversion from ASCII to EBCDIC, or something else or
> is irrelevant to whether what goes over the wire is a cleartext password.
> User-intefaces issues are important, but they have long been outside the
> scope of the IETF PPP WG.  Reasonable people might say that's bad, but it
> is a fact.



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 17:36:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03027
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 17:36:49 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A6C834441C; Thu, 17 Jun 1999 17:36:28 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8068A44478; Thu, 17 Jun 1999 17:36:28 -0400 (EDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by segue.merit.edu (Postfix) with ESMTP id AB8034441C
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 17:36:26 -0400 (EDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.0/calcite) id PAA16312
	for ietf-ppp@merit.edu  env-from <vjs>;
	Thu, 17 Jun 1999 15:36:25 -0600 (MDT)
Date: Thu, 17 Jun 1999 15:36:25 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <199906172136.PAA16312@calcite.rhyolite.com>
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> You are not mistaken. On the wire CHAP and MS-CHAP are equivalent in that
> both produce a response that is a fucntion of the secret and the challenge. 
>
> As far as stored "secrets" are concerned there is no claim that storing
> "user password" is significantly worse than storing its one-way-hash if both
> are treated as "first order" secrets (as in CHAP or MS-CHAP). But this isnt
> the first time on the ppp list that non-issues have been debated ad nauseam
> :-)

It seeems I've been foolishly wrong.  By actually breaking down
and reading RFC 2433, I see that it is essentially CHAP, but with
a form of DES instead of MD5 for the hashing in the challenges and
responses.  MS-CHAP is not PAP.  I appologize for saying it was.


However, both common wisdom and the cleartext passwords for file
sharing on LANs make the password changing features of RFC 2433
and using the same password for user authentication as network
access a Bad Idea(tm).

Also, the following recently mentioned text in section 2 of RFC 2433 is
still wrong and misleading, since the password that matters is the 56-bit
DES key.
                                        The MS-CHAP format does not
        require the authenticator to store a clear-text or reversibly
        encrypted password.

That the user is allowed to type a memorable ASCII string instead of (for
example) 14 hex digits is a good user-interface choice, but does not keep
the key from being stored in the clear.  Of necessity, and contrary to
those words, the key is always stored as "clear-text or reversibly
encrypted."


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 17:44:28 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03071
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 17:44:27 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6BE9A44478; Thu, 17 Jun 1999 17:44:06 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 40D8B44479; Thu, 17 Jun 1999 17:44:06 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id CA57144478
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 17:44:04 -0400 (EDT)
Received: from bluegill ([216.28.121.202]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA2DBA;
          Thu, 17 Jun 1999 17:44:10 -0400
Message-Id: <4.2.0.56.19990617173936.04532c80@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 17 Jun 1999 17:44:01 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>, ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: RE: PPTP AUTHENTICATION
In-Reply-To: <199906172136.PAA16312@calcite.rhyolite.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

At 03:36 PM 6/17/99 -0600, Vernon Schryver wrote:
>It seeems I've been foolishly wrong.  By actually breaking down
>and reading RFC 2433, I see that it is essentially CHAP, but with
>a form of DES instead of MD5 for the hashing in the challenges and
>responses.  MS-CHAP is not PAP.  I appologize for saying it was.

First off, let me admit that the following paragraph is based on my rather 
poor memory of an analysis I did more than four years ago.

One important difference is that DES is used in a way that may make it 
easier than necessary to break.  It is used to encrypt three blocks without 
cipher block chaining, and one of the blocks is padded with 6 bytes of 
zeros, meaning you only have 16 bits of plaintext space to search.  This may 
or may not make it easier to break the entire encrypted sequence.

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



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 20:06:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03780
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 20:06:16 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id D9DF04446E; Thu, 17 Jun 1999 20:05:43 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B3EA444474; Thu, 17 Jun 1999 20:05:43 -0400 (EDT)
Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7])
	by segue.merit.edu (Postfix) with ESMTP id E4CAC4446E
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 20:05:41 -0400 (EDT)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id RAA67247
	for ietf-ppp@merit.edu; Thu, 17 Jun 1999 17:05:41 -0700 (PDT)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199906180005.RAA67247@bubba.whistle.com>
Subject: Re: PPTP AUTHENTICATION
In-Reply-To: <4.2.0.56.19990617173936.04532c80@mail.extant.net> from Karl Fox at "Jun 17, 99 05:44:01 pm"
To: ietf-ppp@merit.edu
Date: Thu, 17 Jun 1999 17:05:41 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Regarding PPTP security weaknesses, some of you may find this paper
interesting if you haven't read it already.

  "Cryptanalysis of Microsoft's Point-to-Point Tunneling Protocol (PPTP)"

  http://www.counterpane.com/pptp.html

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 21:02:44 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03971
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 21:02:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id D970444476; Thu, 17 Jun 1999 21:02:14 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id AFB3244479; Thu, 17 Jun 1999 21:02:14 -0400 (EDT)
Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by segue.merit.edu (Postfix) with SMTP id 7E3EE44476
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 21:02:13 -0400 (EDT)
Received: from 157.54.9.124 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 17 Jun 1999 18:01:01 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2524.0)
	id <ND0B8QP7>; Thu, 17 Jun 1999 18:01:02 -0700
Message-ID: <C35556591D34D111BB5600805F1961B91783DD6D@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'Archie Cobbs'" <archie@whistle.com>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
Subject: RE: PPTP AUTHENTICATION
Date: Thu, 17 Jun 1999 18:00:59 -0700
X-Mailer: Internet Mail Service (5.5.2524.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

This paper is outdated. The later versions of auth and crypto with PPTP
based VPNs use different methods and dont have the weaknesses described in
this.

Gurdeep
-----Original Message-----
From: Archie Cobbs [mailto:archie@whistle.com]
Sent: Thursday, June 17, 1999 5:06 PM
To: ietf-ppp@merit.edu
Subject: Re: PPTP AUTHENTICATION


Regarding PPTP security weaknesses, some of you may find this paper
interesting if you haven't read it already.

  "Cryptanalysis of Microsoft's Point-to-Point Tunneling Protocol (PPTP)"

  http://www.counterpane.com/pptp.html

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 21:34:08 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04131
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 21:34:07 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0791544479; Thu, 17 Jun 1999 21:33:48 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D5DFF4447A; Thu, 17 Jun 1999 21:33:47 -0400 (EDT)
Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7])
	by segue.merit.edu (Postfix) with ESMTP id 8009644479
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 21:33:46 -0400 (EDT)
Received: (from archie@localhost)
	by bubba.whistle.com (8.9.2/8.9.2) id SAA67608;
	Thu, 17 Jun 1999 18:33:45 -0700 (PDT)
From: Archie Cobbs <archie@whistle.com>
Message-Id: <199906180133.SAA67608@bubba.whistle.com>
Subject: Re: PPTP AUTHENTICATION
In-Reply-To: <C35556591D34D111BB5600805F1961B91783DD6D@RED-MSG-47> from Gurdeep Singh Pall at "Jun 17, 99 06:00:59 pm"
To: gurdeep@MICROSOFT.com (Gurdeep Singh Pall)
Date: Thu, 17 Jun 1999 18:33:45 -0700 (PDT)
Cc: archie@whistle.com, ietf-ppp@merit.edu
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Gurdeep Singh Pall writes:
> This paper is outdated. The later versions of auth and crypto with PPTP
> based VPNs use different methods and dont have the weaknesses described in
> this.
> 
>   ...
> 
>   http://www.counterpane.com/pptp.html

That's good to hear.. it might be worth notifying the paper's author
on that website (I believe it originated there).

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 17 23:57:56 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06909
	for <pppext-archive@odin.ietf.org>; Thu, 17 Jun 1999 23:57:55 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 331F64447E; Thu, 17 Jun 1999 23:57:26 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0D68644480; Thu, 17 Jun 1999 23:57:26 -0400 (EDT)
Received: from hotmail.com (wya-lfd113.hotmail.com [207.82.252.177])
	by segue.merit.edu (Postfix) with SMTP id 91CE04447E
	for <ietf-ppp@merit.edu>; Thu, 17 Jun 1999 23:57:24 -0400 (EDT)
Received: (qmail 30198 invoked by uid 0); 18 Jun 1999 03:57:23 -0000
Message-ID: <19990618035723.30197.qmail@hotmail.com>
Received: from 207.20.187.199 by wy1lg.hotmail.com with HTTP;
	Thu, 17 Jun 1999 20:57:22 PDT
X-Originating-IP: [207.20.187.199]
From: Leo Huber <leo_huber@hotmail.com>
To: ietf-ppp@merit.edu
Subject: Re: RADIUS source code availability
Date: Thu, 17 Jun 1999 20:57:22 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

could somebody recommend a source code vendor
for a RADIUS client working with PPP and L2TP?

thx

Leo Huber





_______________________________________________________________
Get Free Email and Do More On The Web. Visit http://www.msn.com



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun 18 00:31:22 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07132
	for <pppext-archive@odin.ietf.org>; Fri, 18 Jun 1999 00:31:21 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 2290144480; Fri, 18 Jun 1999 00:30:52 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E8E9A44481; Fri, 18 Jun 1999 00:30:51 -0400 (EDT)
Received: from pss-imc-01.microsoft.com (pss-imc-01.microsoft.com [131.107.3.100])
	by segue.merit.edu (Postfix) with ESMTP id DA3C944480
	for <ietf-ppp@merit.edu>; Fri, 18 Jun 1999 00:30:50 -0400 (EDT)
Received: by PSS-IMC-01 with Internet Mail Service (5.5.2635.0)
	id <N1SA0Y5K>; Thu, 17 Jun 1999 21:29:42 -0700
Message-ID: <C35556591D34D111BB5600805F1961B910499F38@RED-MSG-47>
From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>
To: "'Vernon Schryver'" <vjs@calcite.rhyolite.com>, ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION
Date: Thu, 17 Jun 1999 11:59:15 -0700
X-Mailer: Internet Mail Service (5.5.2635.0)
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

The clear text password and its hash are equivalent from protocol
standpoint. No argument. No one has claimed otherwise.

MS-CHAP does NOT require clear text password (as the user typed in) to be
available since it works off the one-way-hash. Therefore the comment - "The
MS-CHAP format does not require the authenticator to store a clear-text or
reversibly encrypted password." is absolutely true. If you are reading
implications beyond this - thats, er, your problem.

Gurdeep
-----Original Message-----
From: Vernon Schryver [mailto:vjs@calcite.rhyolite.com]
Sent: Thursday, June 17, 1999 11:39 AM
To: ietf-ppp@merit.edu
Subject: RE: PPTP AUTHENTICATION


> From: Gurdeep Singh Pall <gurdeep@MICROSOFT.com>

> ...
>       * The MS-CHAP Response packet is in a format designed for
>         compatibility with Microsoft's Windows NT 3.5, 3.51 and 4.0, and
>         Windows95 networking products.  The MS-CHAP format does not
>         require the authenticator to store a clear-text or reversibly
>         encrypted password.
>
> gurdeep> This comment in RFC 2433 is absolutely accurate. You can
implement
> MS-CHAP if you all you have is the hash instead of the clear text password
> stored. 

Not so!  The string on the wire may look like gobbledegook, but it is a
cleartext password as the term is understood among the technically
literate.  See for example, page 1 of "Applied Cryptography" by Schneier.

Putting a front-end on PAP that converts (e.g. by hashing) what the user
thinks is the password to something else that goes over the wire would
not change PAP to not use a cleartext password.  If MS-CHAP does not use
a cleartext password, then neither does PAP.  If PAP does use a cleartext
password, then so does MS-CHAP.

That text from RFC 2433 might be literally true in a contorted, user
interface sense, but it conveys a notion that we all (including Microsoft)
in the IETF PPP WG have agreed is false for the last few years.  (Recall
or check the archives for the long discussion in this mailinglist.)  I
wonder what the lawyers at Microsoft or any outfit with deep pockets
would say about the false assurance of security that text conveys if they
knew about it.


> In fact, MS-CHAP *does* require the authenticator to store a
> "clear-text password" in exactly the same manner as standard CHAP.
> That this "password," or secret, is a hard-to-remember string of bytes
> produced automatically by some algorithm is completely irrelevant.
>
> gurdeep> Wrong. Just so that we align our definition - "clear text
password"
> is what the user typed in. This is NOT stored as is. The fact that there
may
> or may not be any value in one-way-obfuscating this "clear text password"
> before storing it is not in debate.

The password used by MS-CHAP is a cleartext password as far as the
authentication protocol is concerned and in the eyes of the technically
knowledgable.  What the user types is irrelevant.  Whether the translation
from what the user types to what goes over the wire is the identity map,
hashing, a look-up in a disk file, a conversion of mixed upper and lower
case to upper case, conversion from ASCII to EBCDIC, or something else or
is irrelevant to whether what goes over the wire is a cleartext password.
User-intefaces issues are important, but they have long been outside the
scope of the IETF PPP WG.  Reasonable people might say that's bad, but it
is a fact.


Separately, the value of cleartext goobledygook passwords compared to
easily remembered (by humans) cleartext passwords is overrated.  It might
be harder for someone who does not care to break into a system to remember
cybercrud, but those people are not a threat, since by definition they
don't care.  The people you need to worry about are those who will set
their sniffers to capture the right bits, and then right them down.
Passwords that are vulerable to dictionary attacks are not made
significantly worse by the use of other vulnerable passwords.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun 18 02:57:49 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20453
	for <pppext-archive@odin.ietf.org>; Fri, 18 Jun 1999 02:57:48 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id ED84A44484; Fri, 18 Jun 1999 02:57:14 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C65C244487; Fri, 18 Jun 1999 02:57:14 -0400 (EDT)
Received: from djwhome.demon.co.uk (djwhome.demon.co.uk [158.152.19.5])
	by segue.merit.edu (Postfix) with ESMTP id 0846A44484
	for <ietf-ppp@merit.edu>; Fri, 18 Jun 1999 02:57:12 -0400 (EDT)
Received: (from david@localhost) by djwhome.demon.co.uk (8.8.8/8.7.3) id WAA05971; Thu, 17 Jun 1999 22:21:40 +0100
From: David Woolley <david@djwhome.demon.co.uk>
Message-Id: <199906172121.WAA05971@djwhome.demon.co.uk>
Subject: Re: PPTP AUTHENTICATION
To: carlson@ironbridgenetworks.com (James Carlson)
Date: Thu, 17 Jun 1999 22:21:40 +0100 (BST)
Cc: gurdeep@MICROSOFT.com, ietf-ppp@merit.edu
Reply-To: ietf-ppp@merit.edu
In-Reply-To: <199906161920.PAA00390@ironbridgenetworks.com> from "James Carlson" at Jun 16, 99 03:20:14 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

> -- it just authenticates using the stolen hash value.  Next, I use
> MS-CHAP to change the compromised user's *actual* password.  Now I can

I was under the impression that the same MD4 hashed value was used for
SMB authentication; if so, there is no distinct *actual* password, and
read access compromises the network without the need to change the
password (you can make the same conceptual change to SAMBA as you can
make to pppd).



From owner-ietf-ppp-outgoing@merit.edu  Fri Jun 18 11:43:08 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25038
	for <pppext-archive@odin.ietf.org>; Fri, 18 Jun 1999 11:43:08 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id C7BF444483; Fri, 18 Jun 1999 11:42:33 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A2D3944485; Fri, 18 Jun 1999 11:42:33 -0400 (EDT)
Received: from newman.aventail.com (newman.aventail.com [216.207.80.1])
	by segue.merit.edu (Postfix) with ESMTP id 2E1AB44483
	for <ietf-ppp@merit.edu>; Fri, 18 Jun 1999 11:42:32 -0400 (EDT)
Received: from leo.in.aventail.com (leo.in.aventail.com [192.168.1.136])
	by newman.aventail.com (8.8.5/8.8.5) with ESMTP id IAA00516;
	Fri, 18 Jun 1999 08:42:22 -0700 (PDT)
Received: from smtp.aventail.com (barenaked.in.aventail.com [192.168.100.6]) by leo.in.aventail.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id M00KTTYH; Fri, 18 Jun 1999 08:38:10 -0700
X-Mailer: exmh version 2.0.2 2/24/98
From: marcvh@aventail.com (Marc VanHeyningen)
To: Archie Cobbs <archie@whistle.com>
Cc: gurdeep@MICROSOFT.com (Gurdeep Singh Pall), ietf-ppp@merit.edu
Subject: Re: PPTP AUTHENTICATION 
In-reply-to: Your message of "Thu, 17 Jun 1999 18:33:45 PDT."
             <199906180133.SAA67608@bubba.whistle.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 18 Jun 1999 08:42:22 -0700
Message-ID: <1193.929720542@smtp.aventail.com>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> Gurdeep Singh Pall writes:
> > This paper is outdated. The later versions of auth and crypto with PPTP
> > based VPNs use different methods and dont have the weaknesses described in
> > this.
> > 
> >   ...
> > 
> >   http://www.counterpane.com/pptp.html
> 
> That's good to hear.. it might be worth notifying the paper's author
> on that website (I believe it originated there).

I believe he has some awareness of it.  At one point Microsoft had a paper
outlining their response, but for some reason MS choose to pull it off
their web site.  If they published something describing (with some
technical detail) how the weaknesses have been addressed, I strongly
suspect Bruce would include a link to it with his paper.

- Marc

-- 
Marc VanHeyningen                 marcvh@aventail.com
Internet Security Architect
Aventail                          http://www.aventail.com/






From owner-ietf-ppp-outgoing@merit.edu  Sat Jun 19 05:34:06 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20391
	for <pppext-archive@odin.ietf.org>; Sat, 19 Jun 1999 05:34:05 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B2F6344424; Sat, 19 Jun 1999 05:33:20 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 8C6A5444B3; Sat, 19 Jun 1999 05:33:20 -0400 (EDT)
Received: from djwhome.demon.co.uk (djwhome.demon.co.uk [158.152.19.5])
	by segue.merit.edu (Postfix) with ESMTP id 3147944424
	for <ietf-ppp@merit.edu>; Sat, 19 Jun 1999 05:33:18 -0400 (EDT)
Received: (from david@localhost) by djwhome.demon.co.uk (8.8.8/8.7.3) id WAA07567; Fri, 18 Jun 1999 22:28:38 +0100
From: David Woolley <david@djwhome.demon.co.uk>
Message-Id: <199906182128.WAA07567@djwhome.demon.co.uk>
Subject: Re: PPP AUTHENTICATION
To: manidhart@future.futsoft.com (T Manidhar)
Date: Fri, 18 Jun 1999 22:28:38 +0100 (BST)
Cc: ietf-ppp@merit.edu
Reply-To: ietf-ppp@merit.edu
In-Reply-To: <01BEB7E6.052F4E60@alpine.future.futsoft.com> from "T Manidhar" at Jun 16, 99 10:50:15 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

[ Re-wrapped to internet standards ]
> Any body knows how to configure the RAS service in NT client and server
> to use the CHAP as a authentication protocol.

It's impossible, for reasons which should be clear from the PPTP 
AUTHENTICATION thread; basically NT does not know the user form of
the password, but MD5-CHAP requires that both parties do know it++.

The free pppd generates the form that NT stores on the fly, but doesn't
have to worry about conforming with Orange book requirements not to
store user form passwords.

++ Pedantically it is only a protocol, and therefore isn't concerned with
user interface issues, but I'm sure you are expecting to work in terms of
what the user enters, not an internal, scrambled, version.



From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 07:36:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03231
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 07:36:00 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id CDBAC4440E; Mon, 21 Jun 1999 07:35:19 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A60694441F; Mon, 21 Jun 1999 07:35:19 -0400 (EDT)
Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2])
	by segue.merit.edu (Postfix) with ESMTP id 08B8E4440E
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 07:35:18 -0400 (EDT)
Received: (from carlson@localhost)
	by ironbridgenetworks.com (8.9.3/8.9.3) id HAA25941;
	Mon, 21 Jun 1999 07:35:17 -0400 (EDT)
To: ietf-ppp@merit.edu
Subject: Re: PPP AUTHENTICATION
References: <199906182128.WAA07567@djwhome.demon.co.uk>
From: James Carlson <carlson@ironbridgenetworks.com>
Date: 21 Jun 1999 07:35:17 -0400
In-Reply-To: david@djwhome.demon.co.uk's message of "19 Jun 1999 05:33:48 -0400"
Message-ID: <86wvwxvlai.fsf@ironbridgenetworks.com>
Lines: 54
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

david@djwhome.demon.co.uk (David Woolley) writes:
> [ Re-wrapped to internet standards ]
> > Any body knows how to configure the RAS service in NT client and server
> > to use the CHAP as a authentication protocol.
> 
> It's impossible, for reasons which should be clear from the PPTP 
> AUTHENTICATION thread; basically NT does not know the user form of
> the password, but MD5-CHAP requires that both parties do know it++.

This doesn't really matter, unless all we're talking about is the
current (and broken) mode of operation.

> The free pppd generates the form that NT stores on the fly, but doesn't
> have to worry about conforming with Orange book requirements not to
> store user form passwords.

"Orange Book" standards don't really apply here.  Computers with
network attachments can't pass TC/SEC muster at all.  (They can be
used in a secure environment if the whole configuration is blessed by
a DAA, but, then, the same is true of a live chicken.  ;-})

> ++ Pedantically it is only a protocol, and therefore isn't concerned with
> user interface issues, but I'm sure you are expecting to work in terms of
> what the user enters, not an internal, scrambled, version.

As also outlined in that thread, there's also no particular reason to
prohibit the user interface from doing the "right thing" here.
(Brashly assuming, of course, that MS-CHAP is also doing the "right
thing.")

The right thing, by way of NT and dial-up clients, would be to have
the "client" end of the conversation detect that the peer is using NT
(perhaps by a distinguished value in the peer name field in the CHAP
Challenge message), and then use MD4 to hash the user's password
before using it as part of the standard CHAP MD5 hash.  (Note that the
MD4 hash in MS-CHAP is done over only the password given by the user.
It is thus effectively a constant for a given user password.)

The shared secret is thus the hashed password, and the user interface
is intact.  No new protocols need be invented, and this procedure is
no more or less secure than MS-CHAP.

(You don't even necessarily need this automatic-detection logic based
on peer name.  This feature could be a check-box in your user
interface or, if you're lucky, a second try at a CHAP Response value.
Some implementations allow a limited number of CHAP retries on
failure, so the first attempt could use the standard method, and, if
that fails, the second could try the MD4 hash first.)

-- 
James Carlson, Software Architect                   <carlson@ibnets.com>
IronBridge Networks / 55 Hayden Avenue   71.246W   Vox:  +1 781 372 8132
Lexington MA  02421-7996 / USA           42.423N   Fax:  +1 781 372 8090
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp



From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 16:44:03 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09807
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 16:44:02 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5D95E4441F; Mon, 21 Jun 1999 16:43:25 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 3692D4442A; Mon, 21 Jun 1999 16:43:25 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by segue.merit.edu (Postfix) with ESMTP id E9C534441F
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 16:43:21 -0400 (EDT)
Received: from pai820exch001h.wins.lucent.com (h135-14-3-59.lucent.com [135.14.3.59])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id QAA29019
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 16:43:21 -0400 (EDT)
Received: by pai820exch001h.micro.lucent.com with Internet Mail Service (5.5.2448.0)
	id <MXDLQ7WS>; Mon, 21 Jun 1999 16:43:20 -0400
Message-ID: <4624C75E76CBD111B43500805F6FA8C103C3F4CB@pai820exch001u.micro.lucent.com>
From: "Waldo, Michael (Michael)" <waldo@lucent.com>
To: "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
Subject: PPP over SONET Signal Label
Date: Mon, 21 Jun 1999 16:43:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

A question about the SONET Path Signal Label with PPP,...

In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label (C2
Byte) of  16(hex) is "PPP with X^43 + 1 scrambling". 

GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
16(hex) as "HDLC-Over-SONET Mapping". 

I couldn't find a signal label of 16(hex) in T1.105 or G.707.

Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
understand that the PPP over SONET is HDLC framed, but is a different Signal
Label needed to differentiate between HDLC framed data ( NOT PPP), and PPP
data in a HDLC frame?

Thanks,
-Waldo

=================================================================
Michael Waldo                                                    
Lucent Technologies                          (Phone) 972.733.2743
17090 Dallas Parkway, Dallas, TX 75248       (Fax)   972.733.8686
email: waldo@lucent.com <mailto:waldo@lucent.com>




From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 17:05:11 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10440
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 17:05:11 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id CF5B54442A; Mon, 21 Jun 1999 17:04:49 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id A8CE34442B; Mon, 21 Jun 1999 17:04:49 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by segue.merit.edu (Postfix) with ESMTP id A38B54442A
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 17:04:47 -0400 (EDT)
Received: from apollo13.casc.com (apollo13 [152.148.10.13])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id RAA03018;
	Mon, 21 Jun 1999 17:04:41 -0400 (EDT)
Received: from localhost by apollo13.casc.com (8.8.8+Sun/SMI-SVR4)
	id RAA23773; Mon, 21 Jun 1999 17:04:41 -0400 (EDT)
Date: Mon, 21 Jun 1999 17:04:41 -0400 (EDT)
From: "Andrew G. Malis" <amalis@casc.com>
X-Sender: amalis@apollo13
To: "Waldo, Michael (Michael)" <waldo@lucent.com>
Cc: "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
Subject: Re: PPP over SONET Signal Label
In-Reply-To: <4624C75E76CBD111B43500805F6FA8C103C3F4CB@pai820exch001u.micro.lucent.com>
Message-ID: <Pine.GSO.4.10.9906211655380.23746-100000@apollo13>
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

Michael,

> A question about the SONET Path Signal Label with PPP,...
> 
> In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label (C2
> Byte) of  16(hex) is "PPP with X^43 + 1 scrambling". 
> 
> GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
> 16(hex) as "HDLC-Over-SONET Mapping". 
> 
> I couldn't find a signal label of 16(hex) in T1.105 or G.707.

You have to look in the 1998 updates to T1.105 and G.707.  You can see
the exact the updates to G.707 in the study group 15 meeting report
from 9-20 Feb. 1998, questions 9-14/15, working party 3.

> Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
> understand that the PPP over SONET is HDLC framed, but is a different Signal
> Label needed to differentiate between HDLC framed data ( NOT PPP), and PPP
> data in a HDLC frame?

I think the Bellcore folks got this wrong.

Cheers,
Andy
________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886




From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 17:45:31 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11255
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 17:45:31 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DBAA14442B; Mon, 21 Jun 1999 17:45:03 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9E63F4442D; Mon, 21 Jun 1999 17:45:03 -0400 (EDT)
Received: from sulu.tdd.hbo.nec.com (unknown [131.241.46.193])
	by segue.merit.edu (Postfix) with ESMTP id F2D0C4442B
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 17:45:01 -0400 (EDT)
Received: from [131.241.46.66](really [131.241.46.66]) by sulu.tdd.hbo.nec.com
	via sendmail with esmtp
	id <m10wBsB-000tRfC@sulu.tdd.hbo.nec.com>
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 14:44:59 -0700 (PDT)
	(Smail-3.2 1996-Jul-4 #4 built 1998-Apr-6)
X-Sender: steveg@sulu.tdd.hbo.nec.com
Message-Id: <v03007803b3946133657e@[131.241.46.66]>
In-Reply-To: 
 <4624C75E76CBD111B43500805F6FA8C103C3F4CB@pai820exch001u.micro.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 21 Jun 1999 14:51:23 -0700
To: "Waldo, Michael (Michael)" <waldo@lucent.com>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
From: Steve Gorshe <steveg@tdd.hbo.nec.com>
Subject: Re: PPP over SONET Signal Label
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Michael,

Hope this helps.

At 1:43 PM -0700 6/21/99, Waldo, Michael (Michael) wrote:
>A question about the SONET Path Signal Label with PPP,...
>
>In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label (C2
>Byte) of  16(hex) is "PPP with X^43 + 1 scrambling".
>
>GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
>16(hex) as "HDLC-Over-SONET Mapping".
>
>I couldn't find a signal label of 16(hex) in T1.105 or G.707.

This is the correct signal label.  T1.105 is currently being updated.  The
latest draft can be found at the Committee T1 web site.  Go to www.t1.org
and follow the links to T1X1 and to the 1999 uploaded contributions of the
T1X1.5 working goup.  Draft T1.105 is listed there as document number
9x150640.pdf.

>Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
>understand that the PPP over SONET is HDLC framed, but is a different Signal
>Label needed to differentiate between HDLC framed data ( NOT PPP), and PPP
>data in a HDLC frame?

There is only the HDLC-Over-SONET signal label.  There is nothing different
for PPP since the PPP uses HDLC framing.

Regards,

Steve Gorshe

T1X1 Chief Editor
T1.105 Technical Editor

NEC Eluminant Technologies
steveg@eluminant.com





From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 21:11:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13119
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 21:11:42 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 661AE44405; Mon, 21 Jun 1999 21:11:03 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 3FE814440C; Mon, 21 Jun 1999 21:11:03 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by segue.merit.edu (Postfix) with ESMTP id D663144405
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 21:11:01 -0400 (EDT)
Received: from amalis ([152.148.173.142])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id VAA01391;
	Mon, 21 Jun 1999 21:10:58 -0400 (EDT)
Message-Id: <4.2.0.56.19990621205639.00df1da0@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Mon, 21 Jun 1999 21:10:54 -0400
To: "Waldo, Michael (Michael)" <waldo@lucent.com>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
From: "Andrew G. Malis" <malis@casc.com>
Subject: Re: PPP over SONET Signal Label
Cc: "Andrew G. Malis" <malis@casc.com>
In-Reply-To: <Pine.GSO.4.10.9906211655380.23746-100000@apollo13>
References: <4624C75E76CBD111B43500805F6FA8C103C3F4CB@pai820exch001u.micro.lucent.com>
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

Michael et al,

A correction to my earlier message:

Now that I had a little more time available, I just reread the ITU changes 
to G.707.  The Path Signal Label is now specified as:

Code "16" assigned for mapping of HDLC according to 10.3/G.707.
Code "CF" assigned for mapping of HDLC according to IETF RFC 1619.

The new text in section 10.3/G.707 describes how to encode any HDLC frames 
(not just PPP) using the x^43+1 scrambler.  So Bellcore got it partially 
right, in that 0x16 is not restricted to PPP, but they apparently neglected 
to mention the scrambler in GR-253.

I also think that this was the right thing to do, rather than try to 
enumerate a label for every variant of HDLC, since the SONET mapping is the 
same for all of them anyway.

Cheers,
Andy

--------

At 05:04 PM 6/21/99 -0400, Andrew G. Malis wrote:
>Michael,
>
> > A question about the SONET Path Signal Label with PPP,...
> >
> > In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label (C2
> > Byte) of  16(hex) is "PPP with X^43 + 1 scrambling".
> >
> > GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
> > 16(hex) as "HDLC-Over-SONET Mapping".
> >
> > I couldn't find a signal label of 16(hex) in T1.105 or G.707.
>
>You have to look in the 1998 updates to T1.105 and G.707.  You can see
>the exact the updates to G.707 in the study group 15 meeting report
>from 9-20 Feb. 1998, questions 9-14/15, working party 3.
>
> > Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
> > understand that the PPP over SONET is HDLC framed, but is a different 
> Signal
> > Label needed to differentiate between HDLC framed data ( NOT PPP), and PPP
> > data in a HDLC frame?
>
>I think the Bellcore folks got this wrong.
>
>Cheers,
>Andy
>________________________________________________________________________
>Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
>Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886




From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 22:21:00 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14475
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 22:21:00 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 17AE84440C; Mon, 21 Jun 1999 22:20:12 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id E59A544411; Mon, 21 Jun 1999 22:20:11 -0400 (EDT)
Received: from ns1.siara.com (fci2.siara.com [209.31.24.130])
	by segue.merit.edu (Postfix) with SMTP id 4BBAB4440C
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 22:20:10 -0400 (EDT)
Received: from siara-serv1. by ns1.siara.com
          via smtpd (for segue.merit.edu [198.108.1.41]) with SMTP; 22 Jun 1999 02:49:43 UT
Received: from siara.com by siara.com with esmtp
	id m10wG9T-001FJQC; Mon, 21 Jun 1999 19:19:07 -0700 (PDT)
Message-ID: <376EF2A2.EBA5215@siara.com>
Date: Mon, 21 Jun 1999 19:19:14 -0700
From: Mathew Joy <mjjoy@siara.com>
Organization: Siara Systems
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-ppp@merit.edu
Subject: CRC in PPP over Sonet
Content-Type: multipart/alternative;
 boundary="------------C8D088A7E7667EBEFFB93C91"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu


--------------C8D088A7E7667EBEFFB93C91
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

I was wondering if anybody could help me answer
a question I had regarding CRC's on PPP over Sonet.  Is the CRC a
negotiable
option (via LCP in PPP)  or is it always configured to be 32-bit?  If it
is configurable,
do you know any RFC's  that define what the CRC option number is for
LCP.

thanks,


-matt



--
Matt Joy (mjjoy@siara.com)
Siara Systems Inc.
(650) 237-3171



--------------C8D088A7E7667EBEFFB93C91
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hello,
<p>I was wondering if anybody could help me answer
<br>a question I had regarding CRC's on PPP over Sonet.&nbsp; Is the CRC
a negotiable
<br>option (via LCP in PPP)&nbsp; or is it always configured to be 32-bit?&nbsp;
If it is configurable,
<br>do you know any RFC's&nbsp; that define what the CRC option number
is for LCP.
<p>thanks,
<br>&nbsp;
<p>-matt
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
Matt Joy (mjjoy@siara.com)
Siara Systems Inc.
(650) 237-3171</pre>
&nbsp;</html>

--------------C8D088A7E7667EBEFFB93C91--




From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 21 22:34:38 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15474
	for <pppext-archive@odin.ietf.org>; Mon, 21 Jun 1999 22:34:38 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BFEFC44411; Mon, 21 Jun 1999 22:34:17 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9991644429; Mon, 21 Jun 1999 22:34:17 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by segue.merit.edu (Postfix) with ESMTP id 4FB4944411
	for <ietf-ppp@merit.edu>; Mon, 21 Jun 1999 22:34:16 -0400 (EDT)
Received: from amalis ([152.148.173.64])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id WAA08792;
	Mon, 21 Jun 1999 22:34:13 -0400 (EDT)
Message-Id: <4.2.0.56.19990621223028.01df6270@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Mon, 21 Jun 1999 22:34:08 -0400
To: Mathew Joy <mjjoy@siara.com>
From: "Andrew G. Malis" <malis@casc.com>
Subject: Re: CRC in PPP over Sonet
Cc: ietf-ppp@merit.edu
In-Reply-To: <376EF2A2.EBA5215@siara.com>
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

Matt,

 From draft-ietf-pppext-pppoversonet-update-04.txt:

    Regarding the FCS length, with one exception, the 32-bit FCS MUST be
    used for all SONET/SDH rates. For STS-3c-SPE/VC-4 only, the 16-bit
    FCS MAY be used, although the 32-bit FCS is RECOMMENDED.  The FCS
    length is set by provisioning and is not negotiated.

By the way, I'm told that RFC is scheduled to be announced Real Soon Now.
Watch your email ...

Regards,
Andy

-------

At 07:19 PM 6/21/99 -0700, Mathew Joy wrote:
>Hello,
>
>I was wondering if anybody could help me answer
>a question I had regarding CRC's on PPP over Sonet.  Is the CRC a negotiable
>option (via LCP in PPP)  or is it always configured to be 32-bit?  If it 
>is configurable,
>do you know any RFC's  that define what the CRC option number is for LCP.
>
>thanks,
>
>
>-matt

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 22 08:45:17 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03097
	for <pppext-archive@odin.ietf.org>; Tue, 22 Jun 1999 08:45:17 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id EADB244432; Tue, 22 Jun 1999 08:44:37 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C160244430; Tue, 22 Jun 1999 08:44:37 -0400 (EDT)
Received: from aperol.lkn.e-technik.tu-muenchen.de (aperol.LKN.E-Technik.TU-Muenchen.DE [129.187.222.163])
	by segue.merit.edu (Postfix) with ESMTP id F25FC44432
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 08:44:30 -0400 (EDT)
Received: from ei.tum.de (orion.LKN.E-Technik.TU-Muenchen.DE [129.187.222.18])
	by aperol.lkn.e-technik.tu-muenchen.de (8.9.3/8.9.3) with ESMTP id OAA00948
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 14:44:28 +0200
Message-ID: <376F852C.330CA287@ei.tum.de>
Date: Tue, 22 Jun 1999 14:44:28 +0200
From: Dominic Schupke <Dominic.Schupke@ei.tum.de>
Organization: LKN TUM http://www.lkn.ei.tum.de
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-ppp@merit.edu
Subject: SDL Performance
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Hello,

In the SDL specification (http://www.lucent.com/micro/tic/docs/sdl.pdf)
I interpreted the results for service unavailability (and thus Mean Time
To Frame) in dependence on the number of framers as been calculated for
the octet-synchronous case, e.g. PPP/SDL/SDH (draft-ietf-pppext-sdl-02).
Are there any calculations available for the bit-synchronous case?

Best regards,
Dominic Schupke

-- 
Dominic A. Schupke 
Institute of Communication Networks, Munich University of Technology
Building 9, 1st floor, Room 1910, Arcisstr. 21, 80290 Munich, Germany
Tel.: +49 (0)89/289-2-3511, Fax: +49 (0)89/289-6-3511



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 22 10:38:01 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05380
	for <pppext-archive@odin.ietf.org>; Tue, 22 Jun 1999 10:38:00 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6E9EB4440D; Tue, 22 Jun 1999 10:37:33 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 45E3044419; Tue, 22 Jun 1999 10:37:33 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by segue.merit.edu (Postfix) with ESMTP id 5AB154440D
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 10:37:29 -0400 (EDT)
Received: from amalis (amalis [152.148.13.74])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id KAA00368;
	Tue, 22 Jun 1999 10:37:00 -0400 (EDT)
Message-Id: <4.2.0.56.19990622103239.01cf6760@alpo.casc.com>
X-Sender: amalis@alpo.casc.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Tue, 22 Jun 1999 10:34:08 -0400
To: "Tim Armstrong" <tim@nortelnetworks.com>
From: "Andrew G. Malis" <malis@casc.com>
Subject: RE: PPP over SONET Signal Label
Cc: "'Andrew G. Malis'" <malis@casc.com>,
        "Waldo, Michael (Michael)" <waldo@lucent.com>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
In-Reply-To: <FF7BD1DFC2ABD211A7580000F81AEB7641FD50@zmerd00d.ca.nortel.
 com>
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

Tim,

Many thanks for the clarification - I haven't had a chance to see the 
GR.  I'm glad to hear it's consistent with the rest of the world.

Cheers,
Andy

-------

At 10:03 AM 6/22/99 -0400, Tim Armstrong wrote:
>See requirement R3-75 in section 3.4.2.3 of Bellcore
>GR-253-CORE, Issue 2, Revision 2, January 1999. It
>clearly states the need for the payload scrambler for
>HDLC-framed payloads as well as detailing the scrambler
>type and application.
>
>Bellcore GR-253-CORE specifies a single Path Signal Label
>value (16 hex) for scrambled, HDLC-framed payloads. That is
>consistent with the mapping and PSL value defined in ANSI
>T1.105.
>
>Tim Armstrong
>Nortel Networks
>
> > -----Original Message-----
> > From: Andrew G. Malis [SMTP:malis@casc.com]
> > Sent: Monday, June 21, 1999 9:11 PM
> > To:   Waldo, Michael (Michael); 'ietf-ppp@merit.edu'
> > Cc:   Andrew G. Malis
> > Subject:      Re: PPP over SONET Signal Label
> >
> > Michael et al,
> >
> > A correction to my earlier message:
> >
> > Now that I had a little more time available, I just reread the ITU changes
> >
> > to G.707.  The Path Signal Label is now specified as:
> >
> > Code "16" assigned for mapping of HDLC according to 10.3/G.707.
> > Code "CF" assigned for mapping of HDLC according to IETF RFC 1619.
> >
> > The new text in section 10.3/G.707 describes how to encode any HDLC frames
> >
> > (not just PPP) using the x^43+1 scrambler.  So Bellcore got it partially
> > right, in that 0x16 is not restricted to PPP, but they apparently
> > neglected
> > to mention the scrambler in GR-253.
> >
> > I also think that this was the right thing to do, rather than try to
> > enumerate a label for every variant of HDLC, since the SONET mapping is
> > the
> > same for all of them anyway.
> >
> > Cheers,
> > Andy
> >
> > --------
> >
> > At 05:04 PM 6/21/99 -0400, Andrew G. Malis wrote:
> > >Michael,
> > >
> > > > A question about the SONET Path Signal Label with PPP,...
> > > >
> > > > In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label
> > (C2
> > > > Byte) of  16(hex) is "PPP with X^43 + 1 scrambling".
> > > >
> > > > GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
> > > > 16(hex) as "HDLC-Over-SONET Mapping".
> > > >
> > > > I couldn't find a signal label of 16(hex) in T1.105 or G.707.
> > >
> > >You have to look in the 1998 updates to T1.105 and G.707.  You can see
> > >the exact the updates to G.707 in the study group 15 meeting report
> > >from 9-20 Feb. 1998, questions 9-14/15, working party 3.
> > >
> > > > Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
> > > > understand that the PPP over SONET is HDLC framed, but is a different
> > > Signal
> > > > Label needed to differentiate between HDLC framed data ( NOT PPP), and
> > PPP
> > > > data in a HDLC frame?
> > >
> > >I think the Bellcore folks got this wrong.
> > >
> > >Cheers,
> > >Andy

________________________________________________________________________
Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 22 10:44:53 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05522
	for <pppext-archive@odin.ietf.org>; Tue, 22 Jun 1999 10:44:53 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 932A044419; Tue, 22 Jun 1999 10:44:09 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9162444434; Tue, 22 Jun 1999 10:44:08 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 7FE2344419
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 10:44:06 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id KAA16114 for ietf-ppp@merit.edu; Tue, 22 Jun 1999 10:44:06 -0400 (EDT)
Received: from smtprich.nortel.com (smtprich.nortel.com [192.135.215.8])
	by segue.merit.edu (Postfix) with ESMTP id 1F10A4440D
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 10:07:07 -0400 (EDT)
Received: from zrtpd004.us.nortel.com (actually nrtpd004) 
          by smtprich.nortel.com; Tue, 22 Jun 1999 09:05:46 -0500
Received: by zrtpd004.us.nortel.com with Internet Mail Service (5.5.2448.0) 
          id <NM1946ND>; Tue, 22 Jun 1999 10:03:31 -0400
Message-ID: <FF7BD1DFC2ABD211A7580000F81AEB7641FD50@zmerd00d.ca.nortel.com>
From: "Tim Armstrong" <tim@nortelnetworks.com>
To: "'Andrew G. Malis'" <malis@casc.com>,
        "Waldo, Michael (Michael)" <waldo@lucent.com>,
        "'ietf-ppp@merit.edu'" <ietf-ppp@merit.edu>
Subject: RE: PPP over SONET Signal Label
Date: Tue, 22 Jun 1999 10:03:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

See requirement R3-75 in section 3.4.2.3 of Bellcore
GR-253-CORE, Issue 2, Revision 2, January 1999. It
clearly states the need for the payload scrambler for
HDLC-framed payloads as well as detailing the scrambler
type and application.

Bellcore GR-253-CORE specifies a single Path Signal Label
value (16 hex) for scrambled, HDLC-framed payloads. That is
consistent with the mapping and PSL value defined in ANSI
T1.105.

Tim Armstrong
Nortel Networks

> -----Original Message-----
> From:	Andrew G. Malis [SMTP:malis@casc.com]
> Sent:	Monday, June 21, 1999 9:11 PM
> To:	Waldo, Michael (Michael); 'ietf-ppp@merit.edu'
> Cc:	Andrew G. Malis
> Subject:	Re: PPP over SONET Signal Label
> 
> Michael et al,
> 
> A correction to my earlier message:
> 
> Now that I had a little more time available, I just reread the ITU changes
> 
> to G.707.  The Path Signal Label is now specified as:
> 
> Code "16" assigned for mapping of HDLC according to 10.3/G.707.
> Code "CF" assigned for mapping of HDLC according to IETF RFC 1619.
> 
> The new text in section 10.3/G.707 describes how to encode any HDLC frames
> 
> (not just PPP) using the x^43+1 scrambler.  So Bellcore got it partially 
> right, in that 0x16 is not restricted to PPP, but they apparently
> neglected 
> to mention the scrambler in GR-253.
> 
> I also think that this was the right thing to do, rather than try to 
> enumerate a label for every variant of HDLC, since the SONET mapping is
> the 
> same for all of them anyway.
> 
> Cheers,
> Andy
> 
> --------
> 
> At 05:04 PM 6/21/99 -0400, Andrew G. Malis wrote:
> >Michael,
> >
> > > A question about the SONET Path Signal Label with PPP,...
> > >
> > > In draft-ietf-pppext-pppoversonet-update-04.txt a Path Signal Label
> (C2
> > > Byte) of  16(hex) is "PPP with X^43 + 1 scrambling".
> > >
> > > GR-253 (Bellcore GR-253-CORE Issue 2, with revision 2) lists a PSL of
> > > 16(hex) as "HDLC-Over-SONET Mapping".
> > >
> > > I couldn't find a signal label of 16(hex) in T1.105 or G.707.
> >
> >You have to look in the 1998 updates to T1.105 and G.707.  You can see
> >the exact the updates to G.707 in the study group 15 meeting report
> >from 9-20 Feb. 1998, questions 9-14/15, working party 3.
> >
> > > Is there a difference between HDLC-Over-SONET, and PPP over SONET? I
> > > understand that the PPP over SONET is HDLC framed, but is a different 
> > Signal
> > > Label needed to differentiate between HDLC framed data ( NOT PPP), and
> PPP
> > > data in a HDLC frame?
> >
> >I think the Bellcore folks got this wrong.
> >
> >Cheers,
> >Andy
> >________________________________________________________________________
> >Andrew G. Malis  malis@ascend.com  phone:978 952-7414   fax:978 392-2074
> >Ascend Communications, Inc.        1 Robbins Road     Westford, MA 01886
> 
> 




From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 22 11:10:52 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05999
	for <pppext-archive@odin.ietf.org>; Tue, 22 Jun 1999 11:10:52 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id B71AC44435; Tue, 22 Jun 1999 11:10:18 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 9118F44436; Tue, 22 Jun 1999 11:10:18 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 95DDA44435
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 11:10:17 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id LAA17992 for ietf-ppp@merit.edu; Tue, 22 Jun 1999 11:10:17 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by segue.merit.edu (Postfix) with ESMTP id 052444440D
	for <ietf-ppp@merit.edu>; Tue, 22 Jun 1999 10:29:48 -0400 (EDT)
Received: from hoserve.ho.lucent.com (h135-17-35-10.lucent.com [135.17.35.10])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id KAA26959;
	Tue, 22 Jun 1999 10:29:47 -0400 (EDT)
From: enrique@lucent.com
Received: from hopaw32 by hoserve.ho.lucent.com (SMI-8.6/EMS-1.4.1 sol2)
	id KAA20865; Tue, 22 Jun 1999 10:35:38 -0400
Received: by hopaw32 (8.8.8+Sun/EMS-1.1.1 SunOS)
	id KAA02012; Tue, 22 Jun 1999 10:35:34 -0400 (EDT)
Date: Tue, 22 Jun 1999 10:35:34 -0400 (EDT)
Message-Id: <199906221435.KAA02012@hopaw32>
To: ietf-ppp@merit.edu, Dominic.Schupke@ei.tum.de
Subject: Re: SDL Performance
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: VrPg4+yDsZlFzFryPwZRrw==
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Dominic,

You'll find the results for the bit-synchronous case in the soon 
to be posted I-D on SDL on Packet-over-lightwave (POL).


Enrique J. Hernandez-Valencia		Phone: (732) 949-6153
Bell Laboratories, 3H-313		FAX:   (732) 834-5906
Holmdel, NJ 07733-3020, USA		Email: enrique@bell-labs.com



> From owner-ietf-ppp-outgoing@merit.edu Tue Jun 22 08:50:59 1999
> Delivered-To: ietf-ppp-outgoing@merit.edu
> From: Dominic Schupke <Dominic.Schupke@ei.tum.de>
> X-Accept-Language: en
> MIME-Version: 1.0
> To: ietf-ppp@merit.edu
> Subject: SDL Performance
> Content-Transfer-Encoding: 7bit
> X-Status: $$$$
> X-UID: 0000003816
> 
> Hello,
> 
> In the SDL specification (http://www.lucent.com/micro/tic/docs/sdl.pdf)
> I interpreted the results for service unavailability (and thus Mean Time
> To Frame) in dependence on the number of framers as been calculated for
> the octet-synchronous case, e.g. PPP/SDL/SDH (draft-ietf-pppext-sdl-02).
> Are there any calculations available for the bit-synchronous case?
> 
> Best regards,
> Dominic Schupke
> 
> -- 
> Dominic A. Schupke 
> Institute of Communication Networks, Munich University of Technology
> Building 9, 1st floor, Room 1910, Arcisstr. 21, 80290 Munich, Germany
> Tel.: +49 (0)89/289-2-3511, Fax: +49 (0)89/289-6-3511
> 




From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 23 13:11:43 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06169
	for <pppext-archive@odin.ietf.org>; Wed, 23 Jun 1999 13:11:43 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4A6FB44430; Wed, 23 Jun 1999 13:11:03 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 22C5844452; Wed, 23 Jun 1999 13:11:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id EE13844430
	for <ietf-ppp@merit.edu>; Wed, 23 Jun 1999 13:10:59 -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 NAA06063;
	Wed, 23 Jun 1999 13:10:56 -0400 (EDT)
Message-Id: <199906231710.NAA06063@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-l2tp-atmext-01.txt
Date: Wed, 23 Jun 1999 13:10:56 -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		: Layer Two Tunnelling Protocol : ATM access network 
                          extensions.
	Author(s)	: Y. T'Joens,  P. Crivellari,  L. Hermans, B. Sales 
	Filename	: draft-ietf-pppext-l2tp-atmext-01.txt
	Pages		: 14
	Date		: 22-Jun-99
	
The L2TP working draft describes a protocol which permits the
tunnelling of the link layer of PPP. This document augments the
procedures described in the L2TP working draft to support ATM SVC or
PVC based access networks. The necessary extensions to the L2TP
working draft are defined in order to allow for asymmetric bi-
directional call establishment in the access network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-l2tp-atmext-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-l2tp-atmext-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-l2tp-atmext-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.

--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:	<19990622132337.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-l2tp-atmext-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 23 14:45:45 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09229
	for <pppext-archive@odin.ietf.org>; Wed, 23 Jun 1999 14:45:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 0DFC144452; Wed, 23 Jun 1999 14:45:04 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 5867244455; Wed, 23 Jun 1999 14:45:02 -0400 (EDT)
Received: from cheetah.safari.net (cheetah.safari.net [206.96.248.28])
	by segue.merit.edu (Postfix) with SMTP id 8764244448
	for <ietf-ppp@merit.edu>; Wed, 23 Jun 1999 14:44:59 -0400 (EDT)
Received: (qmail 15864 invoked from network); 23 Jun 1999 18:44:54 -0000
Received: from rhino.safari.net (HELO noc) (qmailr@208.235.96.54)
  by smtp.safari.net with SMTP; 23 Jun 1999 18:44:54 -0000
Received: (qmail 28084 invoked by uid 500); 23 Jun 1999 18:44:48 -0000
From: xs-dated-97aaf14b045f469b@rhino.safari.net
Received: (qmail 28072 invoked from network); 23 Jun 1999 18:44:45 -0000
Received: from katanga.safari.net (HELO mail1.safari.net) (qmailr@206.96.248.4) by rhino.safari.net with SMTP; 23 Jun 1999 18:44:45 -0000
Received: (qmail 1051 invoked by uid 2600); 23 Jun 1999 18:43:35 -0000
Received: (qmail 1039 invoked from network); 23 Jun 1999 18:43:33 -0000
Received: from loki.ietf.org (132.151.1.177) by mail1.safari.net with SMTP; 23 Jun 1999 18:43:32 -0000
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA05437 for ietf-123-outbound.09@ietf.org; Wed, 23 Jun 1999 13:45:01 -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 NAA04839 for <all-ietf@loki.ietf.org>; Wed, 23 Jun 1999 13:14:53 -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 NAA06063; Wed, 23 Jun 1999 13:10:56 -0400 (EDT)
Message-Id: <199906231710.NAA06063@ietf.org>
Mime-Version: 1.0
X-Security: MIME headers sanitized on rhino See http://www.wolfenet.com/~jhardin/procmail-security.html for details. $Revision: 1.84 $Date: 1999-06-12 12:30:37-07 
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ietf-ppp@merit.edu
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pppext-l2tp-atmext-01.txt
Date: Wed, 23 Jun 1999 13:10:56 -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		: Layer Two Tunnelling Protocol : ATM access network 
                          extensions.
	Author(s)	: Y. T'Joens,  P. Crivellari,  L. Hermans, B. Sales 
	Filename	: draft-ietf-pppext-l2tp-atmext-01.txt
	Pages		: 14
	Date		: 22-Jun-99
	
The L2TP working draft describes a protocol which permits the
tunnelling of the link layer of PPP. This document augments the
procedures described in the L2TP working draft to support ATM SVC or
PVC based access networks. The necessary extensions to the L2TP
working draft are defined in order to allow for asymmetric bi-
directional call establishment in the access network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-l2tp-atmext-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-l2tp-atmext-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-l2tp-atmext-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.

--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:	<19990622132337.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-l2tp-atmext-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 10:48:09 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15015
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 10:48:09 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 29F4C44428; Thu, 24 Jun 1999 10:47:21 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 0034844455; Thu, 24 Jun 1999 10:47:20 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id 8C56C44428
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 10:47:19 -0400 (EDT)
Received: from bluegill ([12.17.197.129]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA6F5F;
          Thu, 24 Jun 1999 10:47:19 -0400
Message-Id: <4.2.0.56.19990624104125.009bbec0@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 24 Jun 1999 10:46:57 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: New PPPEXT Working Group Charter *with* *milestones*
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

Here's the new PPPEXT working group charter with actual milestones, which I
made up based on comments I received from the group.  Please look it over,
but don't panic if something seems awry--we'll be updating it after Oslo.

Karl

Description of Working Group:
-----------------------------
Note: A separate list has been set up for L2TP discussions:

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

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

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

Goals and Milestones:
---------------------
Aug 1999 Advance L2TP MIB to Proposed Standard
Aug 1999 Advance SDL draft to Experimental
Aug 1999 Advance AODI draft to Proposed Standard
Dec 1999 Advance CHAP (RFC 1994) to Standard
Dec 1999 Advance Multilink (RFC 1990) to Standard
Dec 1999 Advance LQM (RFC 1989) to Standard
Dec 1999 Advance IPCP (RFC 1332) to Draft Standard
Dec 1999 Advance BCP (RFC 1638) to Draft Standard
Dec 1999 Advance CCP (RFC 1962) to Draft Standard
Dec 1999 Advance ECP (RFC 1968) to Draft Standard
Dec 1999 Advance PPP over ISDN (RFC 1618) to Draft Standard
Mar 2000 Advance L2TP to Draft Standard
Mar 2000 Advance L2TP MIB to Draft Standard
Mar 2000 Advance AODI to Draft Standard
Mar 2000 Advance LCP MIB (RFC 1471) to Draft Standard
Mar 2000 Advance CHAP MIB (RFC 1472) to Draft Standard
Mar 2000 Advance IPCP MIB (RFC 1473) to Draft Standard
Mar 2000 Advance BCP MIB (RFC 1474) to Draft Standard
Dec 2000 Advance IPCP (RFC 1332) to Standard
Dec 2000 Advance BCP (RFC 1638) to Standard
Dec 2000 Advance CCP (RFC 1962) to Standard
Dec 2000 Advance ECP (RFC 1968) to Standard
Dec 2000 Advance PPP over ISDN (RFC 1618) to Draft Standard
Mar 2001 Advance L2TP to Standard
Mar 2001 Advance L2TP MIB to Standard
Mar 2001 Advance AODI to Standard
Mar 2001 Advance LCP MIB (RFC 1471) to Standard
Mar 2001 Advance CHAP MIB (RFC 1472) to Standard
Mar 2001 Advance IPCP MIB (RFC 1473) to Standard
Mar 2001 Advance BCP MIB (RFC 1474) to Standard


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



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 11:17:31 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15625
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 11:17:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 131BF44459; Thu, 24 Jun 1999 11:16:59 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D6BF944455; Thu, 24 Jun 1999 11:16:58 -0400 (EDT)
Received: from alpha.shiva.com (eagle-ext.shiva.com [192.80.57.28])
	by segue.merit.edu (Postfix) with ESMTP id 43AF544459
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 11:16:57 -0400 (EDT)
Received: from brill.shiva.com (brill.shiva.com [140.248.193.94])
	by alpha.shiva.com (8.8.8/8.8.8) with SMTP id LAA08467;
	Thu, 24 Jun 1999 11:16:46 -0400 (EDT)
Received: by brill.shiva.com (SMI-8.6/SMI-SVR4)
	id LAA27767; Thu, 24 Jun 1999 11:16:52 -0400
Date: Thu, 24 Jun 1999 11:16:52 -0400
Message-Id: <199906241516.LAA27767@brill.shiva.com>
From: John Shriver <jas@shiva.com>
To: karl@extant.net
Cc: ietf-ppp@merit.edu
In-reply-to: <4.2.0.56.19990624104125.009bbec0@mail.extant.net>
	(karl@extant.net)
Subject: Re: New PPPEXT Working Group Charter *with* *milestones*
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

IPXCP should move on to Draft Standard.  That's the only non-IP
protocol with any shelf-life left.  Many implementations (Cisco,
Proteon/OpenRoute, Shiva/Intel, Novell).

There certainly are still multiple interoperable implementations of
DNCP (OpenRoute/Proteon, Cisco, and Cabletron/Digital).  It's still at
Draft Standard, and certainly is old enough to flip to standard.  No
controversy.

XNSCP did get interoperable implementations from Cisco and Proteon.
However, OpenRoute/Proteon dropped XNS from their products a while
ago.  (It's VERY hard to find anything to test against!)  Certainly
nothing will be controversial.

As for BVCP, that might just die on the Vine(s).  Implemented by Cisco
and Proteon/OpenRoute, but Proteon/OpenRoute has dropped support.

Maybe I'm hazy, but BACP is part of the AODI suite, right?  Only at
Proposed Standard.  We (Shiva) finally shipped our ipmlementation.

NBFCP?  I think Shiva (Intel) and Microsoft have interoperable
implementations.  (Yeah, it's ugly.)



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 13:25:51 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17994
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 13:25:51 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A0FBB4445E; Thu, 24 Jun 1999 13:18:18 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 768E44445D; Thu, 24 Jun 1999 13:18:18 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id D58D84445C
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 13:18:16 -0400 (EDT)
Received: from bluegill ([12.17.197.129]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA74D1;
          Thu, 24 Jun 1999 13:18:23 -0400
Message-Id: <4.2.0.56.19990624131227.05e44370@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Thu, 24 Jun 1999 13:17:57 -0400
To: ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Oslo PPPEXT Agenda
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

Here's the (semi) final PPPEXT agenda for Oslo.  There is still a little bit 
of time left, so if you don't want to be frozen out, send me a request right 
away.


PPP Extensions Working Group Agenda
45th IETF--Oslo, Norway

Wednesday, July 14, 1999, 1530-1730 
Opposite rmonmib, deltav, udlr, decides

Discussion of PPPEXT Standards Track Document Status
         Karl Fox <karl@extant.net>
[40 minutes]

PPP over SDL for packet over dark fiber channels
         James Carlson <carlson@ironbridgenetworks.com>
         Enrique Hernandez-Valencia <enrique@lucent.com>
         Nevin Jones <nrjones@lucent.com>
[15-20 minutes]

Mobile PPP
         M. Chuah <chuah@lucent.com>
[15 minutes]

Providing QoS in Multilink PPP
         M. Chuah <chuah@lucent.com>
         Enrique Hernandez-Valencia <enrique@lucent.com>
[15 minutes]


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



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 14:26:12 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19022
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 14:26:11 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 49BE44445C; Thu, 24 Jun 1999 14:25:48 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 208D24445D; Thu, 24 Jun 1999 14:25:48 -0400 (EDT)
Received: from ihemlsrv.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by segue.merit.edu (Postfix) with ESMTP id 9F6544445C
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 14:25:46 -0400 (EDT)
Received: from pai820exch001h.wins.lucent.com (h135-14-3-59.lucent.com [135.14.3.59])
	by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id OAA27431
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 14:25:46 -0400 (EDT)
Received: by pai820exch001h.micro.lucent.com with Internet Mail Service (5.5.2448.0)
	id <MXDL48SH>; Thu, 24 Jun 1999 14:25:45 -0400
Message-ID: <15A2D77655CDD1118B5500805F6FE87A026A7983@pai820exch002u.micro.lucent.com>
From: "Jones, Nevin R (Nevin)" <nrjones@lucent.com>
To: ietf-ppp@merit.edu, "'Karl Fox'" <karl@extant.net>
Cc: "Jones, Nevin R (Nevin)" <nrjones@lucent.com>,
        "Langner, Paul (Paul)" <plangner@lucent.com>
Subject: RE: Oslo PPPEXT Agenda
Date: Thu, 24 Jun 1999 14:25:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

Karl:

Chris Murton (Nortel Networks) and I (Nevin Jones, Lucent Technologies)
anticipate bringing a contribution on PPP over Virtually Concatenated
SONET/SDH Low and High Order Channels. 

We would appreciate some time on the agenda to present this contribution.

Thanks and Regards,

-Nevin Jones (nrjones@lucent.com)
 Chris Murton (murton@nortelnetworks.com)

> ----------
> From: 	Karl Fox[SMTP:karl@extant.net]
> Sent: 	Thursday, June 24, 1999 1:17 PM
> To: 	ietf-ppp@merit.edu
> Subject: 	Oslo PPPEXT Agenda
> 
> Here's the (semi) final PPPEXT agenda for Oslo.  There is still a little
> bit 
> of time left, so if you don't want to be frozen out, send me a request
> right 
> away.
> 
> 
> PPP Extensions Working Group Agenda
> 45th IETF--Oslo, Norway
> 
> Wednesday, July 14, 1999, 1530-1730 
> Opposite rmonmib, deltav, udlr, decides
> 
> Discussion of PPPEXT Standards Track Document Status
>          Karl Fox <karl@extant.net>
> [40 minutes]
> 
> PPP over SDL for packet over dark fiber channels
>          James Carlson <carlson@ironbridgenetworks.com>
>          Enrique Hernandez-Valencia <enrique@lucent.com>
>          Nevin Jones <nrjones@lucent.com>
> [15-20 minutes]
> 
> Mobile PPP
>          M. Chuah <chuah@lucent.com>
> [15 minutes]
> 
> Providing QoS in Multilink PPP
>          M. Chuah <chuah@lucent.com>
>          Enrique Hernandez-Valencia <enrique@lucent.com>
> [15 minutes]
> 
> 
> Karl Fox <karl@extant.net>
> Key fingerprint = 5B15 7260 D55E D680 0B93  4953 8A3B AB0E C05D 77A3
> 



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 15:42:09 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20541
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 15:42:09 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4C14444413; Thu, 24 Jun 1999 15:41:36 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 25AC44445A; Thu, 24 Jun 1999 15:41:36 -0400 (EDT)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by segue.merit.edu (Postfix) with ESMTP id B66D444413
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 15:41:34 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id PAA25123;
	Thu, 24 Jun 1999 15:41:29 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.3.1 sol2)
	id PAA10864; Thu, 24 Jun 1999 15:41:26 -0400
Message-ID: <3772893C.FEEA1441@hotair.hobl.lucent.com>
Date: Thu, 24 Jun 1999 15:38:36 -0400
From: Eve Varma <evarma@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.03 [en] (Win95; U)
MIME-Version: 1.0
To: "Jones, Nevin R (Nevin)" <nrjones@lucent.com>
Cc: ietf-ppp@merit.edu, "'Karl Fox'" <karl@extant.net>,
        "Langner, Paul (Paul)" <plangner@lucent.com>
Subject: Re: Oslo PPPEXT Agenda
References: <15A2D77655CDD1118B5500805F6FE87A026A7983@pai820exch002u.micro.lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Hi,
  It's my recollection that it's been agreed that contributions on
SONET/SDH mapping specifications should be directed towards T1X1 and
ITU-T SG 15 to be incorporated in the associated standards (which can
then be referenced by the IETF). 

If I've misinterpreted the focus of the contribution, please let me
know.  However, if not, I suggest this contribution be accordingly
targeted.
                      Cheers,
                        Eve



From owner-ietf-ppp-outgoing@merit.edu  Thu Jun 24 16:10:16 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21341
	for <pppext-archive@odin.ietf.org>; Thu, 24 Jun 1999 16:10:15 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id AEEDF4445A; Thu, 24 Jun 1999 16:09:53 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 89BF64445D; Thu, 24 Jun 1999 16:09:53 -0400 (EDT)
Received: from home.merit.edu (home.merit.edu [198.108.60.42])
	by segue.merit.edu (Postfix) with ESMTP id 872A24445A
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 16:09:52 -0400 (EDT)
Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id QAA12738 for ietf-ppp@merit.edu; Thu, 24 Jun 1999 16:09:52 -0400 (EDT)
Received: from srv-exchange2.adtran.com (mail-exch2.adtran.com [206.166.249.116])
	by segue.merit.edu (Postfix) with ESMTP id E54ED44413
	for <ietf-ppp@merit.edu>; Thu, 24 Jun 1999 15:39:38 -0400 (EDT)
Received: by srv-exchange2.adtran.com with Internet Mail Service (5.5.2448.0)
	id <NF3VWJRX>; Thu, 24 Jun 1999 14:43:47 -0500
Message-ID: <46476C008A10D311BD0A0000C0775CF920D3EA@srv-exchange.adtran.com>
From: KYLE FARNSWORTH <kyle.farnsworth@adtran.com>
To: John Shriver <jas@shiva.com>
Cc: ietf-ppp@merit.edu
Subject: RE: New PPPEXT Working Group Charter *with* *milestones*
Date: Thu, 24 Jun 1999 14:39:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu


> Maybe I'm hazy, but BACP is part of the AODI suite, right?  Only at
> Proposed Standard.  We (Shiva) finally shipped our implementation.
> 
That is correct.  BACP/BAP has a significant part in AODI.

Kyle Farnsworth
Adtran Inc.




From owner-ietf-ppp-outgoing@merit.edu  Fri Jun 25 18:39:31 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07166
	for <pppext-archive@odin.ietf.org>; Fri, 25 Jun 1999 18:39:30 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id F2D3E4441D; Fri, 25 Jun 1999 18:38:50 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id C7B614446D; Fri, 25 Jun 1999 18:38:50 -0400 (EDT)
Received: from alpo.casc.com (alpo.casc.com [152.148.10.6])
	by segue.merit.edu (Postfix) with ESMTP id CF4B44441D
	for <ietf-ppp@merit.edu>; Fri, 25 Jun 1999 18:38:43 -0400 (EDT)
Received: from apollo13.casc.com (apollo13 [152.148.10.13])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id SAA29460;
	Fri, 25 Jun 1999 18:38:26 -0400 (EDT)
Received: from localhost by apollo13.casc.com (8.8.8+Sun/SMI-SVR4)
	id SAA16476; Fri, 25 Jun 1999 18:38:26 -0400 (EDT)
Date: Fri, 25 Jun 1999 18:38:25 -0400 (EDT)
From: "Andrew G. Malis" <amalis@casc.com>
X-Sender: amalis@apollo13
To: ietf-ppp@merit.edu
Cc: "Andrew G. Malis" <malis@casc.com>
Subject: RFC 2615 on PPP over SONET/SDH  (fwd)
Message-ID: <Pine.GSO.4.10.9906251837540.16471-100000@apollo13>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.GSO.4.10.9906251837542.16471@apollo13>
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

FYI.

Andy

---------- Forwarded message ----------

Date: Thu, 24 Jun 1999 10:02:44 -0700
From: RFC Editor <rfc-ed@isi.edu>
To: IETF-Announce:  ;
Cc: rfc-ed@isi.edu
Subject: RFC 2615 on PPP over SONET/SDH 


A new Request for Comments is now available in online RFC libraries.

	RFC 2615:

        Title:	    PPP over SONET/SDH
	Author(s):  A. Malis, W. Simpson
        Status:     Proposed Standard
	Date:       June 1999
        Mailbox:    malis@ascend.com, wsimpson@GreenDragon.com
        Pages:      10
        Characters: 18708
	Obsoletes:  1619
        I-D Tag:    draft-ietf-pppext-pppoversonet-updates-04.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2615.txt


The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.  This
document describes the use of PPP over Synchronous Optical Network
(SONET) and Synchronous Digital Hierarchy (SDH) circuits.

This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF.

This docuemnt is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute




From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 28 07:55:08 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26242
	for <pppext-archive@odin.ietf.org>; Mon, 28 Jun 1999 07:55:08 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A98C544420; Mon, 28 Jun 1999 07:54:17 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 7E0F744421; Mon, 28 Jun 1999 07:54:17 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 0AA6044420
	for <ietf-ppp@merit.edu>; Mon, 28 Jun 1999 07:54:16 -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 HAA26219;
	Mon, 28 Jun 1999 07:54:12 -0400 (EDT)
Message-Id: <199906281154.HAA26219@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-l2tp-fr-02.txt
Date: Mon, 28 Jun 1999 07:54:11 -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		: Layer Two Tunneling Protocol (L2TP) over Frame Relay
	Author(s)	: V. Rawat, R. Tio,  R. Verma
 	Filename	: draft-ietf-pppext-l2tp-fr-02.txt
	Pages		: 7
	Date		: 25-Jun-99
	
Layer Two Tunneling Protocol describes a mechanism to
tunnel PPP sessions.  The protocol has been designed to be
independent of the media it runs over. The base
specification describes how it should be implemented to
run over UDP and IP. This document describes how the Layer
Two Tunneling Protocol MUST be implemented over Frame
Relay PVCs and SVCs.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-l2tp-fr-02.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 28 07:55:57 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26268
	for <pppext-archive@odin.ietf.org>; Mon, 28 Jun 1999 07:55:57 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 3BB4B44409; Mon, 28 Jun 1999 07:54:12 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 15BBA44418; Mon, 28 Jun 1999 07:54:12 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 1416F44409
	for <ietf-ppp@merit.edu>; Mon, 28 Jun 1999 07:54:09 -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 HAA26207;
	Mon, 28 Jun 1999 07:54:05 -0400 (EDT)
Message-Id: <199906281154.HAA26207@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-l2tp-mib-04.txt
Date: Mon, 28 Jun 1999 07:54:05 -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		: Layer Two Tunneling Protocol 'L2TP' Management 
                          Information Base
	Author(s)	: E. Caves, P. Calhoun, R. Wheeler
	Filename	: draft-ietf-pppext-l2tp-mib-04.txt
	Pages		: 65
	Date		: 25-Jun-99
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing networks using Layer 2
Tunneling Protocol.
This memo specifies a MIB module in a manner that is both compliant
to the SNMPv2 SMI, and semantically identical to the peer SNMPv1
definitions.

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

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

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 28 12:31:29 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05776
	for <pppext-archive@odin.ietf.org>; Mon, 28 Jun 1999 12:31:28 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id BFDEB44421; Mon, 28 Jun 1999 12:30:44 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 995C544429; Mon, 28 Jun 1999 12:30:44 -0400 (EDT)
Received: from aperol.lkn.e-technik.tu-muenchen.de (aperol.LKN.E-Technik.TU-Muenchen.DE [129.187.222.163])
	by segue.merit.edu (Postfix) with ESMTP id 371A944421
	for <ietf-ppp@merit.edu>; Mon, 28 Jun 1999 12:30:42 -0400 (EDT)
Received: from ei.tum.de (ds@wega [129.187.222.3])
	by aperol.lkn.e-technik.tu-muenchen.de (8.9.3/8.9.3) with ESMTP id SAA13314;
	Mon, 28 Jun 1999 18:30:11 +0200
Message-ID: <3777A313.ED94EAD@ei.tum.de>
Date: Mon, 28 Jun 1999 18:30:11 +0200
From: Dominic Schupke <Dominic.Schupke@ei.tum.de>
Organization: LKN TUM http://www.lkn.ei.tum.de
X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: enrique@lucent.com
Cc: ietf-ppp@merit.edu
Subject: Re: SDL Performance
References: <199906221435.KAA02012@hopaw32>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Dear Enrique,

Thank you for the information about SDL in bit-synchronous mode.

According to the performance results of the SDL specification in
octet-synchronous mode, the average overlap (given overlap) of all
framers being out-of-service is much less than 354 bytes for >=2 framers
and for consecutive 354-byte-packets, whereas for 1 framer the average
overlap is 32768 bytes. Did you assume for >=2 framers that the (false)
lengths found by the framers are maximal 354 bytes (i.e. equally
distributed between 0..354 bytes)?

Best regards,
Dominic Schupke

-- 
Dominic A. Schupke 
Institute of Communication Networks, Munich University of Technology
Building 9, 1st floor, Room 1910, Arcisstr. 21, 80290 Munich, Germany
Tel.: +49 (0)89/289-2-3511, Fax: +49 (0)89/289-6-3511



From owner-ietf-ppp-outgoing@merit.edu  Mon Jun 28 14:57:54 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10080
	for <pppext-archive@odin.ietf.org>; Mon, 28 Jun 1999 14:57:53 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id A413B4442F; Mon, 28 Jun 1999 14:57:20 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 79B4A44430; Mon, 28 Jun 1999 14:57:20 -0400 (EDT)
Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by segue.merit.edu (Postfix) with ESMTP id 982FF4442F
	for <ietf-ppp@merit.edu>; Mon, 28 Jun 1999 14:57:18 -0400 (EDT)
Received: from hoserve.ho.lucent.com (h135-17-35-10.lucent.com [135.17.35.10])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with SMTP id OAA13877;
	Mon, 28 Jun 1999 14:57:13 -0400 (EDT)
Received: from lucent.com by hoserve.ho.lucent.com (SMI-8.6/EMS-1.4.1 sol2)
	id PAA02079; Mon, 28 Jun 1999 15:02:58 -0400
Message-ID: <3777C4F0.F10B1116@lucent.com>
Date: Mon, 28 Jun 1999 14:54:40 -0400
From: "Enrique J. Hernandez-Valencia" <enrique@lucent.com>
Reply-To: enrique@bell-labs.com
Organization: Lucent Technologies
X-Mailer: Mozilla 4.06 [en]C-EMS-1.4  (Win95; U)
MIME-Version: 1.0
To: Dominic Schupke <Dominic.Schupke@ei.tum.de>
Cc: ietf-ppp@merit.edu
Subject: Re: SDL Performance
References: <199906221435.KAA02012@hopaw32> <3777A313.ED94EAD@ei.tum.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

Dominic Schupke wrote:

> According to the performance results of the SDL specification in
> octet-synchronous mode, the average overlap (given overlap) of all
> framers being out-of-service is much less than 354 bytes for >=2 framers
> and for consecutive 354-byte-packets, whereas for 1 framer the average
> overlap is 32768 bytes. Did you assume for >=2 framers that the (false)
> lengths found by the framers are maximal 354 bytes (i.e. equally
> distributed between 0..354 bytes)?
> 
> Best regards,
> Dominic Schupke

Yes we did. This is on the conservative side since the average Internet packet
size is typically a bit less than that.

Regards,

Enrique
> --
> Dominic A. Schupke
> Institute of Communication Networks, Munich University of Technology
> Building 9, 1st floor, Room 1910, Arcisstr. 21, 80290 Munich, Germany
> Tel.: +49 (0)89/289-2-3511, Fax: +49 (0)89/289-6-3511

-- 
======================================================================
Enrique J. Hernandez-Valencia		email:  enrique@lucent.com
Bell Laboratories				enrique@bell-labs.com
Lucent Technologies			
Room 3H-313				phone:	732-949-6153
Holmdel, NJ 07733, USA			fax:	732-834-5906
=====================================================================



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 29 05:24:20 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07732
	for <pppext-archive@odin.ietf.org>; Tue, 29 Jun 1999 05:24:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 07B544443C; Tue, 29 Jun 1999 05:23:34 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D65794443E; Tue, 29 Jun 1999 05:23:33 -0400 (EDT)
Received: from aperol.lkn.e-technik.tu-muenchen.de (aperol.LKN.E-Technik.TU-Muenchen.DE [129.187.222.163])
	by segue.merit.edu (Postfix) with ESMTP id 409864443C
	for <ietf-ppp@merit.edu>; Tue, 29 Jun 1999 05:23:31 -0400 (EDT)
Received: from ei.tum.de (ds@wega [129.187.222.3])
	by aperol.lkn.e-technik.tu-muenchen.de (8.9.3/8.9.3) with ESMTP id LAA14435;
	Tue, 29 Jun 1999 11:22:55 +0200
Message-ID: <3778906F.2247BD6B@ei.tum.de>
Date: Tue, 29 Jun 1999 11:22:55 +0200
From: Dominic Schupke <Dominic.Schupke@ei.tum.de>
Organization: LKN TUM http://www.lkn.ei.tum.de
X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: enrique@bell-labs.com
Cc: ietf-ppp@merit.edu
Subject: Re: SDL Performance
References: <199906221435.KAA02012@hopaw32> <3777A313.ED94EAD@ei.tum.de> <3777C4F0.F10B1116@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu
Content-Transfer-Encoding: 7bit

> Dominic Schupke wrote:
> > According to the performance results of the SDL specification in
> > octet-synchronous mode, the average overlap (given overlap) of all
> > framers being out-of-service is much less than 354 bytes for >=2 framers
> > and for consecutive 354-byte-packets, whereas for 1 framer the average
> > overlap is 32768 bytes. Did you assume for >=2 framers that the (false)
> > lengths found by the framers are maximal 354 bytes (i.e. equally
> > distributed between 0..354 bytes)?
> 
"Enrique J. Hernandez-Valencia" wrote:
> Yes we did. This is on the conservative side since the average Internet packet
> size is typically a bit less than that.
Is this feasible? Assuming that the (false) lengths found by the framers
are equally distributed between 0..l_max bytes (l_max << 65535) means
also that the framers have to be configured to find SDL frames with
lengths <= l_max only. Thus one has to restrict the payload length to
l_max.

Best regards,
Dominic

-- 
Dominic A. Schupke 
Institute of Communication Networks, Munich University of Technology
Building 9, 1st floor, Room 1910, Arcisstr. 21, 80290 Munich, Germany
Tel.: +49 (0)89/289-2-3511, Fax: +49 (0)89/289-6-3511



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 29 08:00:29 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09363
	for <pppext-archive@odin.ietf.org>; Tue, 29 Jun 1999 08:00:29 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 05F4944442; Tue, 29 Jun 1999 07:59:49 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id D572344443; Tue, 29 Jun 1999 07:59:48 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id 13AEE44442
	for <ietf-ppp@merit.edu>; Tue, 29 Jun 1999 07:59:47 -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 HAA09346;
	Tue, 29 Jun 1999 07:59:43 -0400 (EDT)
Message-Id: <199906291159.HAA09346@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-aodi-01.txt
Date: Tue, 29 Jun 1999 07:59:43 -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		: Always On Dynamic ISDN (AODI).
	Author(s)	: A. Kuzma, M. Holdrege
	Filename	: draft-ietf-pppext-aodi-01.txt
	Pages		: 16
	Date		: 28-Jun-99
	
Always On/Dynamic ISDN (AO/DI) is a networking service that provides
an always-available connection to TCP/IP-based services through a
specific wide area connection. This service provides several
advantages over current practices for dial-up access to Internet
services.
* For the end-user, there is no need to dial-up the service each
time access is desired.
* For the Internet service provider, it is possible to give the
end-user a notification, such as the arrival of new mail.
* For the Local Exchange Carrier, the switched circuit trunk
utilization is more efficient.

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

--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:	<19990628151846.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-aodi-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 29 11:42:06 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13798
	for <pppext-archive@odin.ietf.org>; Tue, 29 Jun 1999 11:42:06 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 5ECC044424; Tue, 29 Jun 1999 11:41:33 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 37A7F44439; Tue, 29 Jun 1999 11:41:33 -0400 (EDT)
Received: from sand5.global.net.uk (sand5.global.net.uk [194.126.80.249])
	by segue.merit.edu (Postfix) with ESMTP id CD5B844424
	for <ietf-ppp@merit.edu>; Tue, 29 Jun 1999 11:41:30 -0400 (EDT)
Received: from p7fs13a01.client.global.net.uk ([195.147.141.128] helo=hardy.farsite.co.uk)
	by sand5.global.net.uk with esmtp (Exim 2.05 #1)
	id 10z00m-0004d2-00
	for ietf-ppp@merit.edu; Tue, 29 Jun 1999 16:41:28 +0100
Received: by HARDY with Internet Mail Service (5.0.1457.3)
	id <N65FCHYN>; Tue, 29 Jun 1999 16:34:54 +0100
Message-ID: <D1E6783C663ED2119F91020701169FDD01676F@HARDY>
From: Jonathan Goodchild <jon.goodchild@farsite.co.uk>
To: ietf-ppp@merit.edu
Subject: draft-ietf-pppext-aodi-01.txt
Date: Tue, 29 Jun 1999 16:34:52 +0100
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

A few comments:

From Page 3:

>    The IETF provides some guidelines for the use of PPP over X.25 in
>    RFC 1598.  Strictly speaking, RFC 1598 does not apply to AO/DI, but
>    it has been used as a source of many useful concepts.

(It seems to me that had RFC 1598 been written properly, then it ought
to apply equally to X.25 over the ISDN D channel. Perhaps RFC 1598 ought
to be updated during the current phase of document maturation, although
I notice that it's not mentioned in the list of working group
milestones.)

>    It is believed that the overhead of two bytes is more than
>    compensated by the fact that any link in AO/DI could now be treated
>    as dial-up PPP connection due to the protocol stack layering that
>    resulted; i.e., the same PPP process is used for B-Channels and the
>    X.25 channel.

This seems sensible, but an explicit description of the "overhead" might
be useful to avoid any confusion.

>The Data Link Layer
>
>    From RFC 1598: Since both "PPP in HDLC Framing" [3] and X.25 use
ISO
>    3309 as a basis for framing, the X.25 header is easily substituted
>    for the smaller HDLC header.  The fields are transmitted from left
>    to right.
>
> 0                   1                   2                   3
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
>+-+-+-+-+-+-+-+-+
>|  Flag (0x7e)  |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|    Address    |    Control    |D|Q| SVC# (hi) |   SVC# (lo)   |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|p(r) |M|p(s) |0|         PPP Protocol          |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

This description of the framing is misleading - there are 2 octets in
the address field in Q.922 (as opposed to 1 in X.25 LAPB).  Also (my
memory may be wrong here), but isn't the control field 2 octets as well?
It certainly is for SAPI 0 (as used by Q.931 for ISDN call setup).

In addition, having the PPP Protocol field follow immediately after the
X.25 Packet header seems to contradict the previous paragraph about the
"two byte overhead", which I had assumed to be the PPP frame's address
and control field.

Anyway, I consider this description of the framing (and the one in RFC
1598) less than
useful, especially as it ignores the existence of the X.25 M bit - as
far as the PPP implementor is concerned, there is no need to know about
the X.25 protocol frame and packet headers at all.  A PPP implementor
just needs to know how to encapsulate the PPP packet within an X.25
"complete packet sequence" (as defined by X.25 clause 4.3.5).  I
therefore think it's better to omit the framing diagram entirely.  A
diagram of the PPP encapsulation might be useful, although it ought to
be the same as the one in RFC 1661.

(A problem of RFC 1598 is that it takes no account of the possibility of
modulo 128 sequence numbers, which alter the size of the X.25 headers.
I assume that as far as AO/DI is concerned, modulo 8 is always used by
the X.25 packet layer.)


On a more trivial note, what does the term "PC" mean as used in the
draft? For example, in the following paragrap on page 3:

>    * Inability to contact the subscriber.  This could be due to the PC
>    being turned off, an equipment problem due to hardware or software
>    in the network or the PC, etc.

If it means Personal Computer, I would have thought that a more general
term for the user's terminal would be more appropriate.  Or is AO/DI
aimed only at PC's?


Out of curiosity, why is MP+ listed in the references?  I couldn't find
a reference to it in the text.


There also appear to be a number of typos.

In the following paragraph on page 3, "it's" should be "its".

>    * The success of X.25 networks was due in part to the use of SVCs
>    and the ease of provisioning.  Frame Relay, although successful, is
>    extremely complex to provision because of it's PVC implementation
>    and the same would apply to a managed service provider solution.

On page 7, there seems to be an inconsistent use of the singular and
plural in the following paragraph:

>    This recommendation makes it possible for users to operate AO/DI
>    capable protocol stacks even when the users ISDN network interface
>    card does not support AO/DI, or if the user does not have an AO/DI
>    service due either to lack of facilities at the users ISP and/or at
>    the LEC.

How about:

    This recommendation makes it possible for a user to operate AO/DI
    capable protocol stacks even when the user's ISDN network interface
    card does not support AO/DI, or if the user does not have an AO/DI
    service due either to lack of facilities at the users ISP and/or at
    the LEC.

On page 11, "users" should be "user":

>    * When looking at Web pages, a good activity timer is 5-10 seconds
>    without activity probably means the users is studying the received
>    materials and will be absorbed for several tens of seconds longer.

Page 14, "CVD" should be "CUD":

>    * CVD up to 16 octets in length

Page 15, "through put" should be "throughput"

>    When bandwidth becomes insufficient, AO/DI attempts to augment the
>    bandwidth.  Failure to augment bandwidth results in continuing with
>    a slower-than-desired throughput, but no damage.  If the D-Channel
>    through put becomes unacceptable, an attempt to add a B-Channel
will
>    be made; this could be the result of delays in packet
acknowledgment
>    or even packet rejection at the packet handler.

Jonathan Goodchild
FarSite Communications Ltd
email: jon.goodchild@farsite.co.uk



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 29 12:38:21 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14850
	for <pppext-archive@odin.ietf.org>; Tue, 29 Jun 1999 12:38:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 4246844428; Tue, 29 Jun 1999 12:37:58 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 1B77D4443D; Tue, 29 Jun 1999 12:37:58 -0400 (EDT)
Received: from sand5.global.net.uk (sand5.global.net.uk [194.126.80.249])
	by segue.merit.edu (Postfix) with ESMTP id 4FECD44428
	for <ietf-ppp@merit.edu>; Tue, 29 Jun 1999 12:37:56 -0400 (EDT)
Received: from pb1s03a01.client.global.net.uk ([195.147.131.178] helo=hardy.farsite.co.uk)
	by sand5.global.net.uk with esmtp (Exim 2.05 #1)
	id 10z0tO-0005UR-00
	for ietf-ppp@merit.edu; Tue, 29 Jun 1999 17:37:55 +0100
Received: by HARDY with Internet Mail Service (5.0.1457.3)
	id <N65FCHYS>; Tue, 29 Jun 1999 17:00:42 +0100
Message-ID: <D1E6783C663ED2119F91020701169FDD016771@HARDY>
From: Jonathan Goodchild <jon.goodchild@farsite.co.uk>
To: ietf-ppp@merit.edu
Subject: PPPEXT Working Group Description & Mailing List Information
Date: Tue, 29 Jun 1999 17:00:40 +0100
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain
Sender: owner-ietf-ppp@merit.edu
Precedence: bulk
Errors-To: owner-ietf-ppp-outgoing@merit.edu

> Description of Working Group:
> > -----------------------------
> > Note: A separate list has been set up for L2TP discussions:
> >
> > L2TP Discussions:l2tp@ipsec.org
> > To Subscribe: l2tp-request@ipsec.org
> > Archive: http://www.ipsec.org/email/l2tp/
> 
> I've never quite understood the reason why the LT2P mailing list
> information appears after the "Description of the Working Group" title
> and not before (i.e. after the PPP mailing list information).  Can
> anyone enlighten me?
> Also, does anyone know what's happened to the PPP mailing list archive
> at ftp://merit.edu/pub/ietf-ppp-archive/?
> There don't appear to be any entries after March.
> 
> Jonathan Goodchild



From owner-ietf-ppp-outgoing@merit.edu  Tue Jun 29 14:41:50 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17711
	for <pppext-archive@odin.ietf.org>; Tue, 29 Jun 1999 14:41:50 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id 6A1824441B; Tue, 29 Jun 1999 14:41:18 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id 45E654442A; Tue, 29 Jun 1999 14:41:18 -0400 (EDT)
Received: from intra0.extant.net (intra0.lvp.extant.net [216.28.121.11])
	by segue.merit.edu (Postfix) with ESMTP id C3AA74441B
	for <ietf-ppp@merit.edu>; Tue, 29 Jun 1999 14:41:16 -0400 (EDT)
Received: from bluegill ([216.28.121.202]) by intra0.extant.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA36E1;
          Tue, 29 Jun 1999 14:41:13 -0400
Message-Id: <4.2.0.56.19990629144006.0437a930@mail.extant.net>
X-Sender: kfox@mail.extant.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.56 (Beta)
Date: Tue, 29 Jun 1999 14:41:10 -0400
To: Jonathan Goodchild <jon.goodchild@farsite.co.uk>, ietf-ppp@merit.edu
From: "Karl Fox" <karl@extant.net>
Subject: Re: PPPEXT Working Group Description & Mailing List Information
In-Reply-To: <D1E6783C663ED2119F91020701169FDD016771@HARDY>
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

Hi Jonathan,

I can answer one of your questions.  The working group home pages are 
generated by a script which doesn't support more than one mailing list per 
working group.

Karl

At 05:00 PM 6/29/99 +0100, Jonathan Goodchild wrote:
> > Description of Working Group:
> > > -----------------------------
> > > Note: A separate list has been set up for L2TP discussions:
> > >
> > > L2TP Discussions:l2tp@ipsec.org
> > > To Subscribe: l2tp-request@ipsec.org
> > > Archive: http://www.ipsec.org/email/l2tp/
> > 
> > I've never quite understood the reason why the LT2P mailing list
> > information appears after the "Description of the Working Group" title
> > and not before (i.e. after the PPP mailing list information).  Can
> > anyone enlighten me?
> > Also, does anyone know what's happened to the PPP mailing list archive
> > at ftp://merit.edu/pub/ietf-ppp-archive/?
> > There don't appear to be any entries after March.
> > 
> > Jonathan Goodchild


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



From owner-ietf-ppp-outgoing@merit.edu  Wed Jun 30 08:50:40 1999
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15499
	for <pppext-archive@odin.ietf.org>; Wed, 30 Jun 1999 08:50:40 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
	id DF08A4444C; Wed, 30 Jun 1999 08:50:04 -0400 (EDT)
Delivered-To: ietf-ppp-outgoing@merit.edu
Received: by segue.merit.edu (Postfix, from userid 56)
	id B26B54445C; Wed, 30 Jun 1999 08:50:04 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by segue.merit.edu (Postfix) with ESMTP id D1FF04444C
	for <ietf-ppp@merit.edu>; Wed, 30 Jun 1999 08:50:02 -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 IAA15475;
	Wed, 30 Jun 1999 08:49:58 -0400 (EDT)
Message-Id: <199906301249.IAA15475@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-sdl-pol-00.txt
Date: Wed, 30 Jun 1999 08:49:58 -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 over Simple Data Link (SDL)
                          using raw lightwave channels with ATM-like framing
	Author(s)	: J. Carlson, E. Hernandez-Valencia, N. Jones, 
                          P. Langner
	Filename	: draft-ietf-pppext-sdl-pol-00.txt
	Pages		: 25
	Date		: 29-Jun-99
	
The Point-to-Point Protocol (PPP) in RFC-1661 [1] provides a standard
method for  transporting multi-protocol datagrams over point-to-point
links, and RFCs 1662 [2] and 1619 [3] provide a means to carry PPP
over Synchronous Optical Network (SONET) [5] and Synchronous Digital
Hierarchy (SDH) [6] circuits. PPP over Simple Data Link (SDL) using
SONET/SDH with ATM-like framing (PPPEXT WG work in Progress) extended
these standards to include a new encapsulation for PPP called Simple
Data Link (SDL) [8]. This document extends the use of SDL over raw
lightwave channels  without an intervening SONET/SDH layer, which are
also referred to as 'dark fiber' or Packet-over-Lightwave' (POL)
links

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

ENCODING mime
FILE /internet-drafts/draft-ietf-pppext-sdl-pol-00.txt

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

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

--OtherAccess--

--NextPart--





