Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: [802.1] Connectivity Fault Management draft PAR



I'd personally like to see the PAR go forward sooner rather than later.  There has been a great deal of communication on these issues with other groups including .3, ITU, and MEF.  So the work hasn't been going on in isolation.  

- Matt

> -----Original Message-----
> From: Norman Finn [mailto:nfinn@cisco.com]
> Sent: Monday, March 15, 2004 3:15 PM
> To: rbrand@nortelnetworks.com
> Cc: Tony Jeffree; Mick Seaman; Bob Grow; dinesh@cisco.com;
> mohan@cisco.com; Malcom Betts; Ali Sajassi; 
> stds-802-sec@cisco.com; IEEE
> 802.1; dpannell@marvel.com
> Subject: Re: [802.1] Connectivity Fault Management draft PAR
> 
> 
> 
> Richard,
> 
> Is this your company position?  Dinesh Mohan, Malcom Betts, 
> Ali Sajassi, and I have
> been working in close cooperation for some time in order to 
> make sure that the
> excellent work being done in ITU-T Q.3/13, where there is an 
> excellent understanding
> of providers and their needs, is complemented by work in IEEE 
> 802.1, which has a
> correspondingly acute understanding of the Ethernet MAC 
> service in general, and of
> bridges, in particular.  For either group to progress without 
> the other would be
> dangerous to the industry and to the progression of "Metro 
> Ethernet" standards.  It
> is essential that both groups work together.  This is my 
> understanding of the
> positions of the above individuals, of our respective 
> companies, and of the two
> Working Groups.  This has been the subject of considerable 
> discussion and, I firmly
> believed, agreement among us all.  I copy all of the above, 
> of course; I wouldn't
> want to put words in their mouths.
> 
> -- Norm
> 
> Richard Brand wrote:
> > Tony:
> > Having read the draft, seeing a portion of the very large 
> slide presentation made
> > 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 effort
> > for 802.1 that could  have a major effect on many if not 
> all 802 members.  Fault
> > management has potential applicability to all 802 LANs.
> > Given this scope, I would strongly recommend that an 802.1 
> Study Group be formed
> > for this activity before the requesting of a PAR, in order 
> to give notice for all
> > 802 members of your intentions.  However, in line with the 
> contents of  Procedure
> > 2, I would settle for an evening tutorial presentation in 
> March as is "highly
> > recommended" in the Procedure.  This would allow all 802 
> members the opportunity
> > 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 Working
> > Group, however I will bring it up to my group at our March 
> plenary.  FYI, 802.3
> > ran thru many study group meetings in arriving at an 
> acceptable scope for our OAM
> > segment of P802.3ah and we only had one MAC to deal with.
> > Regards,
> > Richard Brand
> > 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:
> >>
> >>http://www.ieee802.org/1/files/public/docs2004/ConnectivityF
aultPAR-v1.2a.doc
>>
>>Regards,
>>Tony
>>
>>=>IEEE 802.1 Email List user information:
>>http://www.ieee802.org/1/email-pages/
> 



=>IEEE 802.1 Email List user information:
http://www.ieee802.org/1/email-pages/


=>IEEE 802.1 Email List user information:
http://www.ieee802.org/1/email-pages/