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

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 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

>    5.   IANA Considerations 

what about future assignments of bit values?

>       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.

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