[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: I-D ACTION:draft-ietf-ipsec-notifymsg-00.txt
For ISAKMP header field error messages (flags, version,
exchange, cookies, message id) it might be easier to
implement and perhaps more beneficial for other reasons
if the entire offending header was supplied rather than
just the offending field.
>2.1 INVALID-PAYLOAD-TYPE
> o Notification Data - contains the subject payload
Perhaps with this message and in others, when
supplying an offending payload the NextHeader field in
the subject payload should be set to the type of the
payload in question.
>2.13 ATTRIBUTES-NOT-SUPPORTED
The transform id in addition to the protocol id should probably
be supplied. Or better yet supply the SA payload with an
offset indicator to the offending attribute.
>2.14 NO-PROPOSAL-CHOSEN
Optionally supply a proposal(s) that might be considered
acceptable in the notification data.
>2.15 BAD-PROPOSAL-SYNTAX
Should probably contain an offset indicator to the offending
byte within the proposal.
>2.16 PAYLOAD-MALFORMED
Also should have an offset indicator and there could be
other messages that might benefit from an offset
indicator as well.
-dave
Follow-Ups: