From mailman-admin@ietf.org  Sat Feb  1 09:43:53 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06882
	for <l2tpext-archive@lists.ietf.org>; Sat, 1 Feb 2003 09:43:52 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h11ElsJ26811
	for <l2tpext-archive@lists.ietf.org>; Sat, 1 Feb 2003 09:47:54 -0500
Date: Sat, 01 Feb 2003 09:47:54 -0500
Message-ID: <20030201144754.8821.29680.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: l2tpext-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, l2tpext-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for l2tpext-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
l2tpext@ietf.org                         ruNF      
https://www1.ietf.org/mailman/options/l2tpext/l2tpext-archive%40lists.ietf.org


From l2tpext-admin@ietf.org  Mon Feb  3 05:07:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01851
	for <l2tpext-archive@lists.ietf.org>; Mon, 3 Feb 2003 05:07:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13A9sJ08014;
	Mon, 3 Feb 2003 05:09:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13A8pJ07950
	for <l2tpext@optimus.ietf.org>; Mon, 3 Feb 2003 05:08:51 -0500
Received: from exchange.Ic4ic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA01827;
	Mon, 3 Feb 2003 05:03:23 -0500 (EST)
Received: through eSafe SMTP Relay 1040832187; Mon Feb 03 13:05:02 2003
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2CB6C.059DEC9C"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Mon, 3 Feb 2003 12:07:13 +0200
Message-ID: <88BC9E379956AE4DB689CC5FF6F5A43D47E929@exchange.Ic4ic.com>
Thread-Topic: TCRTP, L2TPHC and L2TPoAAL5
Thread-Index: AcLLbAWHnYONHmggTjCwQPeJiIUPyw==
From: "Daniel Feldman" <daniel@ic4ic.com>
To: "Tmima Koren (E-mail)" <tmima@cisco.com>, <vandys@zendo.com>,
        <dwing@cisco.com>, <brucet@cisco.com>
Cc: <l2tpext@ietf.org>, <avt@ietf.org>
Subject: [L2tpext] TCRTP, L2TPHC and L2TPoAAL5
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2CB6C.059DEC9C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

    Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,
    Section 3.3.2 of the current TCRTP draft has a bandwidth comparison
table, including TCRTP over PPP and TCRTP over AAL5.
    From the text I understand that:
a) TCRTP over PPP includes Header Compression only once, so the IP
header (20 bytes) is not compressed. This could be reduced by using the
COMPRESSED_NON_TCP format described in RFC2507 below the L2TPHC tunnel.
b) TCRTP over AAL5 includes a 20-bytes IP header which could be reduced
to zero, if L2TPHC worked straight over AAL5.
=20
    My questions are:
1) Can we add the scenario described in (a) to the TCRTP draft?
2) Is it possible to extend L2TPHC so it is compatible with L2TPoAAL5
(RFC3355)?
3) Can we add this scenario to the TCRTP draft?
=20
    Thanks in advance and regards,
=20
        Daniel Feldman.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniel Feldman
System Architecture Group Manager, IC4IC Ltd.
office: +972 (4) 959-4644 ext. 121
mobile: +972 (55) 99-0299
fax:    +972 (4) 959-4944
web:      <http://www.ic4ic.com/> http://www.ic4ic.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
=20


------_=_NextPart_001_01C2CB6C.059DEC9C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">


<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>&nbsp;&=
nbsp;&nbsp;=20
Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>Section 3.3.2 of the current TCRTP draft has a bandwidth compari=
son=20
table, including TCRTP over PPP and TCRTP over AAL5.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>From the text I understand that:</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>a) TCRT=
P over PPP=20
includes Header Compression only once, so the IP header (20 bytes) is not=
=20
compressed. This could be reduced by using the COMPRESSED_NON_TCP format=20
described in RFC2507 below the L2TPHC tunnel.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>b) TCRT=
P over AAL5=20
includes a 20-bytes IP header which could be reduced to zero, if L2TPHC w=
orked=20
straight over AAL5.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>My questions are:</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>1) Can =
we add the=20
scenario described in (a) to the TCRTP draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>2) Is i=
t possible to=20
extend L2TPHC so it is compatible with L2TPoAAL5 (RFC3355)?</FONT></SPAN>=
</DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>3) Can =
we add this=20
scenario to the TCRTP draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>Thanks in advance and regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
<FONT face=3DArial size=3D2>Daniel Feldman.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003></SPAN><FONT=20
size=3D2>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>Daniel Feldman<=
BR>System=20
Architecture Group Manager, IC4IC Ltd.<BR>office: +972 (4) 959-4644 ext.=20
121<BR>mobile: +972 (55) 99-0299<BR>fax:&nbsp;&nbsp;&nbsp; +972 (4)=20
959-4944<BR>web:&nbsp;&nbsp;&nbsp;&nbsp; <A href=3D"http://www.ic4ic.com/=
"=20
target=3D_blank><FONT=20
color=3D#800080>http://www.ic4ic.com</FONT></A><BR>~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~=20
</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>


------_=_NextPart_001_01C2CB6C.059DEC9C--
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Mon Feb  3 05:08:43 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01932
	for <l2tpext-archive@odin.ietf.org>; Mon, 3 Feb 2003 05:08:42 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h13ADca08175
	for l2tpext-archive@odin.ietf.org; Mon, 3 Feb 2003 05:13:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13ADcJ08172
	for <l2tpext-web-archive@optimus.ietf.org>; Mon, 3 Feb 2003 05:13:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01870
	for <l2tpext-web-archive@ietf.org>; Mon, 3 Feb 2003 05:08:11 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13A9sJ08014;
	Mon, 3 Feb 2003 05:09:54 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13A8pJ07950
	for <l2tpext@optimus.ietf.org>; Mon, 3 Feb 2003 05:08:51 -0500
Received: from exchange.Ic4ic.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA01827;
	Mon, 3 Feb 2003 05:03:23 -0500 (EST)
Received: through eSafe SMTP Relay 1040832187; Mon Feb 03 13:05:02 2003
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2CB6C.059DEC9C"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Mon, 3 Feb 2003 12:07:13 +0200
Message-ID: <88BC9E379956AE4DB689CC5FF6F5A43D47E929@exchange.Ic4ic.com>
Thread-Topic: TCRTP, L2TPHC and L2TPoAAL5
Thread-Index: AcLLbAWHnYONHmggTjCwQPeJiIUPyw==
From: "Daniel Feldman" <daniel@ic4ic.com>
To: "Tmima Koren (E-mail)" <tmima@cisco.com>, <vandys@zendo.com>,
        <dwing@cisco.com>, <brucet@cisco.com>
Cc: <l2tpext@ietf.org>, <avt@ietf.org>
Subject: [L2tpext] TCRTP, L2TPHC and L2TPoAAL5
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2CB6C.059DEC9C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

    Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,
    Section 3.3.2 of the current TCRTP draft has a bandwidth comparison
table, including TCRTP over PPP and TCRTP over AAL5.
    From the text I understand that:
a) TCRTP over PPP includes Header Compression only once, so the IP
header (20 bytes) is not compressed. This could be reduced by using the
COMPRESSED_NON_TCP format described in RFC2507 below the L2TPHC tunnel.
b) TCRTP over AAL5 includes a 20-bytes IP header which could be reduced
to zero, if L2TPHC worked straight over AAL5.
=20
    My questions are:
1) Can we add the scenario described in (a) to the TCRTP draft?
2) Is it possible to extend L2TPHC so it is compatible with L2TPoAAL5
(RFC3355)?
3) Can we add this scenario to the TCRTP draft?
=20
    Thanks in advance and regards,
=20
        Daniel Feldman.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniel Feldman
System Architecture Group Manager, IC4IC Ltd.
office: +972 (4) 959-4644 ext. 121
mobile: +972 (55) 99-0299
fax:    +972 (4) 959-4944
web:      <http://www.ic4ic.com/> http://www.ic4ic.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
=20


------_=_NextPart_001_01C2CB6C.059DEC9C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-885=
9-1">


<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>&nbsp;&=
nbsp;&nbsp;=20
Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>Section 3.3.2 of the current TCRTP draft has a bandwidth compari=
son=20
table, including TCRTP over PPP and TCRTP over AAL5.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>From the text I understand that:</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>a) TCRT=
P over PPP=20
includes Header Compression only once, so the IP header (20 bytes) is not=
=20
compressed. This could be reduced by using the COMPRESSED_NON_TCP format=20
described in RFC2507 below the L2TPHC tunnel.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>b) TCRT=
P over AAL5=20
includes a 20-bytes IP header which could be reduced to zero, if L2TPHC w=
orked=20
straight over AAL5.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>My questions are:</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>1) Can =
we add the=20
scenario described in (a) to the TCRTP draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>2) Is i=
t possible to=20
extend L2TPHC so it is compatible with L2TPoAAL5 (RFC3355)?</FONT></SPAN>=
</DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial size=3D2>3) Can =
we add this=20
scenario to the TCRTP draft?</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp; <FONT face=3DAri=
al=20
size=3D2>Thanks in advance and regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D433324809-03022003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
<FONT face=3DArial size=3D2>Daniel Feldman.</FONT></SPAN></DIV>
<DIV><SPAN class=3D433324809-03022003></SPAN><FONT=20
size=3D2>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>Daniel Feldman<=
BR>System=20
Architecture Group Manager, IC4IC Ltd.<BR>office: +972 (4) 959-4644 ext.=20
121<BR>mobile: +972 (55) 99-0299<BR>fax:&nbsp;&nbsp;&nbsp; +972 (4)=20
959-4944<BR>web:&nbsp;&nbsp;&nbsp;&nbsp; <A href=3D"http://www.ic4ic.com/=
"=20
target=3D_blank><FONT=20
color=3D#800080>http://www.ic4ic.com</FONT></A><BR>~~~~~~~~~~~~~~~~~~~~~~=
~~~~~~~~~~~~~~~~~~~~~~~=20
</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>


------_=_NextPart_001_01C2CB6C.059DEC9C--
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Mon Feb  3 09:14:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08129
	for <l2tpext-archive@lists.ietf.org>; Mon, 3 Feb 2003 09:14:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13EGrJ24461;
	Mon, 3 Feb 2003 09:16:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13BnjJ14198
	for <l2tpext@optimus.ietf.org>; Mon, 3 Feb 2003 06:49:45 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03429;
	Mon, 3 Feb 2003 06:44:18 -0500 (EST)
Message-Id: <200302031144.GAA03429@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 03 Feb 2003 06:44:18 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-06.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Layer Two Tunneling Protocol (Version 3)
	Author(s)	: J. Lau, W. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-06.txt
	Pages		: 80
	Date		: 2003-1-31
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the extensions to RFC2661 (L2TPv2)
necessary to provide a basis for tunneling a variety of layer 2 data
link types across a packet switched network (such as an IP network).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-06.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-l2tp-base-06.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-l2tpext-l2tp-base-06.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:	<2003-1-31142945.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-l2tp-base-06.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Mon Feb  3 09:21:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08274
	for <l2tpext-archive@odin.ietf.org>; Mon, 3 Feb 2003 09:21:26 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h13EQQ324974
	for l2tpext-archive@odin.ietf.org; Mon, 3 Feb 2003 09:26:26 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13EQQJ24971
	for <l2tpext-web-archive@optimus.ietf.org>; Mon, 3 Feb 2003 09:26:26 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08268
	for <l2tpext-web-archive@ietf.org>; Mon, 3 Feb 2003 09:20:54 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13EGrJ24461;
	Mon, 3 Feb 2003 09:16:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h13BnjJ14198
	for <l2tpext@optimus.ietf.org>; Mon, 3 Feb 2003 06:49:45 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03429;
	Mon, 3 Feb 2003 06:44:18 -0500 (EST)
Message-Id: <200302031144.GAA03429@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 03 Feb 2003 06:44:18 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-l2tp-base-06.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Layer Two Tunneling Protocol (Version 3)
	Author(s)	: J. Lau, W. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-06.txt
	Pages		: 80
	Date		: 2003-1-31
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the extensions to RFC2661 (L2TPv2)
necessary to provide a basis for tunneling a variety of layer 2 data
link types across a packet switched network (such as an IP network).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tp-base-06.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-l2tp-base-06.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-l2tpext-l2tp-base-06.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:	<2003-1-31142945.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-l2tp-base-06.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Tue Feb  4 15:32:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03519
	for <l2tpext-archive@lists.ietf.org>; Tue, 4 Feb 2003 15:32:17 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14KWaJ21147;
	Tue, 4 Feb 2003 15:32:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14KUcJ21048
	for <l2tpext@optimus.ietf.org>; Tue, 4 Feb 2003 15:30:38 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03366;
	Tue, 4 Feb 2003 15:24:29 -0500 (EST)
Received: from tmima-w2k.cisco.com ([171.71.129.25])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h14KRvB7001040;
	Tue, 4 Feb 2003 12:27:57 -0800 (PST)
Message-Id: <4.3.2.7.2.20030204095404.02329608@mira-sjcm-2.cisco.com>
X-Sender: tmima@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 04 Feb 2003 10:36:51 -0800
To: "Daniel Feldman" <daniel@ic4ic.com>,
        "Tmima Koren (E-mail)" <tmima@cisco.com>, <vandys@zendo.com>,
        <dwing@cisco.com>, <brucet@cisco.com>
From: Tmima Koren <tmima@cisco.com>
Cc: <l2tpext@ietf.org>, <avt@ietf.org>
In-Reply-To: <88BC9E379956AE4DB689CC5FF6F5A43D47E929@exchange.Ic4ic.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_54060374==_.ALT"
Subject: [L2tpext] Re: TCRTP, L2TPHC and L2TPoAAL5
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--=====================_54060374==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 12:07 PM 2/3/2003 +0200, Daniel Feldman wrote:
>     Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,
>     Section 3.3.2 of the current TCRTP draft has a bandwidth comparison 
> table, including TCRTP over PPP and TCRTP over AAL5.
>     From the text I understand that:
>a) TCRTP over PPP includes Header Compression only once, so the IP header 
>(20 bytes) is not compressed. This could be reduced by using the 
>COMPRESSED_NON_TCP format described in RFC2507 below the L2TPHC tunnel.

The L2TP packet traverses multiple links between source and destination
If some individual links on the path are point to point, it is possible to 
compress the L2TP IP header using IPHC
But it's not like you can do IPHC at the source and have the packet go 
compressed all the way to the destination
Once the packet is an L2TP packet it is a regular IP packet and it can be 
compressed on individual links like any other IP packet
So I'm not sure we need to add this to the TCRTP draft
Regards
Tmima

>b) TCRTP over AAL5 includes a 20-bytes IP header which could be reduced to 
>zero, if L2TPHC worked straight over AAL5.
>
>     My questions are:
>1) Can we add the scenario described in (a) to the TCRTP draft?
>2) Is it possible to extend L2TPHC so it is compatible with L2TPoAAL5 
>(RFC3355)?
>3) Can we add this scenario to the TCRTP draft?
>
>     Thanks in advance and regards,
>
>         Daniel Feldman.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Daniel Feldman
>System Architecture Group Manager, IC4IC Ltd.
>office: +972 (4) 959-4644 ext. 121
>mobile: +972 (55) 99-0299
>fax:    +972 (4) 959-4944
>web:     <http://www.ic4ic.com/>http://www.ic4ic.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>

--=====================_54060374==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 12:07 PM 2/3/2003 +0200, Daniel Feldman wrote:<br>
<blockquote type=cite cite><font face="arial" size=2>&nbsp;&nbsp;&nbsp;
Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,</font><br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>Section 3.3.2 of the current
TCRTP draft has a bandwidth comparison table, including TCRTP over PPP
and TCRTP over AAL5.</font><br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>From the text I understand
that:</font><br>
<font face="arial" size=2>a) TCRTP over PPP includes Header Compression
only once, so the IP header (20 bytes) is not compressed. This could be
reduced by using the COMPRESSED_NON_TCP format described in RFC2507 below
the L2TPHC tunnel.</font></blockquote><br>
The L2TP packet traverses multiple links between source and
destination<br>
If some individual links on the path are point to point, it is possible
to compress the L2TP IP header using IPHC<br>
But it's not like you can do IPHC at the source and have the packet go
compressed all the way to the destination<br>
Once the packet is an L2TP packet it is a regular IP packet and it can be
compressed on individual links like any other IP packet<br>
So I'm not sure we need to add this to the TCRTP draft<br>
Regards<br>
Tmima<br>
<br>
<blockquote type=cite cite><font face="arial" size=2>b) TCRTP over AAL5
includes a 20-bytes IP header which could be reduced to zero, if L2TPHC
worked straight over AAL5.</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>My questions
are:</font><br>
<font face="arial" size=2>1) Can we add the scenario described in (a) to
the TCRTP draft?</font><br>
<font face="arial" size=2>2) Is it possible to extend L2TPHC so it is
compatible with L2TPoAAL5 (RFC3355)?</font><br>
<font face="arial" size=2>3) Can we add this scenario to the TCRTP
draft?</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>Thanks in advance and
regards,</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<font face="arial" size=2>Daniel Feldman.</font><br>
<font size=2>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Daniel Feldman<br>
System Architecture Group Manager, IC4IC Ltd.<br>
office: +972 (4) 959-4644 ext. 121<br>
mobile: +972 (55) 99-0299<br>
fax:&nbsp;&nbsp;&nbsp; +972 (4) 959-4944<br>
web:&nbsp;&nbsp;&nbsp;&nbsp;
</font><a href="http://www.ic4ic.com/"><font size=2 color="#800080">http://www.ic4ic.com</a></font><font size=2><br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ </font><br>
&nbsp;</blockquote></html>

--=====================_54060374==_.ALT--

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Tue Feb  4 15:33:16 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03555
	for <l2tpext-archive@odin.ietf.org>; Tue, 4 Feb 2003 15:33:16 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h14Kcrx22022
	for l2tpext-archive@odin.ietf.org; Tue, 4 Feb 2003 15:38:53 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14KcrJ22019
	for <l2tpext-web-archive@optimus.ietf.org>; Tue, 4 Feb 2003 15:38:53 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03548
	for <l2tpext-web-archive@ietf.org>; Tue, 4 Feb 2003 15:32:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14KWaJ21147;
	Tue, 4 Feb 2003 15:32:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h14KUcJ21048
	for <l2tpext@optimus.ietf.org>; Tue, 4 Feb 2003 15:30:38 -0500
Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03366;
	Tue, 4 Feb 2003 15:24:29 -0500 (EST)
Received: from tmima-w2k.cisco.com ([171.71.129.25])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h14KRvB7001040;
	Tue, 4 Feb 2003 12:27:57 -0800 (PST)
Message-Id: <4.3.2.7.2.20030204095404.02329608@mira-sjcm-2.cisco.com>
X-Sender: tmima@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 04 Feb 2003 10:36:51 -0800
To: "Daniel Feldman" <daniel@ic4ic.com>,
        "Tmima Koren (E-mail)" <tmima@cisco.com>, <vandys@zendo.com>,
        <dwing@cisco.com>, <brucet@cisco.com>
From: Tmima Koren <tmima@cisco.com>
Cc: <l2tpext@ietf.org>, <avt@ietf.org>
In-Reply-To: <88BC9E379956AE4DB689CC5FF6F5A43D47E929@exchange.Ic4ic.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_54060374==_.ALT"
Subject: [L2tpext] Re: TCRTP, L2TPHC and L2TPoAAL5
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--=====================_54060374==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 12:07 PM 2/3/2003 +0200, Daniel Feldman wrote:
>     Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,
>     Section 3.3.2 of the current TCRTP draft has a bandwidth comparison 
> table, including TCRTP over PPP and TCRTP over AAL5.
>     From the text I understand that:
>a) TCRTP over PPP includes Header Compression only once, so the IP header 
>(20 bytes) is not compressed. This could be reduced by using the 
>COMPRESSED_NON_TCP format described in RFC2507 below the L2TPHC tunnel.

The L2TP packet traverses multiple links between source and destination
If some individual links on the path are point to point, it is possible to 
compress the L2TP IP header using IPHC
But it's not like you can do IPHC at the source and have the packet go 
compressed all the way to the destination
Once the packet is an L2TP packet it is a regular IP packet and it can be 
compressed on individual links like any other IP packet
So I'm not sure we need to add this to the TCRTP draft
Regards
Tmima

>b) TCRTP over AAL5 includes a 20-bytes IP header which could be reduced to 
>zero, if L2TPHC worked straight over AAL5.
>
>     My questions are:
>1) Can we add the scenario described in (a) to the TCRTP draft?
>2) Is it possible to extend L2TPHC so it is compatible with L2TPoAAL5 
>(RFC3355)?
>3) Can we add this scenario to the TCRTP draft?
>
>     Thanks in advance and regards,
>
>         Daniel Feldman.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Daniel Feldman
>System Architecture Group Manager, IC4IC Ltd.
>office: +972 (4) 959-4644 ext. 121
>mobile: +972 (55) 99-0299
>fax:    +972 (4) 959-4944
>web:     <http://www.ic4ic.com/>http://www.ic4ic.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>

--=====================_54060374==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 12:07 PM 2/3/2003 +0200, Daniel Feldman wrote:<br>
<blockquote type=cite cite><font face="arial" size=2>&nbsp;&nbsp;&nbsp;
Hello Tmima, Mr. Valencia, Mr. Wing and Mr. Thompson,</font><br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>Section 3.3.2 of the current
TCRTP draft has a bandwidth comparison table, including TCRTP over PPP
and TCRTP over AAL5.</font><br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>From the text I understand
that:</font><br>
<font face="arial" size=2>a) TCRTP over PPP includes Header Compression
only once, so the IP header (20 bytes) is not compressed. This could be
reduced by using the COMPRESSED_NON_TCP format described in RFC2507 below
the L2TPHC tunnel.</font></blockquote><br>
The L2TP packet traverses multiple links between source and
destination<br>
If some individual links on the path are point to point, it is possible
to compress the L2TP IP header using IPHC<br>
But it's not like you can do IPHC at the source and have the packet go
compressed all the way to the destination<br>
Once the packet is an L2TP packet it is a regular IP packet and it can be
compressed on individual links like any other IP packet<br>
So I'm not sure we need to add this to the TCRTP draft<br>
Regards<br>
Tmima<br>
<br>
<blockquote type=cite cite><font face="arial" size=2>b) TCRTP over AAL5
includes a 20-bytes IP header which could be reduced to zero, if L2TPHC
worked straight over AAL5.</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>My questions
are:</font><br>
<font face="arial" size=2>1) Can we add the scenario described in (a) to
the TCRTP draft?</font><br>
<font face="arial" size=2>2) Is it possible to extend L2TPHC so it is
compatible with L2TPoAAL5 (RFC3355)?</font><br>
<font face="arial" size=2>3) Can we add this scenario to the TCRTP
draft?</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp; <font face="arial" size=2>Thanks in advance and
regards,</font><br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<font face="arial" size=2>Daniel Feldman.</font><br>
<font size=2>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
Daniel Feldman<br>
System Architecture Group Manager, IC4IC Ltd.<br>
office: +972 (4) 959-4644 ext. 121<br>
mobile: +972 (55) 99-0299<br>
fax:&nbsp;&nbsp;&nbsp; +972 (4) 959-4944<br>
web:&nbsp;&nbsp;&nbsp;&nbsp;
</font><a href="http://www.ic4ic.com/"><font size=2 color="#800080">http://www.ic4ic.com</a></font><font size=2><br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ </font><br>
&nbsp;</blockquote></html>

--=====================_54060374==_.ALT--

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Wed Feb  5 10:05:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27547
	for <l2tpext-archive@lists.ietf.org>; Wed, 5 Feb 2003 10:05:24 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15FAWJ31299;
	Wed, 5 Feb 2003 10:10:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15Bp6J17753
	for <l2tpext@optimus.ietf.org>; Wed, 5 Feb 2003 06:51:06 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19047;
	Wed, 5 Feb 2003 06:44:39 -0500 (EST)
Message-Id: <200302051144.GAA19047@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 05 Feb 2003 06:44:38 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-v92-moh-04.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Signalling of Modem-On-Hold status in Layer 2 
                          Tunneling Protocol (L2TP)
	Author(s)	: I. Goyret
	Filename	: draft-ietf-l2tpext-v92-moh-04.txt
	Pages		: 13
	Date		: 2003-2-4
	
The Layer 2 Tunneling Protocol (L2TP) defines a mechanism for
tunneling Point-to-Point Protocol (PPP) sessions. It is common for
these PPP sessions to be established using modems connected over the
public switched telephone network.
One of the standards governing modem operation defines procedures
that enable a client modem to put the call on hold and later, re-
establish the modem link with minimal delay and without having to
redial.  While the modem call is on hold, the client phone line can
be used to place or receive other calls.
The L2TP base protocol does not provide any means to signal these
events from the L2TP Access Controller (LAC), where the modem is
physically connected, to the L2TP Network Server (LNS), where the PPP
session is handled.
This document describes a method to let the LNS know when a client
modem connected to a LAC has placed the call on hold.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-v92-moh-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-l2tpext-v92-moh-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:	<2003-2-4134031.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-v92-moh-04.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Wed Feb  5 10:06:17 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27583
	for <l2tpext-archive@odin.ietf.org>; Wed, 5 Feb 2003 10:06:17 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h15FCGX31399
	for l2tpext-archive@odin.ietf.org; Wed, 5 Feb 2003 10:12:16 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15FCGJ31396
	for <l2tpext-web-archive@optimus.ietf.org>; Wed, 5 Feb 2003 10:12:16 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27576
	for <l2tpext-web-archive@ietf.org>; Wed, 5 Feb 2003 10:05:46 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15FAWJ31299;
	Wed, 5 Feb 2003 10:10:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h15Bp6J17753
	for <l2tpext@optimus.ietf.org>; Wed, 5 Feb 2003 06:51:06 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19047;
	Wed, 5 Feb 2003 06:44:39 -0500 (EST)
Message-Id: <200302051144.GAA19047@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 05 Feb 2003 06:44:38 -0500
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-v92-moh-04.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: Signalling of Modem-On-Hold status in Layer 2 
                          Tunneling Protocol (L2TP)
	Author(s)	: I. Goyret
	Filename	: draft-ietf-l2tpext-v92-moh-04.txt
	Pages		: 13
	Date		: 2003-2-4
	
The Layer 2 Tunneling Protocol (L2TP) defines a mechanism for
tunneling Point-to-Point Protocol (PPP) sessions. It is common for
these PPP sessions to be established using modems connected over the
public switched telephone network.
One of the standards governing modem operation defines procedures
that enable a client modem to put the call on hold and later, re-
establish the modem link with minimal delay and without having to
redial.  While the modem call is on hold, the client phone line can
be used to place or receive other calls.
The L2TP base protocol does not provide any means to signal these
events from the L2TP Access Controller (LAC), where the modem is
physically connected, to the L2TP Network Server (LNS), where the PPP
session is handled.
This document describes a method to let the LNS know when a client
modem connected to a LAC has placed the call on hold.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-v92-moh-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-l2tpext-v92-moh-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:	<2003-2-4134031.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-v92-moh-04.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Thu Feb  6 10:45:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22964
	for <l2tpext-archive@lists.ietf.org>; Thu, 6 Feb 2003 10:45:41 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FnZp09358;
	Thu, 6 Feb 2003 10:49:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FlRp09185
	for <l2tpext@optimus.ietf.org>; Thu, 6 Feb 2003 10:47:27 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22694
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 10:40:24 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h16FgRPc003700;
	Thu, 6 Feb 2003 16:42:27 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp53.cisco.com [10.61.64.53])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA24813;
	Thu, 6 Feb 2003 16:44:00 +0100 (MET)
Message-ID: <3E4282BF.1030505@cisco.com>
Date: Thu, 06 Feb 2003 16:43:59 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andreas.Waibel@colt.de
CC: l2tpext@ietf.org
Subject: Re: AW: [L2tpext] result code for disconnect in the case of L2TP
 dial	out
References: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
In-Reply-To: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit



Andreas.Waibel@colt.de wrote:
> Mark,
> 
> thank You for Your response. 
> 
> 
>>>What should we return, if 
>>>- the session is terminated because the L2TP session, which had 
>>>initiated it, was normally terminated by the dialin client?
>>
>>The dialin client may cause the LNS to disconnect by sending 
>>a PPP Terminate 
>>Request, or by "hanging up" the line to the LAC. The latter 
>>is a "loss of 
>>carrier" condition, result code 1, RFC3145 may be consulted 
>>for the former.
> 
> 
> However, in this case there is no dialin client, as it is dialout.
> There is a L2TP client who had initiated the dialout via L2TP. He 
> requests the RAS to disconnect the phone line session by closing 
> the L2TP session. So the carrier was not really lost, but actively 
> disconnected by the RAS as a reaction to a termination request by 
> the L2TP client. There appears to be no code for an intended disconnect 
> from the network side.

Perhaps a picture would be useful here for clarification. The typical dialout 
model is:

LNS --- LAC ---- Remote System

The Remote System is your PPP client, and L2TP is run between the LAC and LNS. 
I'm not sure where the L2TP client you refer to here is... Perhaps the Remote 
System??

In any case, typically the LNS initiates the dialout, and LAC makes the call to 
the Remote System. If the LNS then initiates a disconnect, I suspect most 
implementations still simply use "1 - Call disconnected due to loss of carrier" 
though "3 - Call disconnected for administrative reasons" might be a slightly 
better fit. I agree with you that the disconnect codes are a bit lacking here.

Hope this helps,

- Mark

> 
> 
>>>- or if even the corresponding tunnel was lost (in this 
>>
>>case we cannot
>>
>>>return anything however would like to store a local code 
>>
>>for diagnostics)? 
>>
>>This is subject to interpretation, but perhaps a result code 
>>of 2, pointing to 
>>an error code of of "1 - No control connection exists yet for 
>>this LAC-LNS"
> 
> 
> I aggree. That's probably the best applicable solution.
> 
> best regards
> 
> Andreas
> 
> 
>>-----Ursprüngliche Nachricht-----
>>Von: W. Mark Townsley [mailto:townsley@cisco.com]
>>Gesendet am: Dienstag, 21. Januar 2003 02:58
>>An: Waibel, Andreas
>>Cc: l2tpext@ietf.org
>>Betreff: Re: [L2tpext] result code for disconnect in the case of L2TP
>>dialout
>>
>>
>>
>>Andreas.Waibel@colt.de wrote:
>>
>>>Colleagues,
>>>
>>>we are currently discussing a special L2TP dialout 
>>>implementation with a big RAS vendor. The szenario 
>>>includes dialout connection initated from a L2TP client.
>>>
>>>LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
>>> 
>>>Generally we found RFC 2661 well applicable, however
>>>now we have a problem with the CDN result codes:
>>> 
>>>     Defined Result Code values for the CDN message are:
>>>
>>>         0 - Reserved
>>>         1 - Call disconnected due to loss of carrier
>>>         2 - Call disconnected for the reason indicated
>>>             in error code
>>>         3 - Call disconnected for administrative reasons
>>>         4 - Call failed due to lack of appropriate facilities
>>>             being available (temporary condition)
>>>         5 - Call failed due to lack of appropriate facilities being
>>>             available (permanent condition)
>>>         6 - Invalid destination
>>>         7 - Call failed due to no carrier detected
>>>         8 - Call failed due to detection of a busy signal
>>>         9 - Call failed due to lack of a dial tone
>>>         10 - Call was not established within time allotted by LAC
>>>         11 - Call was connected but no appropriate framing was
>>>              detected
>>>
>>>What should we return, if 
>>>- the session is terminated because the L2TP session, which had 
>>>initiated it, was normally terminated by the dialin client?
>>
>>The dialin client may cause the LNS to disconnect by sending 
>>a PPP Terminate 
>>Request, or by "hanging up" the line to the LAC. The latter 
>>is a "loss of 
>>carrier" condition, result code 1, RFC3145 may be consulted 
>>for the former.
>>
>>
>>>- or if even the corresponding tunnel was lost (in this 
>>
>>case we cannot
>>
>>>return anything however would like to store a local code 
>>
>>for diagnostics)? 
>>
>>This is subject to interpretation, but perhaps a result code 
>>of 2, pointing to 
>>an error code of of "1 - No control connection exists yet for 
>>this LAC-LNS"
>>
>>
>>>thank You for Your advice!
>>>
>>>best regards
>>>
>>>Andreas 
>>>
>>>--------------------
>>>Andreas Waibel
>>>COLT Telecom GmbH
>>>Herriotstraße 4
>>>60528 Frankfurt am Main
>>>Tel.: ++49 69 56606 6570
>>>Fax: ++49 69 56606 6350
>>>email: andreas.waibel@colt.de
>>>
>>>_______________________________________________
>>>L2tpext mailing list
>>>L2tpext@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/l2tpext
>>>
>>
>>
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Thu Feb  6 10:46:32 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23026
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Feb 2003 10:46:32 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h16Fr2U09649
	for l2tpext-archive@odin.ietf.org; Thu, 6 Feb 2003 10:53:02 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Fr2p09646
	for <l2tpext-web-archive@optimus.ietf.org>; Thu, 6 Feb 2003 10:53:02 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23003
	for <l2tpext-web-archive@ietf.org>; Thu, 6 Feb 2003 10:46:00 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FnZp09358;
	Thu, 6 Feb 2003 10:49:36 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16FlRp09185
	for <l2tpext@optimus.ietf.org>; Thu, 6 Feb 2003 10:47:27 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22694
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 10:40:24 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h16FgRPc003700;
	Thu, 6 Feb 2003 16:42:27 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp53.cisco.com [10.61.64.53])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA24813;
	Thu, 6 Feb 2003 16:44:00 +0100 (MET)
Message-ID: <3E4282BF.1030505@cisco.com>
Date: Thu, 06 Feb 2003 16:43:59 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andreas.Waibel@colt.de
CC: l2tpext@ietf.org
Subject: Re: AW: [L2tpext] result code for disconnect in the case of L2TP
 dial	out
References: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
In-Reply-To: <4403667CFF70F84283D8521D50CF4CF3036E2E87@franoa03.de.eu.colt>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit



Andreas.Waibel@colt.de wrote:
> Mark,
> 
> thank You for Your response. 
> 
> 
>>>What should we return, if 
>>>- the session is terminated because the L2TP session, which had 
>>>initiated it, was normally terminated by the dialin client?
>>
>>The dialin client may cause the LNS to disconnect by sending 
>>a PPP Terminate 
>>Request, or by "hanging up" the line to the LAC. The latter 
>>is a "loss of 
>>carrier" condition, result code 1, RFC3145 may be consulted 
>>for the former.
> 
> 
> However, in this case there is no dialin client, as it is dialout.
> There is a L2TP client who had initiated the dialout via L2TP. He 
> requests the RAS to disconnect the phone line session by closing 
> the L2TP session. So the carrier was not really lost, but actively 
> disconnected by the RAS as a reaction to a termination request by 
> the L2TP client. There appears to be no code for an intended disconnect 
> from the network side.

Perhaps a picture would be useful here for clarification. The typical dialout 
model is:

LNS --- LAC ---- Remote System

The Remote System is your PPP client, and L2TP is run between the LAC and LNS. 
I'm not sure where the L2TP client you refer to here is... Perhaps the Remote 
System??

In any case, typically the LNS initiates the dialout, and LAC makes the call to 
the Remote System. If the LNS then initiates a disconnect, I suspect most 
implementations still simply use "1 - Call disconnected due to loss of carrier" 
though "3 - Call disconnected for administrative reasons" might be a slightly 
better fit. I agree with you that the disconnect codes are a bit lacking here.

Hope this helps,

- Mark

> 
> 
>>>- or if even the corresponding tunnel was lost (in this 
>>
>>case we cannot
>>
>>>return anything however would like to store a local code 
>>
>>for diagnostics)? 
>>
>>This is subject to interpretation, but perhaps a result code 
>>of 2, pointing to 
>>an error code of of "1 - No control connection exists yet for 
>>this LAC-LNS"
> 
> 
> I aggree. That's probably the best applicable solution.
> 
> best regards
> 
> Andreas
> 
> 
>>-----Ursprüngliche Nachricht-----
>>Von: W. Mark Townsley [mailto:townsley@cisco.com]
>>Gesendet am: Dienstag, 21. Januar 2003 02:58
>>An: Waibel, Andreas
>>Cc: l2tpext@ietf.org
>>Betreff: Re: [L2tpext] result code for disconnect in the case of L2TP
>>dialout
>>
>>
>>
>>Andreas.Waibel@colt.de wrote:
>>
>>>Colleagues,
>>>
>>>we are currently discussing a special L2TP dialout 
>>>implementation with a big RAS vendor. The szenario 
>>>includes dialout connection initated from a L2TP client.
>>>
>>>LT2P client --- l2TP tunnel switch --- dialout LAC ---> target 
>>> 
>>>Generally we found RFC 2661 well applicable, however
>>>now we have a problem with the CDN result codes:
>>> 
>>>     Defined Result Code values for the CDN message are:
>>>
>>>         0 - Reserved
>>>         1 - Call disconnected due to loss of carrier
>>>         2 - Call disconnected for the reason indicated
>>>             in error code
>>>         3 - Call disconnected for administrative reasons
>>>         4 - Call failed due to lack of appropriate facilities
>>>             being available (temporary condition)
>>>         5 - Call failed due to lack of appropriate facilities being
>>>             available (permanent condition)
>>>         6 - Invalid destination
>>>         7 - Call failed due to no carrier detected
>>>         8 - Call failed due to detection of a busy signal
>>>         9 - Call failed due to lack of a dial tone
>>>         10 - Call was not established within time allotted by LAC
>>>         11 - Call was connected but no appropriate framing was
>>>              detected
>>>
>>>What should we return, if 
>>>- the session is terminated because the L2TP session, which had 
>>>initiated it, was normally terminated by the dialin client?
>>
>>The dialin client may cause the LNS to disconnect by sending 
>>a PPP Terminate 
>>Request, or by "hanging up" the line to the LAC. The latter 
>>is a "loss of 
>>carrier" condition, result code 1, RFC3145 may be consulted 
>>for the former.
>>
>>
>>>- or if even the corresponding tunnel was lost (in this 
>>
>>case we cannot
>>
>>>return anything however would like to store a local code 
>>
>>for diagnostics)? 
>>
>>This is subject to interpretation, but perhaps a result code 
>>of 2, pointing to 
>>an error code of of "1 - No control connection exists yet for 
>>this LAC-LNS"
>>
>>
>>>thank You for Your advice!
>>>
>>>best regards
>>>
>>>Andreas 
>>>
>>>--------------------
>>>Andreas Waibel
>>>COLT Telecom GmbH
>>>Herriotstraße 4
>>>60528 Frankfurt am Main
>>>Tel.: ++49 69 56606 6570
>>>Fax: ++49 69 56606 6350
>>>email: andreas.waibel@colt.de
>>>
>>>_______________________________________________
>>>L2tpext mailing list
>>>L2tpext@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/l2tpext
>>>
>>
>>
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
> 

_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Thu Feb  6 10:50:31 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23222
	for <l2tpext-archive@lists.ietf.org>; Thu, 6 Feb 2003 10:50:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Fu7p09807;
	Thu, 6 Feb 2003 10:56:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Ftpp09780
	for <l2tpext@optimus.ietf.org>; Thu, 6 Feb 2003 10:55:51 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23138
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 10:48:50 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h16ForfU005325
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 16:50:53 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp53.cisco.com [10.61.64.53])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA25319
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 16:52:27 +0100 (MET)
Message-ID: <3E4284BA.4050706@cisco.com>
Date: Thu, 06 Feb 2003 16:52:26 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] No l2tpext meeting in SF?
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Given the lack of contentious debate on the l2tpext list since our last meeting, 
I don't see a strong need to take up an in-person meeting slot at the next IETF 
in San Francisco. The PWE3 WG Chair has agreed to give us some slots for any 
short L2TPv3-related discussion if need be. Let me know if this is a problem for 
anyone.

Thanks,

- Mark



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Thu Feb  6 10:51:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23266
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Feb 2003 10:51:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h16FvoC09938
	for l2tpext-archive@odin.ietf.org; Thu, 6 Feb 2003 10:57:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Fvop09935
	for <l2tpext-web-archive@optimus.ietf.org>; Thu, 6 Feb 2003 10:57:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23246
	for <l2tpext-web-archive@ietf.org>; Thu, 6 Feb 2003 10:50:49 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Fu7p09807;
	Thu, 6 Feb 2003 10:56:07 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h16Ftpp09780
	for <l2tpext@optimus.ietf.org>; Thu, 6 Feb 2003 10:55:51 -0500
Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23138
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 10:48:50 -0500 (EST)
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h16ForfU005325
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 16:50:53 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp53.cisco.com [10.61.64.53])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA25319
	for <l2tpext@ietf.org>; Thu, 6 Feb 2003 16:52:27 +0100 (MET)
Message-ID: <3E4284BA.4050706@cisco.com>
Date: Thu, 06 Feb 2003 16:52:26 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] No l2tpext meeting in SF?
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Given the lack of contentious debate on the l2tpext list since our last meeting, 
I don't see a strong need to take up an in-person meeting slot at the next IETF 
in San Francisco. The PWE3 WG Chair has agreed to give us some slots for any 
short L2TPv3-related discussion if need be. Let me know if this is a problem for 
anyone.

Thanks,

- Mark



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Fri Feb 14 07:37:40 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20541
	for <l2tpext-archive@lists.ietf.org>; Fri, 14 Feb 2003 07:37:40 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ECbHp22560;
	Fri, 14 Feb 2003 07:37:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EBnFp18639
	for <l2tpext@optimus.ietf.org>; Fri, 14 Feb 2003 06:49:15 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17067;
	Fri, 14 Feb 2003 06:45:02 -0500 (EST)
Message-Id: <200302141145.GAA17067@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org, pppoe@ipsec.org, l2tp@l2tp.net
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 14 Feb 2003 06:45:01 -0500
Subject: [L2tpext] I-D ACTION:draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: L2TP Active Discovery Relay for PPPoE
	Author(s)	: W. Townsley, R. da Silva
	Filename	: draft-dasilva-l2tp-relaysvc-05.txt
	Pages		: 16
	Date		: 2003-2-13
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
Layer Two Tunneling Protocol (L2TP) [2], facilitates the tunneling of
PPP packets across an intervening packet-switched network.  And yet a
third protocol, PPP over Ethernet (PPPoE) [3] describes how to build
PPP sessions and to encapsulate PPP packets over Ethernet.
L2TP Active Discovery Relay for PPPoE describes a method to relay
Active Discovery and Service Selection functionality from PPPoE over
the reliable control channel within L2TP.  Two new L2TP control
message types and associated PPPoE-specific Attribute Value Pairs
(AVPs) for L2TP are defined.  This relay mechanism provides enhanced
integration of a specific feature in the PPPoE tunneling protocol
with L2TP.

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

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-dasilva-l2tp-relaysvc-05.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Fri Feb 14 07:38:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20628
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Feb 2003 07:38:41 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1ECgJO23123
	for l2tpext-archive@odin.ietf.org; Fri, 14 Feb 2003 07:42:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ECgIp23120
	for <l2tpext-web-archive@optimus.ietf.org>; Fri, 14 Feb 2003 07:42:18 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20610
	for <l2tpext-web-archive@ietf.org>; Fri, 14 Feb 2003 07:38:10 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1ECbHp22560;
	Fri, 14 Feb 2003 07:37:19 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1EBnFp18639
	for <l2tpext@optimus.ietf.org>; Fri, 14 Feb 2003 06:49:15 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17067;
	Fri, 14 Feb 2003 06:45:02 -0500 (EST)
Message-Id: <200302141145.GAA17067@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: l2tpext@ietf.org, pppoe@ipsec.org, l2tp@l2tp.net
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 14 Feb 2003 06:45:01 -0500
Subject: [L2tpext] I-D ACTION:draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: L2TP Active Discovery Relay for PPPoE
	Author(s)	: W. Townsley, R. da Silva
	Filename	: draft-dasilva-l2tp-relaysvc-05.txt
	Pages		: 16
	Date		: 2003-2-13
	
The Point-to-Point Protocol (PPP) [1] provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
Layer Two Tunneling Protocol (L2TP) [2], facilitates the tunneling of
PPP packets across an intervening packet-switched network.  And yet a
third protocol, PPP over Ethernet (PPPoE) [3] describes how to build
PPP sessions and to encapsulate PPP packets over Ethernet.
L2TP Active Discovery Relay for PPPoE describes a method to relay
Active Discovery and Service Selection functionality from PPPoE over
the reliable control channel within L2TP.  Two new L2TP control
message types and associated PPPoE-specific Attribute Value Pairs
(AVPs) for L2TP are defined.  This relay mechanism provides enhanced
integration of a specific feature in the PPPoE tunneling protocol
with L2TP.

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

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-dasilva-l2tp-relaysvc-05.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Fri Feb 14 21:11:26 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12156
	for <l2tpext-archive@lists.ietf.org>; Fri, 14 Feb 2003 21:11:26 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F2Dkp13391;
	Fri, 14 Feb 2003 21:13:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F2CXp13370
	for <l2tpext@optimus.ietf.org>; Fri, 14 Feb 2003 21:12:33 -0500
Received: from mgw.cosinecom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12140
	for <l2tpext@ietf.org>; Fri, 14 Feb 2003 21:08:07 -0500 (EST)
Received: from imchub1.cosinecom.com (imchub1.cosinecom.com [172.21.8.23])
	by mgw.cosinecom.com (Mirapoint)
	with ESMTP id ACD47367;
	Fri, 14 Feb 2003 18:11:51 -0800 (PST)
Received: by imchub1.cosinecom.com with Internet Mail Service (5.5.2655.55)
	id <C78N0DR6>; Fri, 14 Feb 2003 18:11:52 -0800
Message-ID: <69BCCDDC980B4641BFC908D7BF95F18403D5FA38@exchsrv-eng>
From: Venkatesan Pradeep <Venkatesan.Pradeep@cosinecom.com>
To: "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Date: Fri, 14 Feb 2003 18:11:51 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2D497.9A380CF0"
Subject: [L2tpext] Ns in ZLB ACK
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2D497.9A380CF0
Content-Type: text/plain;
	charset="iso-8859-1"

I was testing an LNS using a Cisco LAC (IOS 12.2(T)) and observed a
problem with the Ns in ZLB ACKs sent by the LAC. The LNS was being
stress tested and we were seeing packet loss on it. The LNS had
advertised a window of 20 and the next expected seq was 10. The LAC
had sent packets with Ns = 10 thru Ns = 29 and 10 more were queued
for transmission. The first packet (Ns = 10) didn't make it to the
LNS. The LNS sent a HELLO packet and the LAC responded with
a ZLB ACK with Ns = 40.

The LNS discarded the ZLB because it was outside its window. It looks
like the LAC increments the sequence number right after queueing the
packets for transmission and is using that for the ZLB.

I think that the LNS was right in rejecting the ZLB. Am I correct?.
If so, what should the Ns in the ZLB be in this scenario?
 Ns = 29: This will make sure that it is within the LNS' window but
          given that a non-ZLB packet with Ns=29 had been transmitted,
          the next packet (ZLB or not) should have Ns=30
 Ns = 30: This will satisfy the Ns increment rule but the packet will
          be outside the LNS' window.

Thanks,

Pradeep.

------_=_NextPart_001_01C2D497.9A380CF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Ns in ZLB ACK</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I was testing an LNS using a Cisco LAC (IOS 12.2(T)) =
and observed a</FONT>
<BR><FONT SIZE=3D2>problem with the Ns in ZLB ACKs sent by the LAC. The =
LNS was being</FONT>
<BR><FONT SIZE=3D2>stress tested and we were seeing packet loss on it. =
The LNS had</FONT>
<BR><FONT SIZE=3D2>advertised a window of 20 and the next expected seq =
was 10. The LAC</FONT>
<BR><FONT SIZE=3D2>had sent packets with Ns =3D 10 thru Ns =3D 29 and =
10 more were queued</FONT>
<BR><FONT SIZE=3D2>for transmission. The first packet (Ns =3D 10) =
didn't make it to the</FONT>
<BR><FONT SIZE=3D2>LNS. The LNS sent a HELLO packet and the LAC =
responded with</FONT>
<BR><FONT SIZE=3D2>a ZLB ACK with Ns =3D 40.</FONT>
</P>

<P><FONT SIZE=3D2>The LNS discarded the ZLB because it was outside its =
window. It looks</FONT>
<BR><FONT SIZE=3D2>like the LAC increments the sequence number right =
after queueing the</FONT>
<BR><FONT SIZE=3D2>packets for transmission and is using that for the =
ZLB.</FONT>
</P>

<P><FONT SIZE=3D2>I think that the LNS was right in rejecting the ZLB. =
Am I correct?.</FONT>
<BR><FONT SIZE=3D2>If so, what should the Ns in the ZLB be in this =
scenario?</FONT>
<BR><FONT SIZE=3D2>&nbsp;Ns =3D 29: This will make sure that it is =
within the LNS' window but</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given =
that a non-ZLB packet with Ns=3D29 had been transmitted,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
next packet (ZLB or not) should have Ns=3D30</FONT>
<BR><FONT SIZE=3D2>&nbsp;Ns =3D 30: This will satisfy the Ns increment =
rule but the packet will</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be =
outside the LNS' window.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Pradeep.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2D497.9A380CF0--
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Fri Feb 14 21:12:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12178
	for <l2tpext-archive@odin.ietf.org>; Fri, 14 Feb 2003 21:12:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1F2GE513446
	for l2tpext-archive@odin.ietf.org; Fri, 14 Feb 2003 21:16:14 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F2GEp13443
	for <l2tpext-web-archive@optimus.ietf.org>; Fri, 14 Feb 2003 21:16:14 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12170
	for <l2tpext-web-archive@ietf.org>; Fri, 14 Feb 2003 21:11:44 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F2Dkp13391;
	Fri, 14 Feb 2003 21:13:46 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1F2CXp13370
	for <l2tpext@optimus.ietf.org>; Fri, 14 Feb 2003 21:12:33 -0500
Received: from mgw.cosinecom.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12140
	for <l2tpext@ietf.org>; Fri, 14 Feb 2003 21:08:07 -0500 (EST)
Received: from imchub1.cosinecom.com (imchub1.cosinecom.com [172.21.8.23])
	by mgw.cosinecom.com (Mirapoint)
	with ESMTP id ACD47367;
	Fri, 14 Feb 2003 18:11:51 -0800 (PST)
Received: by imchub1.cosinecom.com with Internet Mail Service (5.5.2655.55)
	id <C78N0DR6>; Fri, 14 Feb 2003 18:11:52 -0800
Message-ID: <69BCCDDC980B4641BFC908D7BF95F18403D5FA38@exchsrv-eng>
From: Venkatesan Pradeep <Venkatesan.Pradeep@cosinecom.com>
To: "'l2tpext@ietf.org'" <l2tpext@ietf.org>
Date: Fri, 14 Feb 2003 18:11:51 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2655.55)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2D497.9A380CF0"
Subject: [L2tpext] Ns in ZLB ACK
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

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

------_=_NextPart_001_01C2D497.9A380CF0
Content-Type: text/plain;
	charset="iso-8859-1"

I was testing an LNS using a Cisco LAC (IOS 12.2(T)) and observed a
problem with the Ns in ZLB ACKs sent by the LAC. The LNS was being
stress tested and we were seeing packet loss on it. The LNS had
advertised a window of 20 and the next expected seq was 10. The LAC
had sent packets with Ns = 10 thru Ns = 29 and 10 more were queued
for transmission. The first packet (Ns = 10) didn't make it to the
LNS. The LNS sent a HELLO packet and the LAC responded with
a ZLB ACK with Ns = 40.

The LNS discarded the ZLB because it was outside its window. It looks
like the LAC increments the sequence number right after queueing the
packets for transmission and is using that for the ZLB.

I think that the LNS was right in rejecting the ZLB. Am I correct?.
If so, what should the Ns in the ZLB be in this scenario?
 Ns = 29: This will make sure that it is within the LNS' window but
          given that a non-ZLB packet with Ns=29 had been transmitted,
          the next packet (ZLB or not) should have Ns=30
 Ns = 30: This will satisfy the Ns increment rule but the packet will
          be outside the LNS' window.

Thanks,

Pradeep.

------_=_NextPart_001_01C2D497.9A380CF0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Ns in ZLB ACK</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I was testing an LNS using a Cisco LAC (IOS 12.2(T)) =
and observed a</FONT>
<BR><FONT SIZE=3D2>problem with the Ns in ZLB ACKs sent by the LAC. The =
LNS was being</FONT>
<BR><FONT SIZE=3D2>stress tested and we were seeing packet loss on it. =
The LNS had</FONT>
<BR><FONT SIZE=3D2>advertised a window of 20 and the next expected seq =
was 10. The LAC</FONT>
<BR><FONT SIZE=3D2>had sent packets with Ns =3D 10 thru Ns =3D 29 and =
10 more were queued</FONT>
<BR><FONT SIZE=3D2>for transmission. The first packet (Ns =3D 10) =
didn't make it to the</FONT>
<BR><FONT SIZE=3D2>LNS. The LNS sent a HELLO packet and the LAC =
responded with</FONT>
<BR><FONT SIZE=3D2>a ZLB ACK with Ns =3D 40.</FONT>
</P>

<P><FONT SIZE=3D2>The LNS discarded the ZLB because it was outside its =
window. It looks</FONT>
<BR><FONT SIZE=3D2>like the LAC increments the sequence number right =
after queueing the</FONT>
<BR><FONT SIZE=3D2>packets for transmission and is using that for the =
ZLB.</FONT>
</P>

<P><FONT SIZE=3D2>I think that the LNS was right in rejecting the ZLB. =
Am I correct?.</FONT>
<BR><FONT SIZE=3D2>If so, what should the Ns in the ZLB be in this =
scenario?</FONT>
<BR><FONT SIZE=3D2>&nbsp;Ns =3D 29: This will make sure that it is =
within the LNS' window but</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; given =
that a non-ZLB packet with Ns=3D29 had been transmitted,</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
next packet (ZLB or not) should have Ns=3D30</FONT>
<BR><FONT SIZE=3D2>&nbsp;Ns =3D 30: This will satisfy the Ns increment =
rule but the packet will</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be =
outside the LNS' window.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Pradeep.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2D497.9A380CF0--
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Fri Feb 21 12:22:28 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07677
	for <l2tpext-archive@lists.ietf.org>; Fri, 21 Feb 2003 12:22:28 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LHRhp06492;
	Fri, 21 Feb 2003 12:27:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LHQnp06451
	for <l2tpext@optimus.ietf.org>; Fri, 21 Feb 2003 12:26:49 -0500
Received: from e31.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07522
	for <l2tpext@ietf.org>; Fri, 21 Feb 2003 12:19:08 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e31.co.us.ibm.com (8.12.7/8.12.2) with ESMTP id h1LHMwYw060494;
	Fri, 21 Feb 2003 12:22:58 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h1LHMmrs019412;
	Fri, 21 Feb 2003 10:22:48 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.5/8.12.5) with ESMTP id h1LHIt97013041;
	Fri, 21 Feb 2003 12:18:55 -0500
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.5/8.12.5/Submit) with ESMTP id h1LHIpX0013036;
	Fri, 21 Feb 2003 12:18:51 -0500
Message-Id: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
To: ron@aol.net, mark@townsley.net
cc: Erik Guttman <Erik.Guttman@Sun.COM>, l2tpext@ietf.org
Date: Fri, 21 Feb 2003 12:18:51 -0500
From: Thomas Narten <narten@us.ibm.com>
Subject: [L2tpext] FWD: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

Some latish LC comments. BTW, you guys were supposed to check ID nits
per my previous review, but apparently missed the reference split
cited below...

Thomas
------- Forwarded Message

From: Erik Guttman <Erik.Guttman@sun.com>
To: iesg@ietf.org
cc: Erik Guttman <erik.guttman@sun.com>
Date: Fri, 14 Feb 2003 14:01:48 +0100 (CET)
Subject: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Reply-To: Erik Guttman <Erik.Guttman@sun.com>


I realize the last call is over but I looked at this document and have a
few comments.

- normative/informative split needed for references

- what is the content of the <attribute type> transmitted
  in the PPPoE Service Relay Response Capability AVP and
  PPPoE Service Relay Forward Capability AVP?

- what is the recommended speed at which a host should retry
  sending PADRs to establish a session?  When should it give
  up after not getting a PADS?  In general - what happens
  if there are failures and delays?  I believe this could
  cause congestion problems on the network and resource
  consumption issues on the LNS's (who do not know if the 
  PADS has been sucessfully delivered, right?)

  RFC 2516 addresses this for PADI and PADO messages:

  section 8
  When a host does not receive a PADO packet within a specified amount
   of time, it SHOULD resend it's PADI packet and double the waiting
   period. This is repeated as many times as desired.  If the Host is
   waiting to receive a PADS packet, a similar timeout mechanism SHOULD
   be used, with the Host re-sending the PADR.  After a specified number
   of retries, the Host SHOULD then resend a PADI packet.

  but I do not see the equivalent here.

- it looks to me like from RFC 2516 as if the PADO contains
  a human readable string. 

   section 5.2
      The PADO packet MUST contain one AC-Name TAG containing the Access
   Concentrator's name, a Service-Name TAG identical to the one in the
   PADI, and any number of other Service-Name TAGs indicating other
   services that the Access Concentrator offers. 

   section 8
   UTF-8 [5] is used throughout this document instead of ASCII.  UTF-8
   supports the entire ASCII character set while allowing for
   international character sets as well.  See [5] for more details.

   Are service names protocol identifiers or human readable strings?
   If they are protocol ids, where are they documented?  If they are
   human readable, what language are they written in?  I believe a
   language tag must be present in this case.  [RFC 2277, section 4.2]

- as this is a discovery protocol, a full example of what the
  client requests and gets would help.

- how does the receiver of the SRRQ alert the sender if it is invalid?
  Should the receiver throw the request away or send back some form
  of error message?

Best regards,

Erik
   

------- End of Forwarded Message
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Fri Feb 21 12:23:20 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07701
	for <l2tpext-archive@odin.ietf.org>; Fri, 21 Feb 2003 12:23:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1LHUT306658
	for l2tpext-archive@odin.ietf.org; Fri, 21 Feb 2003 12:30:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LHUTp06649
	for <l2tpext-web-archive@optimus.ietf.org>; Fri, 21 Feb 2003 12:30:29 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07693
	for <l2tpext-web-archive@ietf.org>; Fri, 21 Feb 2003 12:22:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LHRhp06492;
	Fri, 21 Feb 2003 12:27:44 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1LHQnp06451
	for <l2tpext@optimus.ietf.org>; Fri, 21 Feb 2003 12:26:49 -0500
Received: from e31.co.us.ibm.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07522
	for <l2tpext@ietf.org>; Fri, 21 Feb 2003 12:19:08 -0500 (EST)
Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24])
	by e31.co.us.ibm.com (8.12.7/8.12.2) with ESMTP id h1LHMwYw060494;
	Fri, 21 Feb 2003 12:22:58 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14])
	by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.5) with ESMTP id h1LHMmrs019412;
	Fri, 21 Feb 2003 10:22:48 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by rotala.raleigh.ibm.com (8.12.5/8.12.5) with ESMTP id h1LHIt97013041;
	Fri, 21 Feb 2003 12:18:55 -0500
Received: from rotala.raleigh.ibm.com (narten@localhost)
	by rotala.raleigh.ibm.com (8.12.5/8.12.5/Submit) with ESMTP id h1LHIpX0013036;
	Fri, 21 Feb 2003 12:18:51 -0500
Message-Id: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
To: ron@aol.net, mark@townsley.net
cc: Erik Guttman <Erik.Guttman@Sun.COM>, l2tpext@ietf.org
Date: Fri, 21 Feb 2003 12:18:51 -0500
From: Thomas Narten <narten@us.ibm.com>
Subject: [L2tpext] FWD: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>

Some latish LC comments. BTW, you guys were supposed to check ID nits
per my previous review, but apparently missed the reference split
cited below...

Thomas
------- Forwarded Message

From: Erik Guttman <Erik.Guttman@sun.com>
To: iesg@ietf.org
cc: Erik Guttman <erik.guttman@sun.com>
Date: Fri, 14 Feb 2003 14:01:48 +0100 (CET)
Subject: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Reply-To: Erik Guttman <Erik.Guttman@sun.com>


I realize the last call is over but I looked at this document and have a
few comments.

- normative/informative split needed for references

- what is the content of the <attribute type> transmitted
  in the PPPoE Service Relay Response Capability AVP and
  PPPoE Service Relay Forward Capability AVP?

- what is the recommended speed at which a host should retry
  sending PADRs to establish a session?  When should it give
  up after not getting a PADS?  In general - what happens
  if there are failures and delays?  I believe this could
  cause congestion problems on the network and resource
  consumption issues on the LNS's (who do not know if the 
  PADS has been sucessfully delivered, right?)

  RFC 2516 addresses this for PADI and PADO messages:

  section 8
  When a host does not receive a PADO packet within a specified amount
   of time, it SHOULD resend it's PADI packet and double the waiting
   period. This is repeated as many times as desired.  If the Host is
   waiting to receive a PADS packet, a similar timeout mechanism SHOULD
   be used, with the Host re-sending the PADR.  After a specified number
   of retries, the Host SHOULD then resend a PADI packet.

  but I do not see the equivalent here.

- it looks to me like from RFC 2516 as if the PADO contains
  a human readable string. 

   section 5.2
      The PADO packet MUST contain one AC-Name TAG containing the Access
   Concentrator's name, a Service-Name TAG identical to the one in the
   PADI, and any number of other Service-Name TAGs indicating other
   services that the Access Concentrator offers. 

   section 8
   UTF-8 [5] is used throughout this document instead of ASCII.  UTF-8
   supports the entire ASCII character set while allowing for
   international character sets as well.  See [5] for more details.

   Are service names protocol identifiers or human readable strings?
   If they are protocol ids, where are they documented?  If they are
   human readable, what language are they written in?  I believe a
   language tag must be present in this case.  [RFC 2277, section 4.2]

- as this is a discovery protocol, a full example of what the
  client requests and gets would help.

- how does the receiver of the SRRQ alert the sender if it is invalid?
  Should the receiver throw the request away or send back some form
  of error message?

Best regards,

Erik
   

------- End of Forwarded Message
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



From l2tpext-admin@ietf.org  Fri Feb 28 10:20:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01252
	for <l2tpext-archive@lists.ietf.org>; Fri, 28 Feb 2003 10:20:36 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFTTp03541;
	Fri, 28 Feb 2003 10:29:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFN5p03189
	for <l2tpext@optimus.ietf.org>; Fri, 28 Feb 2003 10:23:05 -0500
Received: from halt-in.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01064
	for <l2tpext@ietf.org>; Fri, 28 Feb 2003 10:12:03 -0500 (EST)
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 28 Feb 2003 07:16:04 -0800
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1SFEIep025104;
	Fri, 28 Feb 2003 16:14:18 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp272.cisco.com [10.61.65.16])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA05681;
	Fri, 28 Feb 2003 16:15:55 +0100 (MET)
Message-ID: <3E5F7D2A.1090409@cisco.com>
Date: Fri, 28 Feb 2003 16:15:54 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
CC: ron@aol.net, mark@townsley.net, Erik Guttman <Erik.Guttman@Sun.COM>,
        l2tpext@ietf.org
References: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
In-Reply-To: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] Re: FWD: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



Thomas, Erik,

Ron and I looked over these comments. Answers inline.

Thanks!

Thomas Narten wrote:
> Some latish LC comments. BTW, you guys were supposed to check ID nits
> per my previous review, but apparently missed the reference split
> cited below...
> 
> Thomas
> ------- Forwarded Message
> 
> From: Erik Guttman <Erik.Guttman@sun.com>
> To: iesg@ietf.org
> cc: Erik Guttman <erik.guttman@sun.com>
> Date: Fri, 14 Feb 2003 14:01:48 +0100 (CET)
> Subject: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
> Reply-To: Erik Guttman <Erik.Guttman@sun.com>
> 
> 
> I realize the last call is over but I looked at this document and have a
> few comments.
> 
> - normative/informative split needed for references

Sorry, we have identified them and made the changes.

> 
> - what is the content of the <attribute type> transmitted
>   in the PPPoE Service Relay Response Capability AVP and
>   PPPoE Service Relay Forward Capability AVP?

This is an L2TP AVP Attribute, a 16 bit number, to be assigned by IANA.

Please see IANA Considerations, section 6.0.

> 
> - what is the recommended speed at which a host should retry
>   sending PADRs to establish a session?  When should it give
>   up after not getting a PADS?  In general - what happens
>   if there are failures and delays?  I believe this could
>   cause congestion problems on the network and resource
>   consumption issues on the LNS's (who do not know if the 
>   PADS has been sucessfully delivered, right?)
> 
>   RFC 2516 addresses this for PADI and PADO messages:
> 
>   section 8
>   When a host does not receive a PADO packet within a specified amount
>    of time, it SHOULD resend it's PADI packet and double the waiting
>    period. This is repeated as many times as desired.  If the Host is
>    waiting to receive a PADS packet, a similar timeout mechanism SHOULD
>    be used, with the Host re-sending the PADR.  After a specified number
>    of retries, the Host SHOULD then resend a PADI packet.
 >
 >   but I do not see the equivalent here.

All PPPoE PAD control messages are being delivered between the LAC and LNS 
embedded within an L2TP Control Message. As an L2TP Control Message, the 
embedded PAD message will undergo all of the properties of normal L2TP Control 
Message delivery, including retransmission backoff and acknowledgement as 
defined in RFC2661.

> 
> - it looks to me like from RFC 2516 as if the PADO contains
>   a human readable string. 
> 
>    section 5.2
>       The PADO packet MUST contain one AC-Name TAG containing the Access
>    Concentrator's name, a Service-Name TAG identical to the one in the
>    PADI, and any number of other Service-Name TAGs indicating other
>    services that the Access Concentrator offers. 
> 
>    section 8
>    UTF-8 [5] is used throughout this document instead of ASCII.  UTF-8
>    supports the entire ASCII character set while allowing for
>    international character sets as well.  See [5] for more details.
> 
>    Are service names protocol identifiers or human readable strings?
>    If they are protocol ids, where are they documented?  If they are
>    human readable, what language are they written in?  I believe a
>    language tag must be present in this case.  [RFC 2277, section 4.2]

As far as L2TP is concerned, these values are defined by and contain the same 
properties as in the PPPoE specification. L2TP does not interpret the values 
except to differentiate duplicate PPPoE messages (which, technically, would more 
be considered a function of the PPPoE software residing on the LAC or LNS than 
L2TP), and to copy the values, byte-by-byte, into an L2TP control message for 
transporting to a PPPoE Server or Client.

> 
> - as this is a discovery protocol, a full example of what the
>   client requests and gets would help.

PPPoE is a discovery protocol, L2TP is not, nor is PPPoE/L2TP relay. L2TP is 
simply picking up the PPPoE Client messages, transporting them to the designated 
PPPoE server residing on the other side of the L2TP connection, and back.

> 
> - how does the receiver of the SRRQ alert the sender if it is invalid?
>   Should the receiver throw the request away or send back some form
>   of error message?

The SRRQ itself is reliably delivered by the L2TP mechanisms defined in RFC2661 
between the PPPoE Client and Server. There really is no such thing as an 
"invalid" SRRQ, as L2TP is not operating on the contents other than to pass them 
to the PPPoE server for it to respond.

If the embedded PPPoE message itself is invalid, an error message will only be 
returned as a PPPoE message embedded within another L2TP control message and 
forwarded to the client. L2TP will be completely unaware that there was an 
invalid message exchange between the PPPoE endpoints.

If there is something invalid in the L2TP message itself (such as a malformation 
of the contents) there are some general recommendations on how to recover in RFC 
2661, possibly resulting in a teardown of the Control Connection. This is all 
pretty drastic though, and if you are malforming your control messages, well, 
you really don't know what you can and cannot recover from as it depends on what 
part of the message was malformed and whether or not there is robustness for 
receipt of that type of malformation.

> 
> Best regards,

Thanks for your comments, Erik. I hope I have answered your questions 
satisfactorily. Ron is making changes (Clarification of what "Attribute Type" is 
and References split) and we will post the result by the deadline on Monday if 
we don't hear otherwise before.

Thanks,

- Mark & Ron

> 
> Erik
>    
> 
> ------- End of Forwarded Message
> 
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext


From mailnull@www1.ietf.org  Fri Feb 28 10:21:21 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01299
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Feb 2003 10:21:20 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h1SFVpa03674
	for l2tpext-archive@odin.ietf.org; Fri, 28 Feb 2003 10:31:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFVpp03671
	for <l2tpext-web-archive@optimus.ietf.org>; Fri, 28 Feb 2003 10:31:51 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01270
	for <l2tpext-web-archive@ietf.org>; Fri, 28 Feb 2003 10:20:48 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFTTp03541;
	Fri, 28 Feb 2003 10:29:30 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1SFN5p03189
	for <l2tpext@optimus.ietf.org>; Fri, 28 Feb 2003 10:23:05 -0500
Received: from halt-in.cisco.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01064
	for <l2tpext@ietf.org>; Fri, 28 Feb 2003 10:12:03 -0500 (EST)
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 28 Feb 2003 07:16:04 -0800
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1SFEIep025104;
	Fri, 28 Feb 2003 16:14:18 +0100 (MET)
Received: from cisco.com (ams-clip-vpn-dhcp272.cisco.com [10.61.65.16])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA05681;
	Fri, 28 Feb 2003 16:15:55 +0100 (MET)
Message-ID: <3E5F7D2A.1090409@cisco.com>
Date: Fri, 28 Feb 2003 16:15:54 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
CC: ron@aol.net, mark@townsley.net, Erik Guttman <Erik.Guttman@Sun.COM>,
        l2tpext@ietf.org
References: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
In-Reply-To: <200302211718.h1LHIpX0013036@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [L2tpext] Re: FWD: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Thomas, Erik,

Ron and I looked over these comments. Answers inline.

Thanks!

Thomas Narten wrote:
> Some latish LC comments. BTW, you guys were supposed to check ID nits
> per my previous review, but apparently missed the reference split
> cited below...
> 
> Thomas
> ------- Forwarded Message
> 
> From: Erik Guttman <Erik.Guttman@sun.com>
> To: iesg@ietf.org
> cc: Erik Guttman <erik.guttman@sun.com>
> Date: Fri, 14 Feb 2003 14:01:48 +0100 (CET)
> Subject: re: IETF last call on draft-dasilva-l2tp-relaysvc-05.txt
> Reply-To: Erik Guttman <Erik.Guttman@sun.com>
> 
> 
> I realize the last call is over but I looked at this document and have a
> few comments.
> 
> - normative/informative split needed for references

Sorry, we have identified them and made the changes.

> 
> - what is the content of the <attribute type> transmitted
>   in the PPPoE Service Relay Response Capability AVP and
>   PPPoE Service Relay Forward Capability AVP?

This is an L2TP AVP Attribute, a 16 bit number, to be assigned by IANA.

Please see IANA Considerations, section 6.0.

> 
> - what is the recommended speed at which a host should retry
>   sending PADRs to establish a session?  When should it give
>   up after not getting a PADS?  In general - what happens
>   if there are failures and delays?  I believe this could
>   cause congestion problems on the network and resource
>   consumption issues on the LNS's (who do not know if the 
>   PADS has been sucessfully delivered, right?)
> 
>   RFC 2516 addresses this for PADI and PADO messages:
> 
>   section 8
>   When a host does not receive a PADO packet within a specified amount
>    of time, it SHOULD resend it's PADI packet and double the waiting
>    period. This is repeated as many times as desired.  If the Host is
>    waiting to receive a PADS packet, a similar timeout mechanism SHOULD
>    be used, with the Host re-sending the PADR.  After a specified number
>    of retries, the Host SHOULD then resend a PADI packet.
 >
 >   but I do not see the equivalent here.

All PPPoE PAD control messages are being delivered between the LAC and LNS 
embedded within an L2TP Control Message. As an L2TP Control Message, the 
embedded PAD message will undergo all of the properties of normal L2TP Control 
Message delivery, including retransmission backoff and acknowledgement as 
defined in RFC2661.

> 
> - it looks to me like from RFC 2516 as if the PADO contains
>   a human readable string. 
> 
>    section 5.2
>       The PADO packet MUST contain one AC-Name TAG containing the Access
>    Concentrator's name, a Service-Name TAG identical to the one in the
>    PADI, and any number of other Service-Name TAGs indicating other
>    services that the Access Concentrator offers. 
> 
>    section 8
>    UTF-8 [5] is used throughout this document instead of ASCII.  UTF-8
>    supports the entire ASCII character set while allowing for
>    international character sets as well.  See [5] for more details.
> 
>    Are service names protocol identifiers or human readable strings?
>    If they are protocol ids, where are they documented?  If they are
>    human readable, what language are they written in?  I believe a
>    language tag must be present in this case.  [RFC 2277, section 4.2]

As far as L2TP is concerned, these values are defined by and contain the same 
properties as in the PPPoE specification. L2TP does not interpret the values 
except to differentiate duplicate PPPoE messages (which, technically, would more 
be considered a function of the PPPoE software residing on the LAC or LNS than 
L2TP), and to copy the values, byte-by-byte, into an L2TP control message for 
transporting to a PPPoE Server or Client.

> 
> - as this is a discovery protocol, a full example of what the
>   client requests and gets would help.

PPPoE is a discovery protocol, L2TP is not, nor is PPPoE/L2TP relay. L2TP is 
simply picking up the PPPoE Client messages, transporting them to the designated 
PPPoE server residing on the other side of the L2TP connection, and back.

> 
> - how does the receiver of the SRRQ alert the sender if it is invalid?
>   Should the receiver throw the request away or send back some form
>   of error message?

The SRRQ itself is reliably delivered by the L2TP mechanisms defined in RFC2661 
between the PPPoE Client and Server. There really is no such thing as an 
"invalid" SRRQ, as L2TP is not operating on the contents other than to pass them 
to the PPPoE server for it to respond.

If the embedded PPPoE message itself is invalid, an error message will only be 
returned as a PPPoE message embedded within another L2TP control message and 
forwarded to the client. L2TP will be completely unaware that there was an 
invalid message exchange between the PPPoE endpoints.

If there is something invalid in the L2TP message itself (such as a malformation 
of the contents) there are some general recommendations on how to recover in RFC 
2661, possibly resulting in a teardown of the Control Connection. This is all 
pretty drastic though, and if you are malforming your control messages, well, 
you really don't know what you can and cannot recover from as it depends on what 
part of the message was malformed and whether or not there is robustness for 
receipt of that type of malformation.

> 
> Best regards,

Thanks for your comments, Erik. I hope I have answered your questions 
satisfactorily. Ron is making changes (Clarification of what "Attribute Type" is 
and References split) and we will post the result by the deadline on Monday if 
we don't hear otherwise before.

Thanks,

- Mark & Ron

> 
> Erik
>    
> 
> ------- End of Forwarded Message
> 
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext



