From mailman-bounces@ietf.org  Tue Jun  1 07:46:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19891
	for <l2tpext-archive@lists.ietf.org>; Tue, 1 Jun 2004 07:46:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BV5Zq-0005lj-Uk
	for l2tpext-archive@lists.ietf.org; Tue, 01 Jun 2004 05:28:59 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: l2tpext-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.17173.1086080708.28143.mailman@lists.ietf.org>
Date: Tue, 01 Jun 2004 05:05:08 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@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 mailman-admin@ietf.org  Tue Jun  1 11:55:54 2004
Received: from optimus.ietf.org ([132.151.1.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18021
	for <l2tpext-archive@lists.ietf.org>; Tue, 1 Jun 2004 11:55:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BV95h-00004q-51
	for l2tpext-archive@lists.ietf.org; Tue, 01 Jun 2004 09:14:05 -0400
Date: Tue, 01 Jun 2004 09:14:05 -0400
Message-ID: <20040601131405.26555.86088.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-bounces@ietf.org  Fri Jun  4 13:39:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26028
	for <l2tpext-archive@lists.ietf.org>; Fri, 4 Jun 2004 13:39:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BWIXc-0002oQ-Ir; Fri, 04 Jun 2004 13:31:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BWIGw-00080M-Fo
	for l2tpext@megatron.ietf.org; Fri, 04 Jun 2004 13:14:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23933
	for <l2tpext@ietf.org>; Fri, 4 Jun 2004 13:14:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BWIGv-0007N8-Da
	for l2tpext@ietf.org; Fri, 04 Jun 2004 13:14:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BWIG2-00072N-00
	for l2tpext@ietf.org; Fri, 04 Jun 2004 13:13:31 -0400
Received: from linares.terra.com.br ([200.154.55.228])
	by ietf-mx with esmtp (Exim 4.12) id 1BWIFT-0006hD-00
	for l2tpext@ietf.org; Fri, 04 Jun 2004 13:12:56 -0400
Received: from estero.terra.com.br (estero.terra.com.br [200.154.55.138])
	by linares.terra.com.br (Postfix) with ESMTP id 18DBDDDC318
	for <l2tpext@ietf.org>; Fri,  4 Jun 2004 14:12:53 -0300 (BRT)
Received: from odin (200-207-3-223.dsl.telesp.net.br [200.207.3.223])
	(authenticated user jc.vitor)
	by estero.terra.com.br (Postfix) with ESMTP id A09473C09D
	for <l2tpext@ietf.org>; Fri,  4 Jun 2004 14:12:52 -0300 (BRT)
Message-ID: <003801c44a57$3001c8d0$df03cfc8@odin>
From: =?iso-8859-1?Q?Jos=E9_Carlos_Vitorino?= <vitorinojc@terra.com.br>
To: <l2tpext@ietf.org>
Date: Fri, 4 Jun 2004 14:12:59 -0300
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE 
	autolearn=no version=2.60
Subject: [L2tpext] L2TP Specification
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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-Type: multipart/mixed; boundary="===============2042978822=="
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2042978822==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0035_01C44A3E.0A6F4A70"

This is a multi-part message in MIME format.

------=_NextPart_000_0035_01C44A3E.0A6F4A70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I intend to research about Formal Techniques of Specification, utilizing =
the Estelle and Lotos languages. As I have a great interest on L2TP, I =
would like to know, if possible, if you utilized any language of =
specification to develop the L2TP, if positive, what was and where could =
I obtain a copy of the specification documentation. If you didn't =
utilize any specification tools, if you would know the existence of any =
academic production about the specification of the L2TP.
>From ever since I would like to express my certainty on this academic =
partnership for the improvement of the protocol.

Academic Greetings



Jos=E9 Carlos Vitorino

------=_NextPart_000_0035_01C44A3E.0A6F4A70
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT size=3D1>
<DIV>
<DIV><SPAN lang=3DEN-US style=3D"mso-ansi-language: EN-US"><FONT =
face=3DArial><FONT=20
size=3D3>I intend to research about Formal Techniques of Specification, =
utilizing=20
the Estelle and Lotos languages. As I have a great interest on L2TP, I =
would=20
like to know, if possible, if you utilized any language of specification =
to=20
develop the L2TP, if positive, what was and where could I obtain a copy =
of the=20
specification documentation. If you didn=92t utilize any specification =
tools, if=20
you would know the existence of any academic production about the =
specification=20
of the L2TP.<?xml:namespace prefix =3D o ns =3D=20
"urn:schemas-microsoft-com:office:office"=20
/><o:p></o:p></FONT></FONT></SPAN></DIV>
<P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: justify"=20
align=3Djustify><SPAN lang=3DEN-US style=3D"mso-ansi-language: =
EN-US"><FONT=20
face=3DArial><FONT size=3D3>From ever since I would like to express my =
certainty on=20
this academic partnership for the improvement of the=20
protocol.<o:p></o:p></FONT></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: justify"=20
align=3Djustify><SPAN lang=3DEN-US style=3D"mso-ansi-language: =
EN-US"><FONT face=3DArial=20
size=3D3>Academic Greetings</FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: justify"=20
align=3Djustify><SPAN lang=3DEN-US style=3D"mso-ansi-language: =
EN-US"><FONT face=3DArial=20
size=3D3></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: justify"=20
align=3Djustify><SPAN lang=3DEN-US style=3D"mso-ansi-language: =
EN-US"><FONT=20
face=3DArial><FONT size=3D3>Jos=E9 Carlos=20
Vitorino<o:p></o:p></FONT></FONT></SPAN></P></DIV></FONT></FONT></DIV></B=
ODY></HTML>

------=_NextPart_000_0035_01C44A3E.0A6F4A70--




--===============2042978822==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============2042978822==--





From l2tpext-bounces@ietf.org  Wed Jun  9 11:50:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23364
	for <l2tpext-archive@lists.ietf.org>; Wed, 9 Jun 2004 11:50:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BY4wA-0008TA-2k; Wed, 09 Jun 2004 11:24:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BY4dg-0001dy-Uw
	for l2tpext@megatron.ietf.org; Wed, 09 Jun 2004 11:05:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10395
	for <l2tpext@ietf.org>; Wed, 9 Jun 2004 07:53:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BY1e3-00001l-IG
	for l2tpext@ietf.org; Wed, 09 Jun 2004 07:53:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY1d8-00070A-00
	for l2tpext@ietf.org; Wed, 09 Jun 2004 07:52:31 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BY1c7-0005PG-00; Wed, 09 Jun 2004 07:51:27 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 09 Jun 2004 07:55:02 -0400
X-BrightmailFiltered: true
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i59Bosc3021973; 
	Wed, 9 Jun 2004 07:50:55 -0400 (EDT)
Received: from cisco.com (ams-clip-vpn-dhcp4139.cisco.com [10.61.80.42])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id AZV13558;
	Wed, 9 Jun 2004 04:50:53 -0700 (PDT)
Message-ID: <40C6F99C.6080201@cisco.com>
Date: Wed, 09 Jun 2004 13:50:52 +0200
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Andrew G. Malis" <andy.malis@tellabs.com>
References: <6.1.0.6.2.20040520172011.072d2c90@po1.vivacenetworks.com>
	<40C6F74C.5060906@cisco.com>
In-Reply-To: <40C6F74C.5060906@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: "W. Mark Townsley" <townsley@cisco.com>, "PWE3 \(IETF\)" <pwe3@ietf.org>,
        l2tpext@ietf.org
Subject: [L2tpext] Re: [PWE3] WG last call requested for
	draft-ietf-pwe3-fcs-retention-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org
Content-Transfer-Encoding: 7bit


OK, let me try again, I made the same mistake as you did regarding the FCS 
length. Andy, I stole the text describing the FCS Length parameter from you 
directly.

4. Signaling FCS Retention With L2TPv3-based Pseudowires

When using the signaling procedures in [7], the FCS Retention AVP, Attribute 
Type L2TP-TBA-1, is used.

  The Attribute Value field for this AVP has the following format:

     0                   1
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |          FCS Length           |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    The FCS Length is a 2-octet unsigned integer.

The presence of this AVP in an ICRQ or ICRP message indicates that an LCCE (PE) 
requests its peer to retain FCS for the L2TP session being established. If the 
receiving LCCE recognizes the AVP and complies with the FCS retention request, 
it MUST include an FCS Retention AVP as an acknowledgement in a corresponding 
ICRP or ICCN message. FCS Retention is always bidirectional, thus FCS is only 
retained if both LCCEs send an FCS Rentention AVP during session establishment.

The Attribute Value is a 16-bit FCS length field, which indicates the length of 
the original FCS being retained.  For Ethernet and ATM AAL5 pseudowires, this 
length will always be set to 4. For HDLC, PPP, and Frame Relay pseudowires, this 
length will be set to either 2 or 4. Since the FCS length on these interfaces is 
a local setting, retaining the FCS only makes sense if the FCS length is 
identical on both ends of the pseudowire.  Including the FCS length in this AVP 
allows the PEs to ensure that the FCS is only retained when it makes sense.

The Length of this AVP is 8. The M bit for this AVP MUST be set to 0 (zero). 
This AVP MAY be hidden (the H bit MAY be 1 or 0).

For the IANA Considerations Section:

This specification requires one value within the L2TP "Control Message Attribute 
Value Pairs" section to be assigned by IANA as per [8]. The new AVP is encoded 
as L2TP-TBA-1 in this document, and should be referred to in the IANA L2TP 
parameters registry as "FCS Retention."

For the References Section:

  [7]   J. Lau, M. Townsley, I. Goyret, "Layer Two Tunneling
        Protocol (Version 3)", work in progress,
        draft-ietf-l2tpext-l2tp-base-14.txt, June 2004.

  [8]   Townsley, W., "Layer Two Tunneling Protocol (L2TP) Internet
        Assigned Numbers Authority (IANA) Considerations Update",
        RFC 3438, December 2002.

Thanks,

- Mark

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


From l2tpext-bounces@ietf.org  Wed Jun  9 11:51:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23419
	for <l2tpext-archive@lists.ietf.org>; Wed, 9 Jun 2004 11:51:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BY4wA-0008Tf-PF; Wed, 09 Jun 2004 11:24:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BY4dl-0001dy-6k
	for l2tpext@megatron.ietf.org; Wed, 09 Jun 2004 11:05:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10073
	for <l2tpext@ietf.org>; Wed, 9 Jun 2004 07:43:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BY1UK-0007Kr-L4
	for l2tpext@ietf.org; Wed, 09 Jun 2004 07:43:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY1TO-0006WL-00
	for l2tpext@ietf.org; Wed, 09 Jun 2004 07:42:27 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BY1Sa-0005E2-00; Wed, 09 Jun 2004 07:41:36 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 09 Jun 2004 07:45:11 -0400
X-BrightmailFiltered: true
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i59Bf3c3021333; 
	Wed, 9 Jun 2004 07:41:03 -0400 (EDT)
Received: from cisco.com (ams-clip-vpn-dhcp4139.cisco.com [10.61.80.42])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id AZV13216;
	Wed, 9 Jun 2004 04:41:01 -0700 (PDT)
Message-ID: <40C6F74C.5060906@cisco.com>
Date: Wed, 09 Jun 2004 13:41:00 +0200
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Andrew G. Malis" <andy.malis@tellabs.com>
References: <6.1.0.6.2.20040520172011.072d2c90@po1.vivacenetworks.com>
In-Reply-To: <6.1.0.6.2.20040520172011.072d2c90@po1.vivacenetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: "PWE3 \(IETF\)" <pwe3@ietf.org>, l2tpext@ietf.org
Subject: [L2tpext] Re: [PWE3] WG last call requested for
	draft-ietf-pwe3-fcs-retention-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org
Content-Transfer-Encoding: 7bit



Andrew G. Malis wrote:

> The authors feel that this draft is ready to enter WG last call.

Looks like section 4 needs some attention first. It's pretty simple, here is 
some text:

4. Signaling FCS Retention With L2TPv3-based Pseudowires

When using the signaling procedures in [7], the FCS Retention AVP, Attribute 
Type L2TP-TBA-1, is used.

The presence of this AVP in an ICRQ or ICRP message indicates that an LCCE (PE) 
requests its peer to retain FCS for the L2TP session being established. If the 
receiving LCCE recognizes the AVP and complies with the FCS retention request, 
it MUST include an FCS Retention Indicator AVP as an acknowledgement in an ICRP 
or ICCN message. FCS Retention is always bidirectional, thus FCS is only 
retained if both LCCEs send an FCS Rentention AVP during session establishment.

The Length of this AVP is 6 (there is no Attribute Value field). The M bit for 
this AVP MUST be set to 0 (zero). This AVP MAY be hidden (the H bit MAY be 1 or 0).

For the IANA Considerations Section:

This specification requires one value within the L2TP "Control Message Attribute 
Value Pairs" section to be assigned by IANA as per [8]. The new AVP is encoded 
as L2TP-TBA-1 in this document, and should be referred to in the IANA L2TP 
parameters registry as "FCS Retention."

For the References Section:

  [7]   J. Lau, M. Townsley, I. Goyret, "Layer Two Tunneling
        Protocol (Version 3)", work in progress,
        draft-ietf-l2tpext-l2tp-base-14.txt, June 2004.

  [8]   Townsley, W., "Layer Two Tunneling Protocol (L2TP) Internet
        Assigned Numbers Authority (IANA) Considerations Update",
        RFC 3438, December 2002.

Thanks,

- Mark

> 
> Thanks,
> Andy
> 
> ------- Begin of Forwarded Message -------
> To: i-d-announce@ietf.org
> Cc: pwe3@ietf.org
> From: Internet-Drafts@ietf.org
> Subject: I-D ACTION:draft-ietf-pwe3-fcs-retention-01.txt
> Date: Thu, 20 May 2004 16:02:00 -0400
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Pseudo Wire Emulation Edge to Edge 
> Working Group of the IETF.
> 
>     Title        : PWE3 Frame Check Sequence Retention
>     Author(s)    : A. Malis, et al.
>     Filename    : draft-ietf-pwe3-fcs-retention-01.txt
>     Pages        : 6
>     Date        : 2004-5-20
>     
> This document defines a mechanism for preserving frame FCS through
> Ethernet, Frame Relay, and HDLC pseudowires.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retention-01.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of 
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 
> 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-pwe3-fcs-retention-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>     mailserv@ietf.org.
> In the body type:
>     "FILE /internet-drafts/draft-ietf-pwe3-fcs-retention-01.txt".
>     
> NOTE:    The mail server at ietf.org can return the document in
>     MIME-encoded form by using the "mpack" utility.  To use this
>     feature, insert the command "ENCODING mime" before the "FILE"
>     command.  To decode the response(s), you will need "munpack" or
>     a MIME-compliant mail reader.  Different MIME-compliant mail readers
>     exhibit different behavior, especially when dealing with
>     "multipart" MIME messages (i.e. documents which have been split
>     up into multiple messages), so check your local documentation on
>     how to manipulate these messages.
>        
>        
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID:    <2004-5-20152730.I-D@ietf.org>
> 
> ENCODING mime
> FILE /internet-drafts/draft-ietf-pwe3-fcs-retention-01.txt
> 
> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-pwe3-fcs-retention-01.txt>
> 
> ------- End of Forwarded Message -------
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 

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


From l2tpext-bounces@ietf.org  Wed Jun  9 13:39:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02305
	for <l2tpext-archive@lists.ietf.org>; Wed, 9 Jun 2004 13:39:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BY6Z7-0001J5-AU; Wed, 09 Jun 2004 13:08:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BY4dQ-0001dy-RE
	for l2tpext@megatron.ietf.org; Wed, 09 Jun 2004 11:05:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11663
	for <l2tpext@ietf.org>; Wed, 9 Jun 2004 08:26:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BY2AM-0003Oi-AG
	for l2tpext@ietf.org; Wed, 09 Jun 2004 08:26:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BY29S-0002X9-00
	for l2tpext@ietf.org; Wed, 09 Jun 2004 08:25:54 -0400
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BY27k-000121-00; Wed, 09 Jun 2004 08:24:08 -0400
Received: from default.mail.com (unknown[195.115.120.34])
	by comcast.net (sccrmhc13) with SMTP id <200406091223160160098sb0e>
	(Authid: agmalis@comcast.net); Wed, 9 Jun 2004 12:23:22 +0000
Message-Id: <6.1.1.1.2.20040609082137.0324eb08@po1.vivacenetworks.com>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Wed, 09 Jun 2004 08:22:53 -0400
To: "W. Mark Townsley" <townsley@cisco.com>
From: "Andrew G. Malis" <andy.malis@tellabs.com>
In-Reply-To: <40C6F99C.6080201@cisco.com>
References: <6.1.0.6.2.20040520172011.072d2c90@po1.vivacenetworks.com>
	<40C6F74C.5060906@cisco.com> <40C6F99C.6080201@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
X-Mailman-Approved-At: Wed, 09 Jun 2004 13:07:52 -0400
Cc: "Andrew G. Malis" <andy.malis@tellabs.com>,
        "W. Mark Townsley" <townsley@cisco.com>,
        "PWE3 \(IETF\)" <pwe3@ietf.org>, l2tpext@ietf.org
Subject: [L2tpext] Re: [PWE3] WG last call requested for
 draft-ietf-pwe3-fcs-retention-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org

Mark,

Thanks!  We'll consider this a last call comment :-) and edit it in 
following the close of last call (which I believe was this past Monday, 
actually).

Cheers,
Andy

---------

At 6/9/2004 01:50 PM +0200, W. Mark Townsley wrote:

>OK, let me try again, I made the same mistake as you did regarding the FCS 
>length. Andy, I stole the text describing the FCS Length parameter from 
>you directly.
>
>4. Signaling FCS Retention With L2TPv3-based Pseudowires
>
>When using the signaling procedures in [7], the FCS Retention AVP, 
>Attribute Type L2TP-TBA-1, is used.
>
>  The Attribute Value field for this AVP has the following format:
>
>     0                   1
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |          FCS Length           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>    The FCS Length is a 2-octet unsigned integer.
>
>The presence of this AVP in an ICRQ or ICRP message indicates that an LCCE 
>(PE) requests its peer to retain FCS for the L2TP session being 
>established. If the receiving LCCE recognizes the AVP and complies with 
>the FCS retention request, it MUST include an FCS Retention AVP as an 
>acknowledgement in a corresponding ICRP or ICCN message. FCS Retention is 
>always bidirectional, thus FCS is only retained if both LCCEs send an FCS 
>Rentention AVP during session establishment.
>
>The Attribute Value is a 16-bit FCS length field, which indicates the 
>length of the original FCS being retained.  For Ethernet and ATM AAL5 
>pseudowires, this length will always be set to 4. For HDLC, PPP, and Frame 
>Relay pseudowires, this length will be set to either 2 or 4. Since the FCS 
>length on these interfaces is a local setting, retaining the FCS only 
>makes sense if the FCS length is identical on both ends of the 
>pseudowire.  Including the FCS length in this AVP allows the PEs to ensure 
>that the FCS is only retained when it makes sense.
>
>The Length of this AVP is 8. The M bit for this AVP MUST be set to 0 
>(zero). This AVP MAY be hidden (the H bit MAY be 1 or 0).
>
>For the IANA Considerations Section:
>
>This specification requires one value within the L2TP "Control Message 
>Attribute Value Pairs" section to be assigned by IANA as per [8]. The new 
>AVP is encoded as L2TP-TBA-1 in this document, and should be referred to 
>in the IANA L2TP parameters registry as "FCS Retention."
>
>For the References Section:
>
>  [7]   J. Lau, M. Townsley, I. Goyret, "Layer Two Tunneling
>        Protocol (Version 3)", work in progress,
>        draft-ietf-l2tpext-l2tp-base-14.txt, June 2004.
>
>  [8]   Townsley, W., "Layer Two Tunneling Protocol (L2TP) Internet
>        Assigned Numbers Authority (IANA) Considerations Update",
>        RFC 3438, December 2002.
>
>Thanks,
>
>- Mark


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


From l2tpext-bounces@ietf.org  Wed Jun 30 11:06:07 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22766
	for <l2tpext-archive@lists.ietf.org>; Wed, 30 Jun 2004 11:06:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BfgTy-0001tR-Jm; Wed, 30 Jun 2004 10:54:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BfgRe-0001aq-33
	for l2tpext@megatron.ietf.org; Wed, 30 Jun 2004 10:52:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22115
	for <l2tpext@ietf.org>; Wed, 30 Jun 2004 10:52:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BfgRd-0004kx-D5
	for l2tpext@ietf.org; Wed, 30 Jun 2004 10:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BfgQe-0004M1-00
	for l2tpext@ietf.org; Wed, 30 Jun 2004 10:51:17 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx with esmtp (Exim 4.12) id 1BfgPf-0003Vy-00
	for l2tpext@ietf.org; Wed, 30 Jun 2004 10:50:15 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 30 Jun 2004 10:49:45 -0400
X-BrightmailFiltered: true
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com
	[64.102.16.27])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i5UEnh6k010233; 
	Wed, 30 Jun 2004 10:49:43 -0400 (EDT)
Received: from cisco.com (rtp-vpn1-48.cisco.com [10.82.224.48])
	by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id BAH27038;
	Wed, 30 Jun 2004 07:49:42 -0700 (PDT)
Message-ID: <40E2D342.5070604@cisco.com>
Date: Wed, 30 Jun 2004 16:50:42 +0200
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.6) Gecko/20040113
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com
Subject: [L2tpext] IESG review of draft-ietf-l2tpext-l2tp-base
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2tpext>,
	<mailto:l2tpext-request@ietf.org?subject=unsubscribe>
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>
Sender: l2tpext-bounces@ietf.org
Errors-To: l2tpext-bounces@ietf.org
Content-Transfer-Encoding: 7bit


The IESG has been reviewing the base L2TPv3 specification, 
draft-ietf-l2tpext-l2tp-base-xx.txt. The last two updates, versions 13 and 14, 
contain changes based on these discussions. A summary of the changes are 
detailed below. Comments welcome.

Thanks,

- Mark

draft -14 updates:

Updated to not preclude support of L2TP over IPv6. This included normalization 
of any specific references to IPv4 as either simply "IP" or pointing out any 
differences between L2TP over IPv4 vs. L2TP over IPv6. Most significant changes 
required were the Result Code AVP which may include IP addresses within Error 
Message text, and stronger wording that the Router ID AVP was not specifically 
an IPv4 address. The IPv6 discussion triggered an additional thread on IP 
fragmentation resulting in new text in section 4.1.4 on this topic.

Clarification of Session ID and Cookie text in section 4.1.

Additional text regarding use of the UDP Checksum in section 4.1.2.3

The Connect Speed AVPs are now 64 bits, the L2TPv2 32bit AVPs which were being 
carried over unchanged are now deprecated in L2TPv3.

Corrected the following 3 cases of improperly capitalized "MUST NOT":

"The L2TPv3 Cookie MUST NOT be regarded as a substitute for security such as
that of IPsec when operating over an open or untrusted network where
packets may be sniffed, decoded and correlated for use in a coordinated
attack. See section 4.1.3 for more information on running L2TP over IPsec."

"This policy MUST NOT be considered a license to send malformed AVPs,
but rather, a guide towards how to handle an improperly formatted"

"LCCE to the other.  Such protection MUST NOT be considered a substitution
for end-to-end security between communicating hosts or applications."

The Application ID AVP was found to be unnecessary for the base specification, 
and was identified as potentially prone to abuse and associated interoperability 
problems as currently defined. The Application ID text was subsequently removed, 
but may be reintroduced in a separate document. Associated L2TP L2VPN documents 
which use this AVP will need to be updated due to this change, though none of 
the L2TPEXT documents should be affected.

One MUST include a new Random Vector AVP if two hidden AVPs with the same 
attribute number are present in a single message (this is an edge case in 
practical usage of L2TP, but is theoretically a security hole).

Section 5.1 and 7.1, clarifications on reserved bits in the AVP format, and how 
to handle malformed AVPs.

Our Vendor-Specific AVP format includes a 16-bit field for the Vendor-ID. It was 
noted that Enterprise codes beyond 65,535 are possible in the not too distant 
future. An "Extended Vendor ID AVP Format" is defined in section 5.1 just in 
case this happens. Only implementations need Vendor IDs beyond 16 bits (or those 
requiring interoperability with vendor-specific features of implementations with 
vendor IDs beyond 16 bits) need be able to parse or create AVPs with this new 
format.

Considerable update of IANA section to be more clear.

If Control Message Authentication is enabled, two shared secrets may be 
configured and a message may be signed with each to enable a secret to be 
changed gracefully (section 5.4.1).

Moved Acknowledgement section.

New RFC 3667/8 Boilerplate.

Various reference updates.

Reformatting of whitespace in some tables to keep them under 72 columns and 
various other nits.

draft -13 updates:

Various small wording clarifications throughout the document that are not worth 
detailing here.

Fixing of nomenclature used to describe control message hashing and 
clarification of procedure in a number of places. Many thanks to Russ Housley 
for his review of this.

Updated and moved "L2TP and IPsec" section to 4.1.3.


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


