Thanks, Alice. There are additional comments from other IESG members
that we need to address:
*Brian Carpenter:*
*Discuss:*
*[2006-07-03]* Points from Gen-ART review by Francis Dupont:
> - 2.2 c): must -> MUST?
...
> - 3.2: may -> MAY?
...
> - (technical) 3.3: I am not convinced at all by the very last part
> (fragmentation/reassemble recommendation) because it is a layer
violation
> and the goal (manage the issue at only one place as explain in
> L2TPFRAG section 5.1) is not explained.
...
> - 4: For Ethernet VLAN PW, VLAN tag rewrite ...: can't parse this
statement
[BC] I think I can, but the sentence is very hard to understand. For
clarity,
shouldn't it be something like
The VLAN tags of an Ethernet VLAN PW may be rewritten by NSP at
the egress LCCE, which is outside the scope of this document (see
Section 3.1).
> - 4: there is no TOS octet or QoS field in the IP header (look at
RFC 2474?)
[BC] Indeed, there is no "for example" about it; there only the DSCP.
> 5: should -> SHOULD ??
*Comment:*
*[2006-07-03]* See editorial issues in Gen-ART review:
http://www.alvestrand.no/ietf/gen/reviews/draft-ietf-l2tpext-pwe3-ethernet-07-dupont.txt
*Lars Eggert:*
*Discuss:*
*[2006-06-30]* Section 5., paragraph 3:
> LCCEs SHOULD monitor for congestion (by using explicit congestion
> notification, or by measuring packet loss) in order to ensure that
> the service using the Ethernet or Ethernet VLAN PW may be maintained.
> When severe congestion is detected (for example when enabling
> Sequencing and detecting that the packet loss is higher than a
> threshold) the Ethernet or Ethernet VLAN PW SHOULD be halted by
> tearing down the L2TP session via a CDN message. The PW may be
> restarted by manual intervention, or by automatic means after an
> appropriate waiting time. Note that the thresholds and time periods
> for shutdown and possible automatic recovery need to be carefully
> configured. This is necessary to avoid loss of service due to
> temporary congestion, and to prevent oscillation between the
> congested and halted states.
RFC3985 also says: "Where congestion is avoided by shutting down a PW,
a suitable mechanism must be provided to prevent it from immediately
returning to service and causing a series of congestion pulses." I
don't see such a mechanism in this draft, only the above
acknowledgment of the issue and the recommendation of careful
configuration.
(This is identical to the DISCUSS I have raised
against draft-ietf-pwe3-atm-encap. As far as I know, PWE3 is working
on an approach for addressing this. This document, however, belongs to
a different WG, so I'm not sure if any resolution that PWE3 comes up
with would apply to this document as well. I'd hope that it would -
can the authors/ADs confirm?)
*Cullen Jennings:*
*Discuss:*
*[2006-07-05]* I may not understand the congestion control technique but
it looks like it says, "in case of congestion, pull the plug". I don't
believe anyone will implement this congestion control suggestions - and
if they do, I don't believe the resulting systems will be usable - they
will be impossible to manage not to mention the incredible DOS
opportunities. No advice on the threshold is provided. I think this
needs to be updated to either be clear no congestion control is provided.
The section titled "Applicability Statement" gives me no idea where this
is applicable and where it is not.
*Dan Romascanu:*
*Discuss:*
*[2006-07-03]* I made the following two comments during the IESG LC. The
comments were not addressed:
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.
Maria A. Dos Santos (mariados) wrote:
Mark, Francis,
Please see response inline, I believe I addressed
all issues. Please check a look at the updated
version attached.
thanx,
Alice
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art
