Re: [dhcwg] draft-ietf-dhc-concat-01.txt

Ralph Droms <rdroms@cisco.com> writes:

> Thomas - I want to make sure I understand your point
> and to clarify the status of existing implementations.

> Once draft-ietf-dhc-concat-01.txt is accepted as a standard,
> it will be considered as a distinct part of the DHCP
> standard.  Existing implementations will still be in
> compliance with the DHCP specification in RFC2131 and RFC2132.
> However, existing implementations might not be in compliance
> with the new option concatenation standard.

Right.  Note that this is not unlike when an existing Proposed
Standard gets reissued as a new RFC, still at Proposed Standard. The
old one doesn't just vanish, even though one hopes/expects that
everyone will update implementations to be compliant with the newer
one.

> With this interpretation, the wording you suggest for the
> option concatenation draft would not cause existing
> implementations to now become out of compliance with
> the DHCP standard.

> Do I have this right?

Yep.

At some future time (i.e, when 2131 and 2132 get reissued), it might
well make sense to just merge the concat text into that one. But even
then, we'd have the situation that there is the old RFC and the new
one and existing implementations may not adhere to the new one 100%,
at least at first.

Thomas

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