[L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05.txt]
"W. Mark Townsley" <townsley@cisco.com> Thu, 26 May 2005 12:29 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24801 for <l2tpext-archive@ietf.org>; Thu, 26 May 2005 08:29:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbHmv-0008CO-GJ for l2tpext-archive@ietf.org; Thu, 26 May 2005 08:48:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DbHSJ-0002iu-AC; Thu, 26 May 2005 08:27:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DbHSH-0002ip-Ux for l2tpext@megatron.ietf.org; Thu, 26 May 2005 08:27:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24521 for <l2tpext@ietf.org>; Thu, 26 May 2005 08:27:16 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DbHkr-000883-M7 for l2tpext@ietf.org; Thu, 26 May 2005 08:46:31 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 26 May 2005 08:27:08 -0400
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 j4QCR54u000205 for <l2tpext@ietf.org>; Thu, 26 May 2005 08:27:06 -0400 (EDT)
Received: from [192.168.1.101] (ams-clip-vpn-dhcp203.cisco.com [10.61.64.203]) by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id BHB37181; Thu, 26 May 2005 05:27:05 -0700 (PDT)
Message-ID: <4295C098.7030100@cisco.com>
Date: Thu, 26 May 2005 08:27:04 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: l2tpext@ietf.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA24521
Subject: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05.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-Archive: <http://www1.ietf.org/pipermail/l2tpext>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Forwarding to l2tpext for comments there. Thanks for the review, Mark. - Mark -------- Original Message -------- Subject: draft-ietf-l2tpext-pwe3-fr-05.txt Date: Thu, 26 May 2005 00:50:05 +0100 From: Mark Lewis <mark@mjlnet.com> Reply-To: mark@mjlnet.com To: mark@townsley.net CC: iesg@ietf.org Hi Mark, Here's a review of draft-ietf-l2tpext-pwe3-fr. Apologies if some of my comments are off-the-mark as I unfortunately had to review it in haste. It seems like another very good draft to me. Just one or two relatively minor comments: 1. Is it worth mentioning in the introduction that, ‘LCCEs supporting Frame Relay DLCI pseudowires perform Frame Relay PVC switching and MAY (must?) participate in LMI with connected CE devices.’ Also, might it be worth mentioning in the introduction that, ‘Frame Relay traffic may also be transported between LCCEs using an HDLC pseudowire [draft-ietf-l2tpext-pwe3- hdlc]. When Frame Relay traffic is transported over an HDLC pseudowire, however, LCCEs do not perform Frame Relay PVC switching, and do not participate in LMI.’ ?? 2. In section 3, might it be worth stating that, ‘LCCEs MAY [must?] participate in FR Local Management Interface [LMI]. An LCCE MAY transmit an SLI message indicating a change in the status of the local PVC as the result of the reception of an LMI message. Similarly, an LCCE receiving an SLI indicating a change in status of a FR PVC (on a remote LCCE) MAY send a corresponding LMI message to its connected CE device indicating this status change.’ The above wording may well be a little rough, but in general might it be worth explicitly mentioning *possible* interaction between LMI and SLI on LCCEs? 3. In section 3.5, is it worth explicitly stating the purpose of the FR header length AVP somewhere (or is in the draft elsewhere, and I just missed it?!)? Obviously, this AVP is used to advertise the FR header length between LCCEs, but is it worth explicitly stating somewhere why this is necessary/desirable?? 4. In section 4.1 support for 2 and 4 byte FR headers are discussed. Off the top of my head, isn’t there is also a 3 byte header format(Q.922)? Might it be an idea to state why the 3 byte header format is not supported (or why it is irrelevant in this context?). Also, (and I am admittedly being pedantic here!) the words ‘FR header’ obviously (I think!) refer to the FR Address field. Would it be a good idea to change ‘FR header’ to ‘FR header (Address Field)’ at least the first time it appears (again, this may well be too pedantic/utterly unnecessary!). Anyway, hope that helps, Mark _______________________________________________ L2tpext mailing list L2tpext@ietf.org https://www1.ietf.org/mailman/listinfo/l2tpext
- [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05.txt] W. Mark Townsley
- Re: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Carlos Pignataro
- Re: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Scott Wainner
- RE: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Mark Lewis
- [L2tpext] draft-ietf-l2tpext-pwe3-fr-05.txt Carlos Pignataro
- Re: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Carlos Pignataro
- RE: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Mark Lewis
- Re: [L2tpext] [Fwd: draft-ietf-l2tpext-pwe3-fr-05… Carlos Pignataro