PacketCable Security Ticket Control Sub-Option for the DHCP CableLabs Client Configuration (CCC) Option
draft-ietf-dhc-pktc-kerb-tckt-03

Mail send to Thomas on 6-Aug-03:

Hi Thomas,

I have a couple of issue with the DHCP draft:

draft-ietf-dhc-isnsoption-08.txt

I thought I'd just send them to you, in case you already
know the answers...

(1) This option uses 32-bit IP address fields.  It does
say that it is for IPv4-only, but I wonder why...  Is
there some reason why a dual-stack hosts wouldn't want
to use a single DHCP server to find storage servers that
it can access via both IPv4 and IPv6?

(2) Why are the references to iSNS and iFCP informative,
rather than normative?  This document uses terminology
(such as Discovery Domain) that can't be fully understood
without reading those documents.  Besides, I can't
think why it would be important (or even advisable?) to
publish and RFC that describes an option for configuring
a protocol with DCHP before that protocol is actually
published as an RFC...

Margaret

[Ballot discuss]
This document refers normatively to a CableLabs specification. I don't think we should be referring normatively to a document from a body that is not a recognized standards organization.

[Ballot discuss]
What does "locally persisted" mean? I think that the proper phrase is
"locally cached".

Section 4 should state that bit values not known to the client MUST be
ignored, or it will be very difficult to add new options.