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

Re: Bridging non-IP traffic over IPSec

To: Stephen Kent <kent@bbn.com>
Subject: Re: Bridging non-IP traffic over IPSec
From: Eric Bomarsi <ebomarsi@xedia.com>
Date: Mon, 22 Feb 1999 09:19:17 -0500
Cc: "Scott G. Kelly" <skelly@redcreek.com>, John Shriver <jas@shiva.com>, ipsec@tis.com
Organization: xedia.com
References: <199902182244.RAA24979@brill.shiva.com> <36CCBCED.A7B5FA62@redcreek.com> <v04011716b2f37eb4c787@[128.33.238.58]>
Sender: owner-ipsec@ex.tis.com


Stephen Kent wrote:

> Eric,
>
> ESP requires the next protocol to be a transport protocol or IP, so
> carrying an Ethernet frame directky above ESP would not be valid.
>
> Steve

What about.....

In RFC 1700 the IP protocol numbers include:

97     ETHERIP     Ethernet-within-IP Encapsulation     [RXH1]

/Eric Bomarsi

Follow-Ups:

Re: Bridging non-IP traffic over IPSec

From: John Shriver <jas@shiva.com>

Re: Bridging non-IP traffic over IPSec

From: Stephen Kent <kent@bbn.com>

References:

Re: Bridging non-IP traffic over IPSec

From: John Shriver <jas@shiva.com>

Re: Bridging non-IP traffic over IPSec

From: "Scott G. Kelly" <skelly@redcreek.com>

Re: Bridging non-IP traffic over IPSec

From: Stephen Kent <kent@bbn.com>

Prev by Date: Re: Bridging non-IP traffic over IPSec
Next by Date: Re: Bridging non-IP traffic over IPSec
Prev by thread: Re: Bridging non-IP traffic over IPSec
Next by thread: Re: Bridging non-IP traffic over IPSec
Index(es):
- Main
- Thread