Re: Vendor Private Extension
Telford001@aol.com Sat, 15 July 1995 11:58 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01564;
15 Jul 95 7:58 EDT
Received: from [204.249.96.18] by IETF.CNRI.Reston.VA.US id aa01560;
15 Jul 95 7:58 EDT
Received: from maelstrom.acton.timeplex.com (maelstrom.nexen.com
[204.249.97.5]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id HAA16273;
Sat, 15 Jul 1995 07:45:57 -0400
Received: (from root@localhost) by maelstrom.acton.timeplex.com
(8.6.12/8.6.12) id HAA00605 for rolc-out; Sat, 15 Jul 1995 07:43:13 -0400
Received: from nexen.nexen.com ([204.249.96.18]) by
maelstrom.acton.timeplex.com (8.6.12/8.6.12) with ESMTP id HAA00596 for
<rolc@nexen.com>; Sat, 15 Jul 1995 07:43:10 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Telford001@aol.com
Received: from mail06.mail.aol.com (mail06.mail.aol.com [152.163.172.108]) by
nexen.nexen.com (8.6.12/8.6.12) with ESMTP id HAA16151 for <rolc@nexen.com>;
Sat, 15 Jul 1995 07:43:09 -0400
Received: by mail06.mail.aol.com
(1.37.109.11/16.2) id AA095898485; Sat, 15 Jul 1995 07:41:25 -0400
Date: Sat, 15 Jul 1995 07:41:25 -0400
Message-Id: <950715074124_115396157@aol.com>
To: tlb@eecs.harvard.edu
Cc: rolc@nexen.com, Telford001@aol.com
Subject: Re: Vendor Private Extension
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
In a message dated 95-07-14 15:32:08 EDT, you write: >Recent discussion of vendor private extensions suggest that they have >evolved from being a mechanism for future contingencies, to an >important feature that people want to use right away. > >If you have concrete ideas for uses of VPX at this point in time, then >maybe they should go directly into the spec. Or at least it might >prompt other groups to realize they require similar functionality. > >Could relevant parties summarize their plans for this field to the >list? How can the vendor private extension be standardized? Vendors create differences between their products and the competition in order to give customers a reason to choose their product over the competition's product. The vendor private extension must express such differences. It cannot possible be standard across all the vendor products. Joachim Carlo Santos Martillo Ajami
- Vendor Private Extension James Luciani
- Re: Vendor Private Extension Bruce Cole
- Re: Vendor Private Extension James Luciani
- Re: Vendor Private Extension Bruce Cole
- Re: Vendor Private Extension James Luciani
- Re: Vendor Private Extension Bruce Cole
- Re: Vendor Private Extension James Luciani
- Re: Vendor Private Extension Andrew Smith
- Re: Vendor Private Extension Trevor Blackwell
- Re: Vendor Private Extension Telford001
- Re: Vendor Private Extension Curtis Villamizar
- Re: Vendor Private Extension Tony Li
- Re: Vendor Private Extension Curtis Villamizar
- Re: Vendor Private Extension Tony Li
- Re: Vendor Private Extension Trevor Blackwell