CableLabs - IETF Standardization Collaboration
RFC 4965

Note: This ballot was opened for revision 03 and is now closed.

(Jari Arkko) (was Discuss, Yes) Yes

(Ross Callon) Yes

(Ron Bonica) No Objection

(Lars Eggert) No Objection

Comment (2007-04-02)
No email
send info
Section 1., paragraph 2:
>    From time to time, individuals involved
>    with CableLabs focus teams submit CableLabs technical requirements or
>    requirement specifications to IETF in order to seek expert reviews
>    and solicit comments to create solutions that foster product
>    interoperability beyond cable.  The submissions related to CableLabs
>    specifications may for example include use cases, protocol
>    requirements, draft MIB modules, and proposed solutions for comments
>    such as new DHCP options.

  First sentence talks about "requirements" and "requirements
  specifications", but the examples include MIB modules and DHCP
  options, which aren't requirements. (Also, I can't parse "proposed
  solutions for comments".)

(Sam Hartman) No Objection

(Russ Housley) No Objection

(Cullen Jennings) (was Discuss, No Objection) No Objection

Comment (2007-04-05)
No email
send info
I'm still confused about what URL should be in in a reference to a cable labs documents.

(Chris Newman) No Objection

Comment (2007-04-05)
No email
send info
Agree with concern about stable URLs to specific versions of cablelabs specifications.  The model W3C uses works well.

(Tim Polk) No Objection

Magnus Westerlund No Objection

(Mark Townsley) Recuse