CableLabs - IETF Standardization Collaboration
draft-mule-ietf-cablelabs-collaboration-03

[Ballot discuss]
2) I might be finding the IANA URL reference advice confusing. I'm not OK with normative references to non stable specifications - the URL that don't have the archives segment look like they are not stable references. However, should we have a URL at all or just something like PKT-SP-EM-I11-040723. It also seems like the documents aren't at the described URLs. For example, PKT-SP-CODEC-MEDIA-I02-061013, seems to be at http://www.packetcable.com/downloads/specs/PKT-SP-CODEC-MEDIA-I02-061013.pdf

[Ballot discuss]
1) I see we sent this to the IAB - did we ever hear back?

2) I might be finding the IANA URL reference advice confusing. I'm not OK with normative references to non stable specifications - the URL that don't have the archives segment look like they are not stable references. However, should we have a URL at all or just something like PKT-SP-EM-I11-040723. It also seems like the documents aren't at the described URLs. For example, PKT-SP-CODEC-MEDIA-I02-061013, seems to be at http://www.packetcable.com/downloads/specs/PKT-SP-CODEC-MEDIA-I02-061013.pdf

[Ballot comment]
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".)

IANA Last Call Comments;

---
IANA has questions.

I think this is the basic set of questions to ask:
1. Are there CableLabs values that are not documented
in RFC's that IANA should keep track of? Or does this
document only apply to future  registrations.

2. Will Cablelab proive a "Stable" reference to their
documents, independant of their location ?

3. If registries are created for Cablelab purposes with
liberal allocation policy (FCFS, or expert review), can
IANA assume making these assignments is harmless from
CableLabs perspective?
The isssue here is a document may appear on Standards
track that request a specific value in a registry. This
value has been assigned to for a different purpose.
IANA SOP is to assign a different unique value to the
second request.

We should also state the basic rules of the road,
from IANA perspective.

1. IANA registers what it is provided documentation on.

2. Future registrations in i-d's SHOULD contain "stable"
reference to the  cablelabs document and IANA can expect
the IANA considerations sections or sections highlighed
in IANA considerations section point to the  cablelabs
document that needs to be referenced.

3. IANA is NOT responsible for finding/registering values
in Cablelabs documents that are not epxlicitly submitted
to IANA.

----


This section provides some guidelines for IANA to
consider when adding references to a CableLabs
specification in its registries.

CableLabs maintains current and archived specification
repositories. When a specification is updated, a copy
of the previous version is moved to the archived
repository to provide a stable reference.

IANA should add a pointer to both the current and
archive specification repositories when referencing
a CableLabs specification, for example:

o For a DOCSIS or cable modem related specification,
consider adding a reference to both

http://www.cablemodem.com/specifications/ and
http://www.cablelabs.com/specifications/archives/ ;

o For a PacketCable specification, consider adding
a reference to both

http://www.packetcable.com/specifications/ and
http://www.cablelabs.com/specifications/archives/

IANA Last Call Comments;

---
IANA has questions.

I think this is the basic set of questions to ask:
1. Are there CableLabs values that are not documented
in RFC's that IANA should keep track of? Or does this
document only apply to future  registrations.

2. Will Cablelab proive a "Stable" reference to their
documents, independant of their location ?

3. If registries are created for Cablelab purposes with
liberal allocation policy (FCFS, or expert review), can
IANA assume making these assignments is harmless from
CableLabs perspective?
The isssue here is a document may appear on Standards
track that request a specific value in a registry. This
value has been assigned to for a different purpose.
IANA SOP is to assign a different unique value to the
second request.

We should also state the basic rules of the road,
from IANA perspective.

1. IANA registers what it is provided documentation on.

2. Future registrations in i-d's SHOULD contain "stable"
reference to the  cablelabs document and IANA can expect
the IANA considerations sections or sections highlighed
in IANA considerations section point to the  cablelabs
document that needs to be referenced.

3. IANA is NOT responsible for finding/registering values
in Cablelabs documents that are not epxlicitly submitted
to IANA.

----


This section provides some guidelines for IANA to
consider when adding references to a CableLabs
specification in its registries.

CableLabs maintains current and archived specification
repositories. When a specification is updated, a copy
of the previous version is moved to the archived
repository to provide a stable reference.

IANA should add a pointer to both the current and
archive specification repositories when referencing
a CableLabs specification, for example:

o For a DOCSIS or cable modem related specification,
consider adding a reference to both

http://www.cablemodem.com/specifications/ and
http://www.cablelabs.com/specifications/archives/ ;

o For a PacketCable specification, consider adding
a reference to both

http://www.packetcable.com/specifications/ and
http://www.cablelabs.com/specifications/archives/