RE: [dhcwg] I-D ACTION:draft-ietf-dhc-rapid-commit-opt-02.txt

Thanks Kostur and see my inline comments.

>Section 3.1: 
>The first step says "The client broadcasts a DHCPDISCOVER 
>mess on its local physical."  Physical what?  Interface, I presume?

To sync current term. we wrote " physical subnet " 
I guess subnet is omitted... sorry.

>The second step talks about using the client identifier or chaddr 
>plus assigned network address as the identifier for the lease.  
>I believe this puts it in conflict with RFC 2131 (which talks about
using
>a subnet address, not necessarily the address of the lease), and 
>RFC 3046 which adds in the Remote ID.  I believe that this draft should

>probably reference RFC 3046 on this topic.

I am not sure why it occurs confliction with RFC2131.

>Come to think of it, it looks like this draft re-iterates a bunch of
wording 
>that is already in RFC 2131... 
>Does this really need to be restated, or would a reference back to the 
>"normal" DHCP behaviour as defined in RFC 2131 be sufficient?

As stated, I also think it is not significant issue. I am citing
Bernie's
response as below:

I'm pretty neutral on the issue of whether or not to copy text from
2131. When we eventually revise 2131, I believe we'd incorporate this
capability (rapid commit) into the revised 2131 text so I don't think it
is a significant issue. We could remove the text for those steps where
there are no differences (such as step 4 - only) and replace it with
"see RFC 2131". But, this may just increase the confusion (or at least
complexity of following the flow)?

Thought ? or we still need to remove it ?

>Section 4: 
>This states that a client SHOULD include this option in a discover if
it's 
>prepared to perform the DISCOVER-ACK exchange.  Shouldn't that be 
>a MUST since there is that if clause at the end?

I thought MUST is too hard, but I have no hard stance to replace it
if we agree that.

- Daniel (Soohong Daniel Park)
- Mobile Platform Laboratory, SAMSUNG Electronics. 

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