[dhcwg] max-unacked-bndupd

[Damien Neil <Damien.Neil at nominum.com>]

draft-ietf-dhc-failover-12.txt defines a "max-unacked-bndupd" option,  
which is sent in all failover CONNECT and CONNECTACK messages.  This  
is defined as follows in section 12.14:

   The maximum number of BNDUPD message that this server is prepared to
   accept over the TCP connection without causing the TCP connection to
   block.

I'm attempting to ascertain whether max-unacked-bndupd applies to the  
number of BNDUPD messages, or the number of binding update  
transactions.  On the face of it, the above definition would appear  
to state the former.  However, sections 7.1 and 7.2 include the  
following phrase:

   The rest of this section is written as though every BNDUPD message
   contains only a single binding update transaction in order to reduce
   the complexity of the discussion.

This introduces a certain confusion between BNDUPD messages and  
binding update transactions.

Since max-unacked-bndupd is defined in section 12.14, which does not  
include the caveat from sections 7.1 and 7.2, I think that a literal  
reading of the draft will conclude that this option applies to  
messages and not transactions.  On the other hand, I think that this  
option is more useful if it is considered to apply to transactions  
rather than messages--the size of a message is variable, depending on  
the number of transactions contained within it, while the size of a  
transaction is somewhat consistent.  (I suspect that the definition  
of this option may predate the ability to pack multiple transactions  
in a single BNDUPD, but my knowledge of the history of the DHCP  
failover draft is insufficient to be certain.)

Any thoughts on how to treat this option would be appreciated.

                    - Damien


_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg