headers
Carlos Pignataro | 2 Aug 2007 22:45
X-Face
Picon
Favicon

TDM over L2TPv3

Please find some review comments on draft-ieft-l2tpext-tdm-03

All, please note that there was a typo in the filename of early versions
of this draft, as draft-ieft-l2tpext-tdm. We had this fixed through the
Secretariat, and the current version -03 has been corrected
(s/ieft/ietf/). Please use the second filename/link onwards (the first
one for the rev history):
http://tools.ietf.org/wg/l2tpext/draft-ieft-l2tpext-tdm/
http://tools.ietf.org/wg/l2tpext/draft-ietf-l2tpext-tdm/
                                         ^^

More substantive:
================

2. L2TP Extension
...
   [PWE3-CESoPSN] and [RFC4553] describe how to transfer the End Point
   status via the data plane. This is therefore RECOMMENDED to not use
   the Set-Link-Info (SLI) described in [RFC3931].

Is the recommendation not to use "Set-Link-Info (SLI)" message, or not
to use the "Circuit Status AVP in Set-Link-Info (SLI)"? Please note that
the Circuit Status AVP is a MUST for ICRQ/ICRP in RFC3931, and that
should probably be clarified as well (i.e., what does the Circuit Status
mean in ICRQ/ICRP for TDM PWs). Additionally, the RFC2119 keyword is
"NOT RECOMMENDED" instead of "RECOMMENDED to not"

---

2.1 TDM PW AVP (ICRQ, OCRQ)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sasha Vainshtein | 5 Aug 2007 17:01
Favicon

RE: TDM over L2TPv3


Carlos,
Thank you for a very detailed review.

Please see some tentative answers inline below.

Hopefully they will be helpful.

Sharon,
I would appreciate your feedback as well.

Regards,
                      Sasha
-----Original Message-----
From: Carlos Pignataro [mailto:cpignata <at> cisco.com] 
Sent: Thursday, August 02, 2007 11:45 PM
To: Sasha Vainshtein; Sharon Galtzur
Cc: l2tpext mailing list
Subject: TDM over L2TPv3

Please find some review comments on draft-ieft-l2tpext-tdm-03

All, please note that there was a typo in the filename of early versions
of this draft, as draft-ieft-l2tpext-tdm. We had this fixed through the
Secretariat, and the current version -03 has been corrected
(s/ieft/ietf/). Please use the second filename/link onwards (the first
one for the rev history):
http://tools.ietf.org/wg/l2tpext/draft-ieft-l2tpext-tdm/
http://tools.ietf.org/wg/l2tpext/draft-ietf-l2tpext-tdm/
                                         ^^
(Continue reading)

Permalink | Reply | 1 comment |
headers
Carlos Pignataro | 9 Aug 2007 19:21
X-Face
Picon
Favicon

Re: TDM over L2TPv3

Sasha,

Many thanks for the prompt reply, your answers are helpful. Please see
inline some follow-ups.

On 8/5/2007 11:01 AM, Sasha Vainshtein said the following:
> Carlos,
> Thank you for a very detailed review.
> 
> Please see some tentative answers inline below.
> 
> Hopefully they will be helpful.
> 
> Sharon,
> I would appreciate your feedback as well.
> 
> Regards,
>                       Sasha
> -----Original Message-----
> From: Carlos Pignataro [mailto:cpignata <at> cisco.com] 
> Sent: Thursday, August 02, 2007 11:45 PM
> To: Sasha Vainshtein; Sharon Galtzur
> Cc: l2tpext mailing list
> Subject: TDM over L2TPv3
> 
> Please find some review comments on draft-ieft-l2tpext-tdm-03
> 
> All, please note that there was a typo in the filename of early versions
> of this draft, as draft-ieft-l2tpext-tdm. We had this fixed through the
> Secretariat, and the current version -03 has been corrected
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 17 Aug 2007 19:00
Picon
Favicon

I-D Action:draft-ietf-l2tpext-pwe3-ip-05.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           : Signaling and Encapsulation for the Transport of IP over L2TPv3
	Author(s)       : C. Pignataro, W. Luo
	Filename        : draft-ietf-l2tpext-pwe3-ip-05.txt
	Pages           : 20
	Date            : 2007-08-17

The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a
protocol for tunneling a variety of data link protocols over IP
networks.  This document defines the control messaging, signaling
procedures and encapsulation specifics of how to tunnel IPv4 and IPv6
packets directly over L2TPv3.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-ip-05.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> 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-l2tpext-pwe3-ip-05.txt".

A list of Internet-Drafts directories can be found in
(Continue reading)

Permalink | Reply | 0 comments |
headers
rfc-editor | 21 Aug 2007 02:09
Favicon

RFC 4951 on Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) "failover"


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

        
        RFC 4951

        Title:      Fail Over Extensions for Layer 
                    2 Tunneling Protocol (L2TP) "failover" 
        Author:     V. Jain, Ed.
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    vipinietf <at> yahoo.com
        Pages:      26
        Characters: 53659
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2tpext-failover-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4951.txt

Layer 2 Tunneling Protocol (L2TP) is a connection-oriented protocol
that has a shared state between active endpoints.  Some of this shared
state is vital for operation, but may be volatile in nature,
such as packet sequence numbers used on the L2TP Control
Connection.  When failure of one side of a control connection occurs, a
new control connection is created and associated with the old
connection by exchanging information about the old connection.  Such a
mechanism is not intended as a replacement for an active fail over
with some mirrored connection states, but as an aid for those
parameters that are particularly difficult to have immediately
(Continue reading)

Permalink | Reply | 0 comments |

Gmane