Subject: [clue] Ticket #20 rejecting configure

From: "Duckworth, Mark" <[email-masked]>
Date: Thu, 11 Jul 2013 12:56:32 -0700

Here is the description of ticket #20:
  Add text to Framework for rejecting Configure
  As discussed at virtual interim on May 21st, this needs to be mentioned
  in the framework, so that the subsequent actions can be described.
  (E.g., does the prior configure remain in effect?)
  The details of how this is communicated belong in the solution.

I propose adding a new paragraph to section 9 of the framework.
=== Begin new proposed paragraph ===
A Provider can reject a Configure message for various reasons.  For example, it could be inconsistent with the most recent Advertisement, or the Provider may be unable to honor the Configure message because conditions have recently changed and the Provider is about to send a new Advertisement.  Whatever the reason, the Provider acknowledges receipt of the message and indicates to the Consumer that it is rejecting it.  The Provider's behavior regarding its transmitted capture encodings should not be affected by a rejected Configure message.
=== End new proposed paragraph ===

Any comments or suggestions?

Mark