RE: Common Encapsulation: Stale Frame Detection in an IP fabric

[Black_David@emc.com]

Something like that.  If the two endpoints can
agree on a common timebase and control their
relative drift, that's good enough to detect
stale FC frames even if the timebase doesn't correspond
to a wall clock.  I'm wondering about situations
in which an FCIP box is deployed into a situation
where there isn't a good SNTP source available.

Thanks,
--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
---------------------------------------------------

> -----Original Message-----
> From:	Charles Monia [SMTP:cmonia@NishanSystems.com]
> Sent:	Friday, May 25, 2001 9:49 PM
> To:	ips@ece.cmu.edu
> Subject:	RE: Common Encapsulation:  Stale Frame Detection in an IP
> fabric
> 
> Hi David:
> 
> How do you see clock synchronization happening? Does the FCIP end point
> use
> an SNTP handshake?
> 
> Charles
> > -----Original Message-----
> > From: Black_David@emc.com [mailto:Black_David@emc.com]
> > Sent: Friday, May 25, 2001 2:43 PM
> > To: cmonia@NishanSystems.com; ips@ece.cmu.edu
> > Subject: RE: Common Encapsulation: Stale Frame Detection in 
> > an IP fabric
> > 
> > 
> > Question for Charles and the WG:
> > 
> > This proposal is based on synchronizing each node
> > to the same wall clock reference (i.e., SNTP server).
> > Is there any interest in just synchronizing the
> > timestamps between the two ends of an FCIP link
> > without requiring interaction with an external
> > time source?
> > 
> > A possible downside is that an implementation
> > that can support multiple FCIP links may need
> > to maintain a separate time offset (from its
> > internal time source) for each FCIP link.
> > 
> > NOTE: This is a question and not to be taken
> > as a suggestion from a co-chair.
> > 
> > Thanks,
> > --David
> >