[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Unsupported DOI attributes and values
> There is some text about that in my
> draft-ietf-ipsec-ike-ext-meth-02.txt saying (see the 12.1 first
> paragraph):
> [snip]
> 12.1. Data Attributes, Protocol and Transform IDs
>
> The proposal or transform payload MUST NOT be selected by the responder
> if it contains unknown protocol IDs, transform IDs, data attribute
> types, or data attribute values.
>
> This means that an initiator SHOULD always include a proposal without
> any private-use types or values so that if the other end does not
> understand them then it may select the transform or proposal without
> private-use types or values.
I like that text - I'll put something approximating it into the ipsec-ecn
document
(we're dealing with a new IANA allocated attribute and its values)
and trust that Derrell will get RFC 2407 updated accordingly.
--David
---------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 42 South St., Hopkinton, MA 01748
+1 (508) 435-1000 x75140, FAX: +1 (508) 497-6909
black_david@emc.com
---------------------------------------------------