Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-failover-protocol-04

[kkinnear <[e-mail]>]

I have submitted a new version of the DHCPv6 Failover Protocol:

 draft-ietf-dhc-dhcpv6-failover-protocol-06

https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-failover-protocol/ <https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-failover-protocol/>

which reflects the final changes resulting from the IESG and
directorate reviews to date.  All of these changes are to explain
things more clearly or explicitly.  None of them alter the intended
operation of the protocol.

The first two changes resulted from a COMMENT by Mirja Kuhlewind.

* Expanded the first occurrence of the use of MAX_UNACKED_BNDUPD
  in Section 6.1.1 "Sending a CONNECT message", from the current:

>   o  OPTION_F_MAX_UNACKED_BNDUPD containing the maximum number of BNDUPD
>      messages that this server is prepared to accept over the failover
>      connection without causing the connection to block.

  to the following:

  o  OPTION_F_MAX_UNACKED_BNDUPD containing the maximum number of BNDUPD
     messages that this server is prepared to accept over the failover
     connection without causing the connection to block.  This is to
     implement application level flow control over the connection, so
     that a flood of BNDUPD messages does not cause the connection to block
     and thereby prevent other messages from being transmitted 
     over the connection and received by the failover partner.

* Changed the second place where OPTION_F_MAX_UNACKED_BNDUPD
  is transmitted in Section 6.1.2 "Receiving a CONNECT message", where
  it discusses creating a CONNECTREPLY message, to say the same thing
  as above (as it currently has the same "current" text).

* Fixed several typographical errors observed while making the above
  changes (OPTION_F_MAX_UNACKED_BNDUPD was referenced as
  OPTION_F_UNACKED_BNDUPD).

* Added a missing "a" in recently added paragraph in Security
  Considerations section.

Regards -- Kim