Re: [dhcwg] draft-ietf-dhc-packetcable-03.txt

Thomas Narten <> Tue, 22 October 2002 16:19 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id MAA24629 for <>; Tue, 22 Oct 2002 12:19:52 -0400 (EDT)
Received: (from mailnull@localhost) by (8.11.6/8.11.6) id g9MGLhs23870 for; Tue, 22 Oct 2002 12:21:43 -0400
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id g9MGLhv23867 for <>; Tue, 22 Oct 2002 12:21:43 -0400
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id MAA24614 for <>; Tue, 22 Oct 2002 12:19:21 -0400 (EDT)
Received: from (localhost.localdomain []) by (8.11.6/8.11.6) with ESMTP id g9MGJDv23771; Tue, 22 Oct 2002 12:19:13 -0400
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id g9MGIQv23696 for <>; Tue, 22 Oct 2002 12:18:26 -0400
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id MAA24486 for <>; Tue, 22 Oct 2002 12:16:04 -0400 (EDT)
Received: from ( []) by (8.12.2/8.12.2) with ESMTP id g9MGI9ol027192; Tue, 22 Oct 2002 12:18:09 -0400
Received: from ( []) by (8.12.3/NCO/VER6.4) with ESMTP id g9MGI8lJ104850; Tue, 22 Oct 2002 10:18:08 -0600
Received: from (narten@localhost) by (8.11.6/8.11.6) with ESMTP id g9MGFR831663; Tue, 22 Oct 2002 12:15:27 -0400
Message-Id: <>
To: Paul Duffy <>
Subject: Re: [dhcwg] draft-ietf-dhc-packetcable-03.txt
In-Reply-To: Message from Paul Duffy <> of "Wed, 16 Oct 2002 15:26:10 EDT." <>
Date: Tue, 22 Oct 2002 12:15:27 -0400
From: Thomas Narten <>
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>

Paul Duffy <> writes:

> RFC 2131 Section 4.4.1 "The time over which the client collects
> messages and the mechanism used to select one DHCPOFFER are
> implementation dependent".  PacketCable does not feel CCC.1/.2 in
> any way modifies the RFC.

OK, I think we're OK then. What would be good is if the words in the
document communicated clearly what is going on (at a high-level) so
its clear how the option is used (at a high-level) and that the usage
is consistent with the DHC specs.

> > >    Due to specific needs of the MTA configuration process (described in
> > >    [5]), a new CableLabs Client Configuration (CCC) option is needed for
> > >    the DHCP protocol.  Both CM and MTA DHCP clients will request this
> > >    option.  When requested, both the CM and TSP DHCP servers will
> > >    populate this option into DHCP responses.
> >
> >
> >Doesn't the client also provide this option and fill in some info?
> >better to say this above (one or two sentences here would suffice). Or
> >maybe just merge Section 9 text into the text here.

> No, an MTA DHCP client never populates CCC option content into its any if 
> its requests.  The PacketCable MTA provisioning  specification (section 7) 
> contains detailed descriptions of when the CCC option is/is not populated 
> into DHCP messaging.

> PacketCable's intent is to specify option syntax in the draft/RFC, while 
> referring to the PacketCable MTA prov specification for usage 
> details.  Otherwise, we're going to end up pulling large pieces of the 
> PacketCable provisioning spec into this draft...lots of duplication between 
> the documents (which I thought we agreed was undesirable).


> That said, I can add a sentence or two stating that the client never 
> populates CCC option content into DHCP request messages.

This is all I'm asking for. So that at a high-level one can understand
what is going on. The details can be elsewhere.

> >Should this document add a normative references to
> >draft-ietf-dhc-concat-05.txt (which has been approved by the IESG, so
> >referencing it shouldn't be a problem)? Seems like that would make
> >sense.

> If you feel inclusion of this draft is a hard requirement, PacketCable will 
> have to open this issue with the manufacturers...further delaying the 
> progress of this draft (not good for us).  I'm also going to need an RFC # 
> for the ref ?

Note: dhc-concat has been approved by the IESG, so this document
doesn't need to wait for it.

The question is, should this document require the other as well? Seems
to me like that might be useful. Hence, I asked.

> >The CCC options for configuring Kerberos parameters seems odd to me
> >(what kerberos document talks about the need for tuning these
> >parameters?). The IESG may want this reviewed by someone with kerberos
> >clue. (I'm just saying this so that there are no surprises should this
> >issue come up later.)

> This is a specific need of a PacketCable MTA.  It does not present any 
> issues with the Kerberos RFCs.  The CCC option is, by definition, Cablelabs 
> specific, so PacketCable does not see this causing any issues with non 
> Cablelabs devices.

If there are no issues with the kerberos RFCs, why do you need an
option to tune how they behave?

In terms of how to proceed, you might consider posting proposed text
for each of the items prior to reissuing the draft. That way, you're
more likely to get quick review of the new wording and that might save
on the need for an additional revision.

dhcwg mailing list