From l2tpext-bounces@ietf.org Mon Jul 03 07:10:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FxMK0-0000G2-HN; Mon, 03 Jul 2006 07:10:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1FxMJz-0000Fu-Jr
for l2tpext@ietf.org; Mon, 03 Jul 2006 07:10:31 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
helo=chiedprmail1.ietf.org)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxL1U-0001xu-N4
for l2tpext@ietf.org; Mon, 03 Jul 2006 05:47:20 -0400
Received: from p130.piuha.net ([193.234.218.130])
by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FxKmC-0001TX-Cs
for l2tpext@ietf.org; Mon, 03 Jul 2006 05:31:35 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
by p130.piuha.net (Postfix) with ESMTP id 5F01D898BC;
Mon, 3 Jul 2006 12:31:24 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
by p130.piuha.net (Postfix) with ESMTP id 246DE898B8;
Mon, 3 Jul 2006 12:31:24 +0300 (EEST)
Message-ID: <44A8E3E8.2040003@piuha.net>
Date: Mon, 03 Jul 2006 12:31:20 +0300
From: Jari Arkko
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org, rahul@juniper.net, mariados@cisco.com
References:
In-Reply-To:
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: "Romascanu, Dan \(Dan\)"
Subject: [L2tpext] Re: Last Call: 'Transport of Ethernet Frames over L2TPv3'
to Proposed Standard (draft-ietf-l2tpext-pwe3-ethernet)
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
Authors, WG,
Do we have answers / suggested text for Dan's issues below?
If possible, I would like to get an agreed resolution to this
by Wednesday, before the next IESG telechat.
Thanks,
--Jari
Romascanu, Dan (Dan) wrote:
>I have a few questions related to the use of the terms Ethernet and VLAN
>in this I-D:
>
>1. The I-D speaks about 'Ethernet' but does not provide any reference.
>What version of the Ethernet standard is targeted here? The latest
>approved version of the Ethernet standard is IEEE Std 802.3-2005, but
>the IEEE 802.3 WG also has in works an extension of the frame size as
>IEEE 802.3as. One cannot talk about Ethernet PDU and MTU without a
>proper reference.
>2. The I-D speaks about 'Ethernet VLAN'. Strictly speaking there is no
>such thing, Virtual LANs are being defined by IEEE 802.1 and not only
>for Ethernet. However accepting terminology license based on the
>de-facto reality that most if not all VLANs run over Ethernet, there
>still is a need to specify if the document refers to IEEE 802.1Q VLANs
>(one 12-bit tag) or IEEE 802.1ad which accommodate multiple tags and
>introduce the concepts of Customer VLAN and Service VLAN. Maybe the
>VLANs referred in this I-D are transparent to the type of VLANs that are
>being connected, but even so there should be text explaining this.
>
>Dan
>
>
>
>
>
>
>
>
>
>>-----Original Message-----
>>From: The IESG [mailto:iesg-secretary@ietf.org]
>>Sent: Monday, June 12, 2006 6:07 PM
>>To: IETF-Announce
>>Cc: l2tpext@ietf.org
>>Subject: Last Call: 'Transport of Ethernet Frames over
>>L2TPv3' to Proposed Standard (draft-ietf-l2tpext-pwe3-ethernet)
>>
>>The IESG has received a request from the Layer Two Tunneling
>>Protocol Extensions WG to consider the following document:
>>
>>- 'Transport of Ethernet Frames over L2TPv3 '
>> as a Proposed Standard
>>
>>The IESG plans to make a decision in the next few weeks, and
>>solicits final comments on this action. Please send any
>>comments to the iesg@ietf.org or ietf@ietf.org mailing lists
>>by 2006-06-26.
>>
>>The file can be obtained via
>>http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-pwe3-et
>>hernet-07.txt
>>
>>
>>_______________________________________________
>>IETF-Announce mailing list
>>IETF-Announce@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf-announce
>>
>>
>>
>
>
>
>
>
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext
From accounting@0x1b.com Wed Jul 12 03:56:05 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G0ZZl-0000jp-Je; Wed, 12 Jul 2006 03:56:05 -0400
Received: from [125.234.130.80] (helo=mxs.mail.ru)
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1G0ZZj-0005gR-FY; Wed, 12 Jul 2006 03:56:05 -0400
Message-ID: <662161c80604i2mh3p0dadn9ahs077i3ukoocsm3svfa@mx3.daemonmail.net>
Date: Wed, 12 Jul 2006 07:56:04 -0420
From: "Jonah Starnes"
To: l1vpn-bounces@lists.ietf.org
Subject: IDY
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam: Not detected
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
"What were you doing in the Prezone Area?"
while they rested on the beach after a session of folded-wing snap rolls.
Commission on Problems of the Visitation."
from are standing on the ground, squawking and fighting among themselves.
From komatsu@kamposv.kampo2002.net Wed Jul 12 04:42:49 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G0aIz-0004WC-CP
for l2tpext-archive@lists.ietf.org; Wed, 12 Jul 2006 04:42:49 -0400
Received: from [219.163.126.184] (helo=kamposv.kampo2002.net)
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1G0aIw-0000HH-DV
for l2tpext-archive@lists.ietf.org; Wed, 12 Jul 2006 04:42:49 -0400
Received: (from komatsu@localhost)
by kamposv.kampo2002.net (8.11.6p2/8.11.6) id k6C94j828130;
Wed, 12 Jul 2006 18:04:45 +0900
Date: Wed, 12 Jul 2006 18:04:45 +0900
Message-Id: <200607120904.k6C94j828130@kamposv.kampo2002.net>
To: l2tpext-archive@lists.ietf.org
Subject: Message from eBay Member
From: eBay-Mitglied gret
Content-Type: text/html
X-Spam-Score: 3.8 (+++)
X-Scan-Signature: fca7d4b87f391aa4d413f865ce6efe79
eBay sent this message. Your registered name
is included to show this message originated from eBay. Learn
more. | |
|
Question from eBay Member --
Respond Now |
|
|
eBay sent this message on
behalf of an eBay member via My Messages. Responses sent
using email will not reach the eBay member. Use the
Respond Now button below to respond to this
message. | |
| | |
|
|
From acannon@1-800-database.com Wed Jul 19 03:24:30 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G36Q2-0002xw-0A
for l2tpext-archive@lists.ietf.org; Wed, 19 Jul 2006 03:24:30 -0400
Received: from [85.96.13.89] (helo=dsl.dynamic85961389.ttnet.net.tr)
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1G36Pw-0003pG-FK
for l2tpext-archive@lists.ietf.org; Wed, 19 Jul 2006 03:24:29 -0400
Message-ID: <662161c80604yar4n2hggu5oj5fah1vszkriq7g33v4f@mail.global.frontbridge.com>
Date: Wed, 19 Jul 2006 07:24:20 -0120
From: "Geneva Parrish"
To: l2tpext-archive@lists.ietf.org
Subject: Success, well-described
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam: Not detected
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Your cre dit doesn't matter to us! If you OWN real est ate
and want IMMEDIATEM cash to spend ANY way you like, or simply wish
to LOWER your monthly paym ents by a third or more, here are the dea ls
we have TODAY (hurry, these ofers will expre TONIGHT):
$488,000.00 at a 3.67,% fixed-rateR
$372,000.00 at a 3.90,% variable-rateY
$492,000.00 at a 3.21,% interest-only4
$248,000.00 at a 3.36,% fixed-rateT
$198,000.00 at a 3.55,% variable-rate4
Hurry, when these deals are gone, they are gone Simply fill out this one-min ute form...
Don't worry about approval, your cre dit will not disqualify you!
http://8VR6RXT.foorests.net
muscles to the weight of the heavy backpack. He watched Arthur out of the
asking about the cottage--what kind was it, where was it, what did it
Arthur Burbridge's leather jacket. The boy was striding along lightly and
wet, hungry, crazy, with a sack over my shoulder, I burst into the bar and
home."
was immediately blanketed by rust and then twisted and deformed into the
hurry to hide in some faraway corner and watch in fear as his father tore
hill except the intense sunlight, but on the right slope, in the shade, pale
"Well, I guessed! I don't remember exactly what gave me the clue. Well,
he looked like, and what he did, Redrick could not remember. For some
really taken a beating. The top buckles had melted and the vials in the
From l2tpext-bounces@ietf.org Thu Jul 20 14:12:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G3d09-0004jG-59; Thu, 20 Jul 2006 14:11:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1FvURI-0003QF-96
for l2tpext@ietf.org; Wed, 28 Jun 2006 03:26:20 -0400
Received: from mail.us.es ([193.147.175.20] helo=us.es)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvURG-00063K-Q9
for l2tpext@ietf.org; Wed, 28 Jun 2006 03:26:20 -0400
Received: (qmail 22258 invoked from network); 28 Jun 2006 09:26:16 +0200
Received: from unknown (HELO us.es) (192.168.2.11)
by us.es with SMTP; 28 Jun 2006 09:26:16 +0200
Received: (qmail 12334 invoked from network); 28 Jun 2006 07:26:16 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on antivirus1
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=7.5 tests=BAYES_50,SPF_HELO_PASS
autolearn=disabled version=3.1.3
Received: from unknown (HELO us.es) (127.0.0.1)
by us.es with SMTP; 28 Jun 2006 09:26:16 +0200
Received: (qmail 21865 invoked from network); 28 Jun 2006 09:26:17 +0200
Received: from trajano.us.es (193.147.162.130)
by us.es with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP;
28 Jun 2006 09:26:17 +0200
Received: from [193.147.162.138] (trajano.us.es [193.147.162.130])
(authenticated bits=0)
by trajano.us.es (8.12.3/8.12.3/Debian-7.1) with ESMTP id
k5S7QAY9008053
for ; Wed, 28 Jun 2006 09:26:10 +0200
Message-ID: <44A22F2D.3070605@trajano.us.es>
Date: Wed, 28 Jun 2006 09:26:37 +0200
From: Javi
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: l2tpext@ietf.org
Subject: [L2tpext] HDLC Timers (2)
References:
<200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
In-Reply-To: <200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Thu, 20 Jul 2006 14:11:53 -0400
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
If so, you may need too many resources over the IP link between the
LCCEs, it wouldn't be efficient.
If that is the only way to manage L2 timers with pseudo-wires and
L2TPv3, I have no clear it is a good idea to transport L2 frames over IP
networks.
Javi
Ignacio Goyret escribió:
> At 20:51 6/27/2006 +0200, Javi wrote:
>
>> I have a question related to transport of HDLC frames over L2TPv3 (RFC 4349):
>>
>> HDLC identifies a number of timers that may be used by an HDLC link (which
>> is operating in the reliable ABM Mode) to provide reliable data transmission,
>> such as the Acknowledgement Timer (T1).
>>
>> How are these timers managed in transport of HDLC frames over L2TPv3 and PWEs?.
>> The transport over IP may result in an expiration of the timers.
>>
>> Javi
>>
>
> I would expect the timers to work the same way as they do over a regular
> point to point link.
>
> Depending on the quality of the link between the LCCEs, the expiration times
> may need tweaking though.
>
> -Ignacio
>
> _______________________________________________
> 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-bounces@ietf.org Thu Jul 20 14:12:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G3d09-0004jQ-GM; Thu, 20 Jul 2006 14:11:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1G0yL0-0005Y3-NT
for l2tpext@ietf.org; Thu, 13 Jul 2006 06:22:30 -0400
Received: from mail.us.es ([193.147.175.20] helo=us.es)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0yKz-0003NU-8J
for l2tpext@ietf.org; Thu, 13 Jul 2006 06:22:30 -0400
Received: (qmail 18324 invoked from network); 13 Jul 2006 12:22:26 +0200
Received: from unknown (HELO us.es) (192.168.2.12)
by us.es with SMTP; 13 Jul 2006 12:22:26 +0200
Received: (qmail 5573 invoked from network); 13 Jul 2006 10:22:25 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on antivirus2
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=7.5 tests=BAYES_50,SPF_HELO_PASS
autolearn=disabled version=3.1.3
Received: from unknown (HELO us.es) (127.0.0.1)
by us.es with SMTP; 13 Jul 2006 12:22:25 +0200
Received: (qmail 17633 invoked from network); 13 Jul 2006 12:22:27 +0200
Received: from trajano.us.es (193.147.162.130)
by us.es with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP;
13 Jul 2006 12:22:27 +0200
Received: from [193.147.162.138] (trajano.us.es [193.147.162.130])
(authenticated bits=0)
by trajano.us.es (8.12.3/8.12.3/Debian-7.1) with ESMTP id
k6DAMKY9015940
for ; Thu, 13 Jul 2006 12:22:20 +0200
Message-ID: <44B61EDC.8000000@trajano.us.es>
Date: Thu, 13 Jul 2006 12:22:20 +0200
From: Javi
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: l2tpext@ietf.org
References:
<200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
In-Reply-To: <200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-Mailman-Approved-At: Thu, 20 Jul 2006 14:11:53 -0400
Subject: [L2tpext] Changing HDLC Timers in Remote Systems
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
Another question related to transport of HDLC (or LAPB) frames over L2TPv3:
HDLC identifies a number of timers that may be used by an HDLC link
(which is operating in the reliable ABM Mode) to provide reliable data
transmission, such as the Acknowledgement Timer (T1).
According RFC 4349 (HDLCPWs over L2TPv3), depending on the quality of
the link between the LCCEs, the HDLC expiration times may need tweaking
though.
If so, it may need a PSN with excellent QoS or to change HDLC timers in
HDLC terminales (Remote System for RFC 4349), but the last, changing all
terminals, is not a viable solution, I think.
Javi
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext
From l2tpext-bounces@ietf.org Thu Jul 20 14:12:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G3d09-0004jL-Ah; Thu, 20 Jul 2006 14:11:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1FwDS9-0000IJ-ME
for l2tpext@ietf.org; Fri, 30 Jun 2006 03:30:13 -0400
Received: from mail.us.es ([193.147.175.20] helo=us.es)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwDS7-00014f-6a
for l2tpext@ietf.org; Fri, 30 Jun 2006 03:30:13 -0400
Received: (qmail 14871 invoked from network); 30 Jun 2006 09:30:09 +0200
Received: from unknown (HELO us.es) (192.168.2.12)
by us.es with SMTP; 30 Jun 2006 09:30:09 +0200
Received: (qmail 21858 invoked from network); 30 Jun 2006 07:30:07 -0000
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on antivirus2
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=7.5 tests=BAYES_50,SPF_HELO_PASS
autolearn=disabled version=3.1.3
Received: from unknown (HELO us.es) (127.0.0.1)
by us.es with SMTP; 30 Jun 2006 09:30:07 +0200
Received: (qmail 21308 invoked from network); 30 Jun 2006 09:30:07 +0200
Received: from trajano.us.es (193.147.162.130)
by us.es with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP;
30 Jun 2006 09:30:07 +0200
Received: from [193.147.162.138] (trajano.us.es [193.147.162.130])
(authenticated bits=0)
by trajano.us.es (8.12.3/8.12.3/Debian-7.1) with ESMTP id
k5U7U1Y9031687; Fri, 30 Jun 2006 09:30:02 +0200
Message-ID: <44A4D2FD.2090503@trajano.us.es>
Date: Fri, 30 Jun 2006 09:30:05 +0200
From: Javi
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Ignacio Goyret
Subject: Re: [L2tpext] HDLC Timers
References:
<200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
In-Reply-To: <200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Thu, 20 Jul 2006 14:11:53 -0400
Cc: l2tpext@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
And another question. Terminals have usually setup a value for the L2
timers. If you need "tweaking though" them, it would have to be done in
all the terminals, which doesn't seem rasonable. And, generally, L2
timers negotiation is not implemented. Which is the solution of
L2TPv3+PWE then?
-Javi
Ignacio Goyret escribió:
> At 20:51 6/27/2006 +0200, Javi wrote:
>
>> I have a question related to transport of HDLC frames over L2TPv3 (RFC 4349):
>>
>> HDLC identifies a number of timers that may be used by an HDLC link (which
>> is operating in the reliable ABM Mode) to provide reliable data transmission,
>> such as the Acknowledgement Timer (T1).
>>
>> How are these timers managed in transport of HDLC frames over L2TPv3 and PWEs?.
>> The transport over IP may result in an expiration of the timers.
>>
>> Javi
>>
>
> I would expect the timers to work the same way as they do over a regular
> point to point link.
>
> Depending on the quality of the link between the LCCEs, the expiration times
> may need tweaking though.
>
> -Ignacio
>
> _______________________________________________
> 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-bounces@ietf.org Mon Jul 24 14:15:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G54xp-0000cd-72; Mon, 24 Jul 2006 14:15:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1G54xn-0000bZ-8x
for l2tpext@ietf.org; Mon, 24 Jul 2006 14:15:31 -0400
Received: from hoemail2.lucent.com ([192.11.226.163])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G54xl-0003Li-0r
for l2tpext@ietf.org; Mon, 24 Jul 2006 14:15:31 -0400
Received: from horh1.emsr.lucent.com (h135-112-138-211.lucent.com
[135.112.138.211])
by hoemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k6OIFRbL007477;
Mon, 24 Jul 2006 13:15:27 -0500 (CDT)
Received: from new-wopr.eng.ascend.com (new-wopr.eng.ascend.com
[135.140.53.19])
by horh1.emsr.lucent.com (8.12.11/8.12.11) with ESMTP id k6OIFOFH000337;
Mon, 24 Jul 2006 13:15:26 -0500 (CDT)
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [135.140.53.169])
by new-wopr.eng.ascend.com (8.11.6+Sun/8.10.2) with ESMTP id
k6OIFNk03000; Mon, 24 Jul 2006 11:15:23 -0700 (PDT)
Received: from igoyret-t23 (dhcp-135-140-27-193 [135.140.27.193])
by cliff.eng.ascend.com (8.13.1/8.13.1) with SMTP id k6OIFMgK015097;
Mon, 24 Jul 2006 11:15:23 -0700
Message-Id: <200607241815.k6OIFMgK015097@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2
Date: Mon, 24 Jul 2006 11:04:17 -0700
To: Javi
From: Ignacio Goyret
Subject: Re: [L2tpext] HDLC Timers
In-Reply-To: <44A4D2FD.2090503@trajano.us.es>
References: <200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
<200606272209.k5RM9GhL022097@cliff.eng.ascend.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: l2tpext@ietf.org
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
At 09:30 6/30/2006 +0200, Javi wrote:
>And another question. Terminals have usually setup a value for the L2
>timers. If you need "tweaking though" them, it would have to be done in
>all the terminals, which doesn't seem rasonable. And, generally, L2
>timers negotiation is not implemented. Which is the solution of
>L2TPv3+PWE then?
The solution is to make sure the network between the LCCEs is properly
engineered so you won't have to worry about HDLC timers.
If the network does not have any SLAs of any kind, the network response
may be random. In situations like these, your only choice may be to adjust
the appropriate HDLC timers, thus the comment on the draft.
HTH,
-Ignacio
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext
From l2tpext-bounces@ietf.org Mon Jul 24 15:50:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G56RI-0001kM-65; Mon, 24 Jul 2006 15:50:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1G56RG-0001jJ-E4; Mon, 24 Jul 2006 15:50:02 -0400
Received: from oak.neustar.com ([209.173.53.70])
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1G56RG-0007uA-2H; Mon, 24 Jul 2006 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
[10.31.47.10])
by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k6OJo1p0006965
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Mon, 24 Jul 2006 19:50:01 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
id 1G56RF-0005Gx-ML; Mon, 24 Jul 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id:
Date: Mon, 24 Jul 2006 15:50:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: l2tpext@ietf.org
Subject: [L2tpext] I-D ACTION:draft-ietf-l2tpext-radius-ext-nas-port-00.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: l2tpext-bounces@ietf.org
--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 : RADIUS & L2TP Extended NAS-Port AVPs
Author(s) : T. Mistretta, et al.
Filename : draft-ietf-l2tpext-radius-ext-nas-port-00.txt
Pages : 14
Date : 2006-7-24
This document defines additional Layer 2 Transfer Protocol (L2TP) and
Remote Authentication Dial In User Service (RADIUS) Attribute-Value
Pairs (AVPs) to communicate Network Access Server (NAS) informational
ASCII text and port usage information between L2TP peers during call
establishment to facilitate authorization, accounting and logging.
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-radius-ext-nas-port-00.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-l2tpext-radius-ext-nas-port-00.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-ietf-l2tpext-radius-ext-nas-port-00.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
server="mailserv@ietf.org"
Content-Type: text/plain
Content-ID: <2006-7-24124743.I-D@ietf.org>
ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-radius-ext-nas-port-00.txt
--OtherAccess
Content-Type: Message/External-body;
name="draft-ietf-l2tpext-radius-ext-nas-port-00.txt";
site="ftp.ietf.org"; access-type="anon-ftp";
directory="internet-drafts"
Content-Type: text/plain
Content-ID: <2006-7-24124743.I-D@ietf.org>
--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext
--NextPart--