[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter

To: "'David B. Nelson'" <dnelson@elbrysnetworks.com>
Subject: RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
From: "Glen Zorn" <glenzorn@comcast.net>
Date: Tue, 22 Apr 2008 12:10:01 +0700
Cc: <radiusext@ops.ietf.org>
In-reply-to: <00fe01c8a3b7$ec35a360$1f0a0a0a@xpsuperdvd2>
References: <BLU137-DS3201313A440BD95347E3B93E80@phx.gbl> <01c201c89e64$259ca440$1f0a0a0a@xpsuperdvd2> <001601c89ea3$12f2f7b0$33da787c@arubanetworks.com> <200804150800.53961.stefan.winter@restena.lu> <004001c89ed0$d8b0f100$33da787c@arubanetworks.com> <48046B45.20008@deployingradius.com> <007501c89f8c$57c0f380$99e0787c@arubanetworks.com> <EDC652A26FB23C4EB6384A4584434A04B082B7@307622ANEX5.global.avaya.com> <BLU137-W3582AC60B8DE34F3A13CD93EA0@phx.gbl> <007d01c89f9a$adb6d6c0$99e0787c@arubanetworks.com> <029d01c89fe3$a60d4820$1f0a0a0a@xpsuperdvd2> <400A74A604718E46BC9EE95677BAFF31181A2B@wv-mailsrv2.strixsystems.com> <029e01c89fea$5f2eb7c0$1f0a0a0a@xpsuperdvd2> <400A74A604718E46BC9EE95677BAFF31181A3C@wv-mailsrv2.strixsystems.com> <029f01c89fec$b9f8d5d0$1f0a0a0a@xpsuperdvd2> <000001c8a048$450e3e70$9ae4787c@arubanetworks.com> <034d01c8a0d8$6652ed70$1f0a0a0a@xpsuperdvd2> <006601c8a10c$aa26ad00$6ce2787c@arubanetworks.com> <039601c8a164$fd337a70$1f0a0a0a@xpsuperdvd2> <006601c8a1ed$48962660$65e4787c@aruban etworks.com> <00f901c8a21b$6cf79240$6401a8c0@NEWTON603> <00a501c8a25a$cb4e1eb0$65e4787c@arubanetworks.com> <00fe01c8a3b7$ec35a360$1f0a0a0a@xpsuperdvd2>

owner-radiusext@ops.ietf.org <> scribbled on Monday, April 21, 2008 9:00
PM:

> Glen Zorn writes...
> 
>> A wonderful attitude, except that the only thing the IETF produces is
>> words; therefore, it behooves us to make sure that those words are
>> correct.
> 
> Yes, and I think that what is correct in this case will not be
> accurately described by a well-used phrase such as "backwards
> compatible" or "interoperable".  I think we need spell out
> exactly what we expect, in a couple of sentences.

Good idea.

...



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- Consensus Call on RADEXT WG re-charter
  - From: <Bernard_Aboba@hotmail.com>
- RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- Re: Consensus Call on RADEXT WG re-charter
  - From: Stefan Winter <stefan.winter@restena.lu>
- RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- Re: Consensus Call on RADEXT WG re-charter
  - From: Alan DeKok <aland@deployingradius.com>
- Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: Bernard Aboba <bernard_aboba@hotmail.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Matt Holdrege" <Matt.Holdrege@strixsystems.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Matt Holdrege" <Matt.Holdrege@strixsystems.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <d.b.nelson@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "Glen Zorn" <glenzorn@comcast.net>
- RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>

Prev by Date: RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
Next by Date: Re: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
Previous by thread: RE: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
Next by thread: Re: Meaning of "backward compatible" WAS RE: Consensus Call on RADEXT WG re-charter
Index(es):
- Date
- Thread