OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [security-services] InResponseTo optional

As part of the set of changes to use Response objects in the POST profile,
I forgot to include one necessary change, which is to make the
InResponseTo attribute optional.  It has to be optional because in the
POST case the Response isn't in response to a request.  As we discussed on
the call today, it's also desirable to have this attribute be optional
because a responder might want to respond to a malformed request for
which a RequestID could not be determined.

So below is the specific change to make to core-28, as approved by the
committee on the call today (modulo wording tweaks).  It is also
suggested, for clarity, to move the definition of this optional element to
be after all the required elements, hence after MinorVersion.

 - RL "Bob"


delete current lines 1371-1373

add after line 1379:

  InResponseTo [Optional]
  A reference to the identifier of the request to which the response
  corresponds, if any.  If the response is not generated in response to a
  request, or if the RequestID of a request cannot be determined (because
  the request is malformed), then this attribute MUST NOT be present.
  Otherwise, it MUST be present and match the value of the corresponding
  RequestID attribute.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC