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

Re: ISATAP Security (was: RE: I-D Action:draft-ietf-v6ops-rfc3330-for-ipv6-04.txt)



Le 08-01-16 à 07:56, Dunn, Jeffrey H. a écrit :
Marc,

Since I try to provide solutions when I point out what I think are
problems, I suggest the following changes in section 3, Security
Considerations:

This document lists IPv6 address blocks, their associated prefixes and
guidelines associated with them.  The guidelines should improve the
security of networks by the filtering of invalid routing prefixes.
Rules for filtering other special IPv6 address types, such as those
associated with RFC 4214, ISATAP, are beyond the scope of this
document.


Jeffrey,
I may concur with you about people that might want to filter ISATAP traffic.

However, this draft is clearly intended to address blocks and prefixes. This quote is the first sentence of the draft:

"This document describes the global and other specialized IPv6 address blocks. "

To me, it is pretty clear that interface identifiers such as ISATAP or privacy addresses ... are out of scope, from the very beginning of this draft.

I would suggest to write a draft on filtering interface identifiers and submit it to the wg.

Marc.

-----
IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca