Re: [dhcwg] FW: Discussion of draft-ietf-dhc-l2ra-01.txt prior to dhc WG last call

Ted,

> > 4.1.1 seems to go into too much detail about the actual DHCP protocol.
> >
> > <Bharat>
> > We had started with minimal set of explanation but few internal
> > reviewers and one external reviewer specifically asked few questions
> > because of which we end up explaning everything here. I think this
> > way it looks complete and does not left anything question open.
> > </Bharat>
>
> This is a common problem.   The solution isn't to add text to your
> draft, though - it's to refer to the RFC that defines the behavior in
> question.   If the reader is not familiar with that RFC, they can go
> get it.   The problem is that the more language from RFC A that we
> stuff into RFC B, the more likely it is that we will get it wrong and
> accidentally advice an implementor to do something that we claim RFC A
> said to do, but that it did not actually say to do.
>
> So I'd really like to see you address this problem that way, rather
> than with all this explanatory text.   Remember that the purpose of a
> standards-track RFC is to specify how to implement a protocol - it is
> not to act as an introductory text.

Yes. I completely agree with you on this.

Though the text which we have put up in this draft repeats some of the text already available in parent RFC but this is required here to set the context to describe a particular DHCP message handling in L2 RA.

Let me look at the text again and as I mentioned earlier, I will try to remove the extra text which is obvious and taken as it is from parent RFC.

Does this sound ok to you?

Thanks,
Bharat

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg