At 9:10 PM -0800 11/14/00, Brian Zill wrote: >Therefore, I'd like to propose that the spec is clarified to limit mutable >options to where they make sense, i.e. in Hop-by-Hop and Destination Options >headers that appear before the Routing Header. Alternatively, we could specify that any mutable options that appear after the AH header are treated as if they were immutable, i.e., included in the authentication computation. Such options, though mutable, would not undergo mutation, so could safely be treated as immutable by AH. >P.S. As an aside, it occurs to me that it might be clearer to define a new >"Intermediate Destination Options" header to take the place of DO1. Then it >could be declared that this new header (if present) MUST appear before the >Routing Header, and that mutable options (if present) MUST appear in either >this new header or a Hop-by-Hop header. Or to put it another way, mutable >options wouldn't be allowed any more in a Destination Options header. This >would also make the spec cleaner - it could get rid of the special case >notations explaining the difference between DO1 and DO2. Sounds reasonable, but seems to me like a significant change for a small benefit at this point. Steve -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
