Layer Two Tunneling Protocol Extensions (l2tpext)

Internet-Drafts | 1 Jul 2003 13:22

Picon

I-D ACTION:draft-ietf-l2tpext-l2tp-base-08.txt

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-08.txt
	Pages		: 86
	Date		: 2003-6-30
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the base control protocol and
encapsulation for tunneling multiple layer 2 connections between two
IP connected nodes. Additional documents detail the specifics for
each link-type being emulated.

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

(Continue reading)

Mark Townsley | 14 Jul 2003 16:25

wrong version of draft-ietf-l2tpext-l2tp-base-08.txt posted


Please find a corrected version of draft-ietf-l2tpext-l2tp-base-08.txt
below. An early version was posted in error a few weeks ago. It did
not contain a number of small fixes. 

This version has been submitted to internet-drafts <at> ietf.org as -09, but
will not be available until after the IETF meeting this week.

Apologies for any confusion.

- Mark


Network Working Group                                             J. Lau
Internet-Draft                                               M. Townsley
Category: Standards Track                                  cisco Systems
<draft-ietf-l2tpext-l2tp-base-08.txt>                          I. Goyret
                                                     Lucent Technologies
                                                                 Editors
                                                               June 2003


                Layer Two Tunneling Protocol (Version 3)

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 10 of RFC2026.

   Internet-Drafts are working documents of the Internet Engineering

(Continue reading)

W. Mark Townsley | 14 Jul 2003 16:49

Picon

Agenda for l2tpext meeting, Tuesday, July 15, 57th IETF

1415 - Agenda Bashing

1420 - Sasha Vainshtein, Sasha <at> AXERRA.com
        L2TPv3 Graceful Restart
        draft-galtzur-l2tpext-gr-00.txt

1435 - Mark Townsley townsley <at> cisco.com
        L2TPv3 Update
        draft-l2tpext-l2tp-base-08.txt

1450 - Mark Townsley, townsley <at> cisco.com
        WG draft status

W. Mark Townsley | 15 Jul 2003 05:13

Picon

L2TPv3 draft update details


Thomas and all,

This email updates the last sent to the list with quick responses to the
issues raised by Thomas. It includes his original comments (preceeded by ">"), 
additional comments in response (some posted to the list already, some new) and 
the ultimate action taken for each.

Please note that the draft posted as draft-ietf-l2tpext-l2tp-base-08.txt was 
unfortunately incorrect (due an administrative error on my part). The proper -08 
has been posted to this list and will appear as -09 after the IETF meeting this 
week. Text included below and comments are based on this version.

Thanks,

- Mark

> Running l2tp directly over IP:
>   - no checksum for l2tp fields. This seems a bad idea, especially for
>     the control connection.


Disagree for data connection, but understand that there could be some concern on
the control connection. I think we could and address this via a new AVP which
includes a checksum, CRC or hash of the control packet. Would that suffice?

Action: Extension of existing Tunnel Authentication mechanism to cover hash of
entire control packet. This is the most significant protocol change to this draft.

>   - not clear that IPsec has been specified enough for running l2tp

(Continue reading)

W. Mark Townsley | 16 Jul 2003 16:51

Picon

WG Meeting Summary


The l2tpext meeting in Vienna was fairly short and relatively uneventful. 
Minutes will be sent in a subsequent email.

One new draft was presented, L2TPv3 Graceful Restart, 
draft-galtzur-l2tpext-gr-00.txt. A few comments were made, and the document will 
be updated and resubmitted before the next meeting.

draft-l2tpext-l2tp-base-08.txt contains a number of clarifications and edits 
based on AD review. New version will undergo a new WG last call, and be 
resubmitted to IESG.

We will issue a WG last call for "L2TP Multicast Extension" 
draft-ietf-l2tpext-mcast-03.txt for advancement as an Experimental document.

Other WG milestone targets are:

Aug 03 Submit final Internet-Draft of L2TPv3 Base Specification to IESG
Aug 03 Submit L2TP Header Compression to IESG
        for consideration as a Proposed Standard
Sep 03 Submit Internet-Draft of HDLC over L2TPv3 to IESG
Sep 03 Submit Internet-Draft of Frame Relay over L2TPv3 to IESG
Nov 03 Submit Internet-Draft of Ethernet over L2TPv3 to IESG
Nov 03 Submit Internet-Draft of PPP over L2TPv3 to IESG

Thanks,

- Mark Townsley

W. Mark Townsley | 16 Jul 2003 16:55

Picon

Minutes from l2tpext, IETF 57


IETF-57, Vienna
Tuesday 7/16/03 3:15pm
L2TPEXT minutes

Mark - Agenda bashing

Sasha Vainshtein - Graceful restart update on behalf of authors

Sasha presented draft. Pat Calhoun asked questions about how one might avoid 
session hi-jacking, and if there was forwarding info sent that could be used 
maliciously. Somewhat incorherent discussion ensued, and it was decided to take 
the issue offline.

Mark - Sequence numbers are assumed to be check pointed, not lost??
Sasha - Sessions are terminated on linecards w/circuits, with control
plane on different part of the system. Wanted
psuedo wire traffic to not be impacted by control plane reboots..
Mark - So this draft does not target failover to another line card at all.
Sasha - Right..

Mark - What happens when control plane restart for non-established
sessions?
Sasha - Control connection broken, non-completed sessions need to
be re-established after control returns.

Mark - Hmm for next steps on doc?
no response for or against doc...

Mark - L2TPv3 updates (please see slides)

(Continue reading)

rfc-editor | 18 Jul 2003 01:21

RFC 3573 on Signaling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)


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

        RFC 3573

        Title:      Signalling of Modem-On-Hold status
                    in Layer 2 Tunneling Protocol (L2TP)
        Author(s):  I. Goyret
        Status:     Standards Track
        Date:       July 2003
        Mailbox:    igoyret <at> lucent.com
        Pages:      13
        Characters: 22758
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-l2tpext-v92-moh-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3573.txt

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.

(Continue reading)

Internet-Drafts | 24 Jul 2003 20:32

Picon

I-D ACTION:draft-ietf-l2tpext-l2tp-base-09.txt

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, M. Townsley, I. Goyret
	Filename	: draft-ietf-l2tpext-l2tp-base-09.txt
	Pages		: 87
	Date		: 2003-7-24
	
This document describes 'version 3' of the Layer Two Tunneling
Protocol (L2TPv3). L2TPv3 defines the base control protocol and
encapsulation for tunneling multiple layer 2 connections between two
IP connected nodes. Additional documents detail the specifics for
each link-type being emulated.

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

(Continue reading)

Chris Hellberg | 26 Jul 2003 17:17

Picon

draft-ietf-l2tpext-failover-01 query

Hi,

Does anyone have any code or reports of trials with the mechanism? I've been having a few thoughts on the
passing of state between a LAC and two LNSs. With the failover mechanism, there's a concept of hinting to
the "backup" LNS on the session ID it would prefer to use. 

Would I be correct in thinking that the passing of upper-layer state information (such as IP address for an
IPv4-encapsulated tunnel, DNS, WINS, etc) would need to be handled by upper-layer protocols such as PPP? 

Would this also mean that most PPP implementations would need to cope with suddenly having to start LCP
again in the middle of a session, or does this capability happen with most stacks today anyway?

Cheers,

Chris

------------------------------------------------------------------------------
"This communication, including any attachments, is confidential. 
If you are not the intended recipient, you should not read
it - please contact me immediately, destroy it, and do not
copy or use any part of this communication or disclose
anything about it. Thank you."
------------------------------------------------------------------------------

Vipin Jain | 28 Jul 2003 19:41

Picon

Re: draft-ietf-l2tpext-failover-01 query


my comments inline..

> Does anyone have any code or reports of trials with the mechanism?
There were some (I worked on one) proprietary implementations circling around
the mechanism. The draft has also changed significantly from its first rev.

> I've been having a few thoughts on the passing of state between
> a LAC and two LNSs.
I assume. by 'state' you mean the state of an L2TP session, which is 'Idle',
'Established', 'Wait-Tunnel', 'Wait-Connect', or 'Wait-Reply'. Failover
mechanism described in the mentioned draft doesn't aim at recovering sessions
that were not in 'Established' state. Do you suggest we could preserve the
sessions that were in semi established state and recover them as well to help
the restart process?

> With the failover mechanism, there's a concept
> of hinting to the "backup" LNS on the session ID it would prefer to use.  The
draft today requires that the 'backup' LNS MUST use the same 'session ID'
otherwise the recovery of a session is not possible. Are you suggesting that
the mechanism to switch session ids would give some benefits? IMHO it would be
more messy, specially because failover node's peer would have to switch the
traffic to the new session id then.

> Would I be correct in thinking that the passing of upper-layer state
> information (such as IP address for an IPv4-encapsulated tunnel, DNS, WINS,
> etc) would need to be handled by upper-layer protocols such as PPP? 
If session id remains same, there is no need for PPP renegotiations. The sesion
would simply work as if nothing failed on the other side, except a small hiccup
in the data path.

(Continue reading)

Group

gmane.ietf.l2tpext.

Advertisement

Search Archive

Page

1 | 2

Articles in period: 11

July 2003

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

Emulation of basic ISDN interfaces using TDMPWs (30 Dec 2011)
Set up of TDMPWs after the establishment of a call (13 Dec 2011)
PWs in the NGN network (12 Dec 2011)
Different manipulation of channels in a Nx64 service (12 Dec 2011)
Payload needs to align with a 32-bit boundary (1 Dec 2011)
FR over PWs (20 Nov 2011)
TDMoIP AAL2 and TSSI/RDTD structures (13 Oct 2011)
FRPW: LAPF or Core-LAPF (8 Aug 2011)
[Editorial Errata Reported] RFC3931 (2766) (4 Apr 2011)
L2TPV3 (25 Mar 2011)
Fwd: NomCom 2010-2011: Call for More Nominations (17 Sep 2010)
Pseudo-wires: uni-directional o bi-directional? (18 Jun 2010)
RFC 4349 and RFC 4591: FR negotiation (18 Jun 2010)
RFC 4591 and RFC 4349: DLCI at egress LCCE (16 Jun 2010)
RFC 4591 and RFC 4349: DLCI at egress LCCE (15 Jun 2010)
L2TPext | Interest on Expired Milestones (10 Jun 2010)
RFC 5641 on Layer 2 Tunneling Protocol Version 3 (L2TPv3) Extended Cir (1 Sep 2009)
RFC 5611 on Layer Two Tunneling Protocol version 3 - Setup of Time-Div (19 Aug 2009)
An error in RFC 4446 "IANA Allocations for Pseudowire Edge to Edge Emu (18 Aug 2009)
Protocol Action: 'L2TPv3 Extended Circuit Status Values' to Proposed S (20 Jul 2009)
I-D Action:draft-ietf-l2tpext-circuit-status-extensions-05.txt (13 Jul 2009)

Archives

7	December 2011
1	November 2011
1	October 2011
1	September 2011
2	August 2011
5	April 2011
1	March 2011
1	September 2010
5	July 2010
25	June 2010
1	September 2009
15	August 2009
5	July 2009
5	June 2009
1	May 2009
5	April 2009
7	March 2009
1	February 2009
1	December 2008
4	November 2008
2	October 2008
3	September 2008
10	August 2008
1	July 2008
1	June 2008
3	March 2008
1	February 2008
1	January 2008
1	December 2007
3	November 2007
1	October 2007
5	August 2007
6	July 2007
11	June 2007
1	May 2007
5	March 2007
3	February 2007
2	January 2007
7	December 2006
5	November 2006
5	October 2006
25	September 2006
8	August 2006
4	July 2006
9	June 2006
5	May 2006
4	April 2006
4	March 2006
6	February 2006
6	January 2006
12	December 2005
5	November 2005
10	October 2005
27	September 2005
10	August 2005
12	July 2005
13	June 2005
20	May 2005
9	April 2005
3	March 2005
2	February 2005
1	January 2005
5	December 2004
14	November 2004
9	October 2004
28	September 2004
6	August 2004
5	July 2004
7	June 2004
1	May 2004
1	April 2004
4	March 2004
1	February 2004
11	January 2004
5	December 2003
7	November 2003
11	October 2003
11	September 2003
5	August 2003
11	July 2003
9	June 2003
9	May 2003
10	April 2003
7	March 2003
7	February 2003
9	January 2003
6	December 2002
56	November 2002
5	October 2002
4	September 2002
27	August 2002
33	July 2002
16	June 2002
33	May 2002
17	April 2002
1	February 2001

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template