Re: [dhcwg] draft-ietf-dhc-pktc-kerb-tckt-01.txt

Paul Duffy <paduffy@cisco.com> Wed, 23 April 2003 19:29 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03093 for <dhcwg-archive@odin.ietf.org>; Wed, 23 Apr 2003 15:29:47 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3NJfvx22569 for dhcwg-archive@odin.ietf.org; Wed, 23 Apr 2003 15:41:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NJfv822566 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 23 Apr 2003 15:41:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03071 for <dhcwg-web-archive@ietf.org>; Wed, 23 Apr 2003 15:29:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198Pxw-0006hR-00 for dhcwg-web-archive@ietf.org; Wed, 23 Apr 2003 15:31:36 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 198Pxw-0006hN-00 for dhcwg-web-archive@ietf.org; Wed, 23 Apr 2003 15:31:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NJdg822465; Wed, 23 Apr 2003 15:39:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3NJao821497 for <dhcwg@optimus.ietf.org>; Wed, 23 Apr 2003 15:36:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02891 for <dhcwg@ietf.org>; Wed, 23 Apr 2003 15:24:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198Pt0-0006fK-00 for dhcwg@ietf.org; Wed, 23 Apr 2003 15:26:30 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 198Psz-0006fA-00 for dhcwg@ietf.org; Wed, 23 Apr 2003 15:26:29 -0400
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h3NJQNlY017165; Wed, 23 Apr 2003 15:26:24 -0400 (EDT)
Received: from paduffy-w2k.cisco.com (ch2-dhcp150-106.cisco.com [161.44.150.106]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA09426; Wed, 23 Apr 2003 15:26:23 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030423151100.026384e8@funnel.cisco.com>
X-Sender: paduffy@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 23 Apr 2003 15:26:20 -0400
To: Thomas Narten <narten@us.ibm.com>
From: Paul Duffy <paduffy@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-pktc-kerb-tckt-01.txt
Cc: dhcwg@ietf.org
In-Reply-To: <200304221641.h3MGfMl03743@cichlid.adsl.duke.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_105628726==_.ALT"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Thanks Thomas...inline please...

At 12:41 PM 4/22/2003 -0400, Thomas Narten wrote:
>I've gone ahead and asked for the IETF LC to start for this document.
>
>A few small comments:
>
> >        Code   Len      TCM
> >       +-----+-----+-----+-----+
> >       | TBD |  2  | m1  | m2  |
> >       +-----+-----+-----+-----+
>
>It might be better to not have m1/m2, since the text talks about a
>single 16-bit field rather than two smaller fields.

The format is consistent with the formats presented in RFC 3495 (sections 
8.3, 8.4, etc.).  I'm not sure what you are driving at.  Suggestions?

>
> >       The length MUST be 2.  The TCM field is encoded as an unsigned 16
> >       bit quantity per network byte-ordering rules.  Each bit of the TCM
>
>better wording for bit ordering might be:
>
>       The length MUST be 2.  The TCM field is encoded as an unsigned 16
>       bit quantity in network byte order.  Each bit of the TCM

OK...will make that change in next draft.


> >    5.   IANA Considerations
>
>what about future assignments of bit values?

Yes, needs to be added.  How about...

"IANA is requested to maintain a new number space of "CableLabs Client 
Configuration Option Ticket Control Mask Bit Definitions", located in the 
BOOTP-DHCP Parameters Registry.  The initial bit definitions are described 
in section 4 of this document.  IANA is requested to register future bit 
mask definitions via an "IETF Consensus" approval policy as described in 
RFC 2434 [add ref}."


> >       However, the scenario described above is unlikely to occur.
> >       Within the cable delivery architecture required by the various
> >       CableLabs projects, the DHCP client is connected to a network
> >       through a cable modem and the CMTS (head-end). The CMTS is
> >       explicitly configured with a set of DHCP servers to which DHCP
> >       requests are forwarded.  Further, a correctly configured CMTS
> >       will only allow downstream traffic from specific IP
> >       addresses/ranges.
>
>Could be more clear. I don't follow the last sentence, for example.

Last sentence change to...

"Further, the CMTS is explicitly configured to allow downstream traffic 
only from specific IP addresses/ranges."

OK ?

P.S.  Should I hold the next draft until after IESG LC ?


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

--

Paul Duffy
Cisco Systems, Inc.
paduffy@cisco.com