RE: [802.1] Connectivity Fault Management draft PAR
One of the items that has been intensively discussed in the 802.1 meetings
is the layering approach to connectivity management (amongst other aspects
of "OAM") used by the service providers who are principally interested in
I can't mimic their terms, but essentially the approach is to isolate faults
to the limits of one's visibility at a certain layer in the hierarchy, and
then from one or more of the boundary points at that layer of visibility to
ask questions of the layer below (or make a request to someone who is able
and authorized to do so). For example users may see and end to end service,
with little detail about how that service is made up of separate providers,
each of which does not (by policy) reveal the internal details of how they
This model applies right layer by layer or step by step from the grand
detail to the eventual micro-detail. Just as it applies to connections
fulfilled by a number of concatenated providers, each providing connections
using many LANs concatenated by bridges, the same layering of concerns
applies to the difference between LANs concatenated by bridges as opposed to
the internal details of the LANs themselves (stations interconnected by
media access control specific methods).
This model is important as it means that 802.1 is not trying to boil the
ocean with this PAR, and in particular it is not trying to boil the seas and
rivers that compose each of the individual MACs. There is absolutely no
suggestion anywhere that MAC specific detail should feature in this work.
Given the complexity of new MACs I am not at all surprised that fault
management for an individual MAC proves far more difficult than fault
management at the level of bridges operating using those MACs (or at the
level subnetworks of bridges that use those MACs).
[mailto:email@example.com]On Behalf Of Richard Brand
Sent: Tuesday, January 27, 2004 1:58 PM
To: Tony Jeffree
Cc: firstname.lastname@example.org; email@example.com; Grow, Bob;
Subject: Re: [802.1] Connectivity Fault Management draft PAR
Having read the draft, seeing a portion of the very large slide presentation
at the January interim, and then rereading the scope of this PAR covering
"transport fault management", I would offer that this is major new work
for 802.1 that could have a major effect on many if not all 802 members.
management has potential applicability to all 802 LANs.
Given this scope, I would strongly recommend that an 802.1 Study Group be
for this activity before the requesting of a PAR, in order to give notice
802 members of your intentions. However, in line with the contents of
2, I would settle for an evening tutorial presentation in March as is
recommended" in the Procedure. This would allow all 802 members the
to participate/provide input for a potential PAR in July.
In this case, I am speaking for myself as a member and not for the 802.3
Group, however I will bring it up to my group at our March plenary. FYI,
ran thru many study group meetings in arriving at an acceptable scope for
segment of P802.3ah and we only had one MAC to deal with.
Liaison rep from 802.3 to 802.1
Tony Jeffree wrote:
> This is notification under Procedure 2 - "Procedure for PARs" that 802.1
> intends to request SEC approval of the following draft PAR at the March
> 2004 closing SEC meeting:
> =>IEEE 802.1 Email List user information:
=>IEEE 802.1 Email List user information: