OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [cti] CTI TC Adoption and Interoperability SCs

Hi Trey,

I'm not sure this dialogue is relevant to this list.

Something is getting lost in translation here.

It seems unfair to be excising a quote from a
1989 RFC about much of anything concerning
the DARPA Internet when the design purpose
was to support the NREN, not large-scale public
infrastructure - which was being attempted
over in the OSI Internet venues.  I have otherwise
no quibble with Thompson's contemporary draft.

With that said, Jon's observations in Sec. 1.2.2
apart from the quote -about assuming all code is
flawed - is rather interesting if not prescient, e.g.,

  In general, it is best to assume that the
  network is filled with malevolent entities
  that will send in packets designed to have
  the worst possible effect. This assumption
  will lead to suitable protective design,

The statement could well be a CTI mantra.


On 2015-07-09 09:05 AM, Trey Darley wrote:

Um, Tony, did you take the time to read the RFC draft I posted? It's dated March 9, 2015. I realize that things do move quickly but I would hardly qualify that as an artifact from a bygone era. On the contrary, I would say that it deprecates RFC1122, § 1.2.2.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]