[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FW: IPSec Monitoring MIB works for IPv4 only?
Mike's comment appears quite valid.
Comments on his proposal for the address issue are requested.
Thanks.
---
Tim Jenkins TimeStep Corporation
tjenkins@timestep.com http://www.timestep.com
(613) 599-3610 x4304 Fax: (613) 599-3617
-----Original Message-----
From: Mike Daniele [mailto:daniele@zk3.dec.com]
Sent: Tuesday, November 17, 1998 10:08 AM
To: tjenkins@timestep.com
Cc: bound@zk3.dec.com; wong@zk3.dec.com; daniele@zk3.dec.com
Subject: IPSec Monitoring MIB works for IPv4 only?
Hello Tim,
I just did a quick review of draft-ietf-ipsec-mib-02.txt.
It appears not to support IPv6. That is, tunnel and peer
endpoints are defined as objects with syntax IpAddress, which
is limited to 4 octets and hence can't represent an IPv6 address.
Since IPSec is mandatory for IPv6, it would make little sense
if the IPSec MIB didn't permit implementations by IPv6 nodes.
Since the address-valued objects aren't used to index any tables,
you could simply add equivalent objects of syntax IPv6Address,
and parhaps an enumeration for what address type is in use.
See draft-ietf-ipngwg-ipv6-mib-04.txt for IPv6 textual conventions.
(All the IPv6-related MIBs have been approved as Proposed Std RFCs, I
believe.)
Regards,
Mike
Follow-Ups: