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

For transport items this basically means "uses RADIUS packet formats defined in RFC 2865, 2866 and 5176" (although the ports can be different).

Follow-Ups:
- 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: Alan DeKok <aland@nitros9.org>

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>