Re: Vendor ID Paylod

"Elfed T. Weaver" <weaver@hydra.dra.hmg.gb> Fri, 06 March 1998 10:21 UTC

Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id FAA01719 for ipsec-outgoing; Fri, 6 Mar 1998 05:21:12 -0500 (EST)
Message-Id: <199803061048.CAA18000@relay.la.tis.com>
Comments: Authenticated sender is <weaver@hydra.dra.hmg.gb>
From: "Elfed T. Weaver" <weaver@hydra.dra.hmg.gb>
Organization: DERA
To: ipsec@tis.com
Date: Fri, 06 Mar 1998 10:31:22 +0000
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: Vendor ID Paylod
X-mailer: Pegasus Mail for Win32 (v2.54)
Sender: owner-ipsec@ex.tis.com
Precedence: bulk

> >>>>> "Elfed" == Elfed T Weaver <weaver@hydra.dra.hmg.gb> writes:
>     Elfed> Is this extension to ISAKMP really necessary. It sounds to
>     Elfed> me that what it is meant to achieve can be achieved by
>     Elfed> defining a vendor specific DOI - based primarily on the
>     Elfed> Internet DOI.
> 
>   If I offer a new DOI, and the other end doesn't like it, what do I
> do? How I register the new DOI number? How do I find out what bugs in
> my previous versions I need to work around?
> 
If its Vendor specific then I assume the vendor will load images into 
their kit that support the functionality they wish to test ?

Bug reports, if Doug Maughan had suggested that we support such 
flexibility in ISAKMP 2 years ago the ipsec WG would have erupted 
with hoots of SPOOK ! ;-) ;-)

- Elfed
****************************************************
 "The views expressed above are entirely  those of
the writer and do not represent the views, policy or
understanding of  any other person or official body."

Elfed T. Weaver
DERA
Malvern
UK

weaver@hydra.dra.hmg.gb

****************************************************

Re: Vendor ID Paylod Elfed T. Weaver