|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: FCencap: List ALL SOF/EOF codesHi Folks: > David's observation is correct. FC-MI rev 1.8 (28 Sept 2001) > prohibits Class 1 and I can find no letter ballot comments > asking that it be reinstated. The last time I checked, the FC-MI spec was not a "standards track" document (to use IETF terminology). If that's still the case, is FC-MI's prohibition of class 1 a sufficient basis for precluding class 1 support in the encapsulation spec? Charles > -----Original Message----- > From: Ralph Weber [mailto:ralphoweber@compuserve.com] > Sent: Saturday, November 10, 2001 8:52 AM > To: IPS Reflector > Cc: Black_David@emc.com > Subject: Re: FCencap: List ALL SOF/EOF codes > > > David's observation is correct. FC-MI rev 1.8 (28 Sept 2001) > prohibits Class 1 and I can find no letter ballot comments > asking that it be reinstated. > > Therefore, I am forced to agree with David. Class 1 MUST NOT > be mentioned in the FC Encapsulation draft. If necessary, a > note discussing interoperability and FC-MI can be added. > > Thanks. > > Ralph... > > Black_David@emc.com wrote: > > > FC-MI was going to prohibit Class 1 last time I checked. Since the > > I in FC-MI stands for "Interoperability", this seems like a > reasonable > > rationale for excluding Class 1 service. > > > > --David > > --------------------------------------------------- > > David L. Black, Senior Technologist > > EMC Corporation, 42 South St., Hopkinton, MA 01748 > > +1 (508) 435-1000 x75140 FAX: +1 (508) 497-8500 > > black_david@emc.com Mobile: +1 (978) 394-7754 > > --------------------------------------------------- >
Home Last updated: Mon Nov 12 19:17:50 2001 7767 messages in chronological order |