[dhcwg] Edit #3 of DHCP spec

[Ralph Droms <[e-mail]>]

  
Narten:
  
  > 17.1.4. Receipt of Reply message
  
  >  If the client includes a Rapid Commit option in the Solicit message,
  >  it will expect a Reply message that includes a Rapid Commit option
  >  in response.  If the client receives a Reply message, it processes
  >  the message as described in section 18.1.6.  If the client does not
  >  receive a Reply message, the client restarts the server solicitation
  >  process by sending a Solicit message that does not include a Rapid
  >  Commit option.

  So, if the client sets the Rapid Commit, because it is in a hurry, the
  process may actually take *longer* because some servers won't respond
  unless the Rapid Commit is not present? This seems like a disincentive
  to using the mechanism, as it might not only be quicker, it might
  actually be longer, and there isn't a way for the client to know
  without just trying. Right?

Response:

Modified Rapid Commit to allow servers to respond with Advertise and
client to respond to Advertise if it does not receive a
Rapid Commit/Reply

*** dhcpv6.tty	Wed May 15 06:14:14 2002
--- dhcpv6-24.txt	Tue Apr 23 15:35:14 2002
***************
*** 1940,1951 ****
        MRD   0
  
     If the client has included a Rapid Commit option and is waiting for
!    a Reply message, the client terminates the retransmission process
!    as soon as a Reply message is received.  If the client receives an
!    Advertise message that includes a Preference option with a preference
!    value of 255, the client immediately begins a client-initiated
!    message exchange (as described in section 18) by sending a Request
!    message to the server from which the Advertise message was received.
  
  
  
--- 1939,1951 ----
        MRD   0
  
     If the client has included a Rapid Commit option and is waiting for
!    a Reply message, the client terminates the retransmission process as
!    soon as a Reply message is received.
! 
!    If the client is waiting for an Advertise message, the mechanism in
!    section 14 is modified as follows for use in the transmission of
!    Solicit messages.  The message exchange is not terminated by the
!    receipt of an Advertise before IRT has elapsed.  Rather, the client
  
  
  
***************
*** 1954,1969 ****
  Internet Draft              DHCP for IPv6 (-24)              22 Apr 2002
  
  
-    If the client receives an Advertise message that does not include
-    a Preference option with a preference value of 255, the client
-    continues to wait until IRT elapses.  If IRT elapses and the client
-    has received an Advertise message, the client SHOULD continue with a
-    client-initiated message exchange by sending a Request message.
- 
-    If the client is waiting for an Advertise message, the mechanism in
-    section 14 is modified as follows for use in the transmission of
-    Solicit messages.  The message exchange is not terminated by the
-    receipt of an Advertise before IRT has elapsed.  Rather, the client
     collects Advertise messages until IRT has elapsed.  Also, the first
     RT MUST be selected to be strictly greater than IRT by choosing RAND
     to be strictly greater than 0.
--- 1954,1959 ----
***************
*** 2039,2047 ****
  17.1.4. Receipt of Reply message
  
     If the client includes a Rapid Commit option in the Solicit message,
!    it will expect a Reply message that includes a Rapid Commit option in
!    response.  If the client receives a Reply message, it processes the
!    message as described in section 18.1.6.
  
  
  17.2. Server Behavior
--- 2028,2039 ----
  17.1.4. Receipt of Reply message
  
     If the client includes a Rapid Commit option in the Solicit message,
!    it will expect a Reply message that includes a Rapid Commit option
!    in response.  If the client receives a Reply message, it processes
!    the message as described in section 18.1.6.  If the client does not
!    receive a Reply message, the client restarts the server solicitation
!    process by sending a Solicit message that does not include a Rapid
!    Commit option.
  
  
  17.2. Server Behavior
***************
*** 2061,2081 ****
     If the client has included a Rapid Commit option in the Solicit
     message and the server has been configured to respond with committed
     address assignments and other resources, the server responds to the
!    Solicit with a Reply message as described in section 17.2.3.  If the
!    server has been configured to respond to the client but has not been
!    configured to respond with committed address assignments and other
!    resources, the server responds with an Advertise message.
  
     Otherwise, the server generates and sends an Advertise message to the
     client.
  
  
- 
- Droms (ed.), et al.            Expires 22 Oct 2002             [Page 30]
- 
- Internet Draft              DHCP for IPv6 (-24)              22 Apr 2002
- 
- 
  17.2.2. Creation and transmission of Advertise messages
  
     The server sets the "msg-type" field to ADVERTISE and copies the
--- 2053,2064 ----
     If the client has included a Rapid Commit option in the Solicit
     message and the server has been configured to respond with committed
     address assignments and other resources, the server responds to the
!    Solicit with a Reply message as described in section 17.2.3.
  
     Otherwise, the server generates and sends an Advertise message to the
     client.
  
  
  17.2.2. Creation and transmission of Advertise messages
  
     The server sets the "msg-type" field to ADVERTISE and copies the

_______________________________________________
dhcwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg