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

Re: [Fwd: Deprecation of AH header from the IPSEC tool kit]

To: Dave Perks <Dave_Perks@mitel.com>
Subject: Re: [Fwd: Deprecation of AH header from the IPSEC tool kit]
From: Dan McDonald <danmcd@Eng.Sun.COM>
Date: Wed, 14 Jun 2000 11:52:49 -0700 (PDT)
CC: IP Security List <ipsec@lists.tislabs.com>
In-Reply-To: <3947CC5F.63D6EF93@mitel.com> from Dave Perks at "Jun 14, 2000 02:18:07pm"
Sender: owner-ipsec@lists.tislabs.com

> > IPSEC+AH would seem to be a good choice for all control traffic exchange
> > between routers. If this exchange is confidential, the ESP could be used as
> > well.
> 
> RIPV2 is multicast, and AFAIK IPSEC hasn't addressed keying of multicast
> sessions.

The tools are there for people to build multicast key management protocols
for IPsec.  An IPsec implementation should be able to handle manually-added
multicast SAs already.  Layering one's experimental multicast KM
implementation on top shouldn't be difficult, modulo the actual hard work of
building a multicast KM protocol.

Dan

References:

[Fwd: Deprecation of AH header from the IPSEC tool kit]

From: Dave Perks <Dave_Perks@mitel.com>

Prev by Date: Re: Deprecation of AH header from the IPSEC tool kit
Next by Date: Re: Deprecation of AH header from the IPSEC tool kit
Prev by thread: [Fwd: Deprecation of AH header from the IPSEC tool kit]
Next by thread: I-D ACTION:draft-ietf-ipsec-doi-tc-mib-03.txt
Index(es):
- Main
- Thread