Skip to main content

CCNinfo: Discovering Content and Network Information in Content-Centric Networks
draft-irtf-icnrg-ccninfo-15

Revision differences

Document history

Date Rev. By Action
2023-02-13
15 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2023-01-23
15 (System) RFC Editor state changed to AUTH48
2022-12-28
15 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-15.txt
2022-12-28
15 (System) New version approved
2022-12-28
15 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-12-28
15 Hitoshi Asaeda Uploaded new revision
2022-12-28
14 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-14.txt
2022-12-28
14 (System) New version approved
2022-12-28
14 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-12-28
14 Hitoshi Asaeda Uploaded new revision
2022-12-21
13 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2022-10-14
13 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2022-10-14
13 (System) IANA Action state changed to Waiting on RFC Editor from In Progress
2022-10-14
13 (System) IANA Action state changed to In Progress from Waiting on Authors
2022-10-13
13 (System) IANA Action state changed to Waiting on Authors from In Progress
2022-10-07
13 (System) RFC Editor state changed to EDIT
2022-10-07
13 (System) IANA Action state changed to In Progress
2022-10-07
13 Colin Perkins IRTF state changed to Sent to the RFC Editor from In IESG Review
2022-10-07
13 Colin Perkins Sent request for publication to the RFC Editor
2022-10-05
13 (System) Revised ID Needed tag cleared
2022-10-05
13 (System) IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed
2022-10-05
13 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-13.txt
2022-10-05
13 (System) New version approved
2022-10-05
13 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-10-05
13 Hitoshi Asaeda Uploaded new revision
2022-10-02
12 Colin Perkins IESG Review completed, with comments to consider from Erik Kline.
2022-10-02
12 Colin Perkins Tags IESG Review Completed, Revised I-D Needed set.
2022-10-02
12 Colin Perkins IRTF state changed to In IESG Review from Waiting for IRTF Chair
2022-09-12
12 Erik Kline
# Internet AD comments for {draft-irtf-icnrg-ccninfo-12}
CC @ekline

## Comments

### S1.1

* "PIT" acronym/initialism is used without prior expansion? (probably not
  …
# Internet AD comments for {draft-irtf-icnrg-ccninfo-12}
CC @ekline

## Comments

### S1.1

* "PIT" acronym/initialism is used without prior expansion? (probably not
  required for CCN-knowledgeable folks but might still be helpful)

### S3.1.1

* Consider whether you want to include a reference to RFC 8877 and describe
  this timestamp format's relationship to any text that appears in there.

### S3.2.1.1

* "total size (KB) of the unexpired content objects"

  In which direction should rounding occur, or are all content objects
  1KB-aligned?

### S5.2

* For list item #1: does the router decrement the hoplimit and then compare
  to zero, or compare to zero first and then decrement before forwarding?

* Also for list item #1: I was confused by the description of FHR behaviour
  for non-zero hoplimit values.  The text implied to me that the FHR drops
  the request unless the hoplimit == 0 exactly, which to me seems like it
  only prolongs the time it takes to run a diagnostic info request (because
  the ccninfo has to walk hoplimits upwards until it gets the exact right
  value rather than setting a suitably large guess and having the FHR
  handle it regardless of hoplimit value).

  But I'm probably just misreading the text or simply confused.

### S5.5

* If a HopLimit is decremented to zero for a reply message, does an error
  get sent back to the replying router or is it silently dropped?

  I assume silently dropped.

## Nits

### S1.1

* "it examines own cache" -> "it examines its own cache", perhaps

### S3.2.1.1

* "value of one (i.e., %xFFFFFFFF)" ->
  "value of all ones (i.e., %xFFFFFFFF)", perhaps

### S5.6

* "To avoid routing loop" -> "To avoid routing loops", I think
2022-09-02
12 Amanda Baber IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed
2022-09-01
12 (System) IANA Review state changed to Version Changed - Review Needed from IANA - Not OK
2022-09-01
12 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-12.txt
2022-09-01
12 (System) New version approved
2022-09-01
12 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-09-01
12 Hitoshi Asaeda Uploaded new revision
2022-08-31
11 (System) IANA Review state changed to IANA - Not OK
2022-08-31
11 Amanda Baber
(Via drafts-eval@iana.org): IESG/Authors/ISE:

IANA has questions about draft-irtf-icnrg-ccninfo-11.

The IANA Considerations section is unclear, but it seems to indicate that the document can't make …
(Via drafts-eval@iana.org): IESG/Authors/ISE:

IANA has questions about draft-irtf-icnrg-ccninfo-11.

The IANA Considerations section is unclear, but it seems to indicate that the document can't make registrations because the unnamed registry requires Standards Action (RFC 8126).

However, the registries that the document appears to refer to require only RFC publication ("RFC Required") or a document approved by an expert ("Specification Required"):

https://www.iana.org/assignments/ccnx

For example, "Figure 4: Packet Type Namespace" lists three registrations made in the CCNx Packet Types registry by RFC 8609:

%x00        PT_INTEREST
%x01        PT_CONTENT
%x02        PT_RETURN

It then lists two more entries that aren't listed in the CCNx Packet Types registry yet:

%x03        PT_CCNINFO_REQUEST
%x04        PT_CCNINFO_REPLY

The IANA Considerations section doesn't ask us to register those Packet Types, but it could: the registration procedure is "RFC Required," which requires only that this document be published as an RFC.

This is also true for the unregistered entries in the lists in Figure 5 (CCNx Top-Level Types), Figure 8 (CCNx Hop-by-Hop Types), Figure 11 (CCNx Message Types), and possibly others. Why aren't these being registered by this document? Are these meant to be registered by a different document?

Should there be a new registry for the list in Section 3.1? Also, Figure 16 refers to a "CCNinfo Reply Type Namespace," which doesn't appear to exist yet. Should that be created by this document?

(This may not be an exhaustive list of possible registries and registrations.)

If this document is making registrations, each registry and set of new registrations should be listed in the IANA Considerations section. If the document is creating registries, a registration procedure must also be provided (see RFC 8126).
2022-08-31
11 Colin Perkins IETF conflict review initiated - see conflict-review-irtf-icnrg-ccninfo
2022-08-31
11 Colin Perkins IRSG Final Poll concluded. Has enough Yes positions to progress.
2022-08-31
11 Colin Perkins IRTF state changed to Waiting for IRTF Chair from In IRSG Poll
2022-08-31
11 Colin Perkins Closed "IRSG Approve" ballot
2022-08-30
11 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-11.txt
2022-08-30
11 (System) New version approved
2022-08-30
11 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao , icnrg-chairs@ietf.org, irtf-chair@irtf.org
2022-08-30
11 Hitoshi Asaeda Uploaded new revision
2022-08-30
10 Brian Trammell [Ballot Position Update] New position, No Objection, has been recorded for Brian Trammell
2022-08-30
10 Marie-Jose Montpetit
[Ballot comment]
I think it's ready and in fact will be very useful for not only for it's intended audience but for people trying to …
[Ballot comment]
I think it's ready and in fact will be very useful for not only for it's intended audience but for people trying to understand how CCN works.
2022-08-30
10 Marie-Jose Montpetit [Ballot Position Update] Position for Marie-Jose Montpetit has been changed to Yes from No Objection
2022-08-29
10 Allison Mankin
[Ballot comment]
This is a very clear document. I'd want more solutions for the privacy risks (clearly described) if it were from a WG but …
[Ballot comment]
This is a very clear document. I'd want more solutions for the privacy risks (clearly described) if it were from a WG but from an RG it's ready for publication IMO.
2022-08-29
10 Allison Mankin [Ballot Position Update] New position, Yes, has been recorded for Allison Mankin
2022-08-29
10 Jane Coffin [Ballot Position Update] New position, No Objection, has been recorded for Jane Coffin
2022-06-28
10 Vincent Roca
[Ballot comment]
I gave a quick look at the Security Considerations section that seems of good quality. Given that this tool opens the door to …
[Ballot comment]
I gave a quick look at the Security Considerations section that seems of good quality. Given that this tool opens the door to a large set of new security and privacy risks, this is clearly required. I hope the SecDir review will go through all of this more carefully than I did.
2022-06-28
10 Vincent Roca [Ballot Position Update] New position, No Objection, has been recorded for Vincent Roca
2022-06-27
10 Jérôme François [Ballot Position Update] Position for Jérôme François has been changed to Yes from No Objection
2022-06-27
10 Jérôme François [Ballot Position Update] New position, No Objection, has been recorded for Jérôme François
2022-06-27
10 Mat Ford [Ballot Position Update] New position, No Objection, has been recorded for Mat Ford
2022-06-23
10 David Oran [Ballot Position Update] Position for David Oran has been changed to Recuse from Yes
2022-06-23
10 Marie-Jose Montpetit [Ballot Position Update] New position, No Objection, has been recorded for Marie-Jose Montpetit
2022-06-09
10 Dirk Kutscher [Ballot Position Update] New position, Yes, has been recorded for Dirk Kutscher
2022-06-07
10 David Oran [Ballot Position Update] New position, Yes, has been recorded for David Oran
2022-06-06
10 Colin Perkins [Ballot Position Update] New position, No Objection, has been recorded for Colin Perkins
2022-06-06
10 Colin Perkins IRTF state changed to In IRSG Poll from IRSG Review
2022-06-06
10 Colin Perkins Created IRSG Ballot
2022-04-25
10 (System) Revised ID Needed tag cleared
2022-04-25
10 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-10.txt
2022-04-25
10 (System) New version approved
2022-04-25
10 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-04-25
10 Hitoshi Asaeda Uploaded new revision
2022-04-08
09 Colin Perkins Jérôme François reviewed -09 for the IRSG. Revised draft needed.
2022-04-08
09 Colin Perkins Tag Revised I-D Needed set.
2022-04-08
09 Colin Perkins IRTF state changed to IRSG Review from Awaiting IRSG Reviews
2022-02-10
09 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-09.txt
2022-02-10
09 (System) New version approved
2022-02-10
09 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2022-02-10
09 Hitoshi Asaeda Uploaded new revision
2022-01-28
08 (System) Document has expired
2022-01-25
08 Colin Perkins IRTF state changed to Awaiting IRSG Reviews from Waiting for IRTF Chair
2022-01-25
08 Colin Perkins Changed consensus to Yes from Unknown
2021-12-10
08 David Oran
CCNInfo is one of a suite of tools for the instrumentation and management of ICN networks. it has gone through significant evolution over a number …
CCNInfo is one of a suite of tools for the instrumentation and management of ICN networks. it has gone through significant evolution over a number of years, and is deemed ready by the RG participants and chairs as ready for IRSG review and publication as an experimental RFC.

During Last Call, only a few comments were received. These were focused on:
- correctly positioning the work as one of a set of tools (as opposed to the "one and only blessed tool")
- including material describing the nature of the experiments with ICN that such a tool as CCNInfo can support.

Material addressing these is included in the current draft.

As a note, two additional ICN management tools, Ping and Traceroute, are under active development in ICNRG as will be entering Last Call in the near future.


2021-12-10
08 David Oran Notification list changed to daveoran@orandom.net because the document shepherd was set
2021-12-10
08 David Oran Document shepherd changed to David R. Oran
2021-12-10
08 David Oran Last cal completed and new version produced based on (limited) comments. This should go for IRSG Review as soon as IRTF chair deems appropriate.
2021-12-10
08 David Oran IRTF state changed to Waiting for IRTF Chair from Active RG Document
2021-07-27
08 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-08.txt
2021-07-27
08 (System) New version approved
2021-07-27
08 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2021-07-27
08 Hitoshi Asaeda Uploaded new revision
2021-07-12
07 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-07.txt
2021-07-12
07 (System) New version approved
2021-07-12
07 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2021-07-12
07 Hitoshi Asaeda Uploaded new revision
2021-03-10
06 David Oran Added to session: IETF-110: icnrg  Wed-1300
2021-03-09
06 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-06.txt
2021-03-09
06 (System) New version approved
2021-03-09
06 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Hitoshi Asaeda , Xun Shao
2021-03-09
06 Hitoshi Asaeda Uploaded new revision
2020-09-21
05 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-05.txt
2020-09-21
05 (System) New version approved
2020-09-21
05 (System) Request for posting confirmation emailed to previous authors: Hitoshi Asaeda , Xun Shao , Atsushi Ooka
2020-09-21
05 Hitoshi Asaeda Uploaded new revision
2020-03-22
04 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-04.txt
2020-03-22
04 (System) New version approved
2020-03-22
04 (System) Request for posting confirmation emailed to previous authors: Atsushi Ooka , Xun Shao , Hitoshi Asaeda
2020-03-22
04 Hitoshi Asaeda Uploaded new revision
2020-03-09
03 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-03.txt
2020-03-09
03 (System) New version approved
2020-03-09
03 (System) Request for posting confirmation emailed to previous authors: Xun Shao , Hitoshi Asaeda , Atsushi Ooka
2020-03-09
03 Hitoshi Asaeda Uploaded new revision
2020-01-09
02 (System) Document has expired
2019-07-08
02 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-02.txt
2019-07-08
02 (System) New version approved
2019-07-08
02 (System) Request for posting confirmation emailed to previous authors: Xun Shao , Atsushi Ooka , Hitoshi Asaeda
2019-07-08
02 Hitoshi Asaeda Uploaded new revision
2019-03-23
01 David Oran Added to session: interim-2019-icnrg-02
2019-03-11
01 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-01.txt
2019-03-11
01 (System) New version approved
2019-03-11
01 (System) Request for posting confirmation emailed to previous authors: Xun Shao , irtf-chair@irtf.org, Hitoshi Asaeda , icnrg-chairs@ietf.org
2019-03-11
01 Hitoshi Asaeda Uploaded new revision
2018-11-06
00 David Oran Added to session: IETF-103: icnrg  Thu-0900
2018-10-08
00 David Oran IRTF state changed to Active RG Document
2018-10-08
00 David Oran Intended Status changed to Experimental from None
2018-10-08
00 David Oran Reissued as RG document
2018-10-08
00 David Oran This document now replaces draft-asaeda-icnrg-ccninfo instead of None
2018-10-08
00 Hitoshi Asaeda New version available: draft-irtf-icnrg-ccninfo-00.txt
2018-10-08
00 (System) WG -00 approved
2018-10-07
00 Hitoshi Asaeda Set submitter to "Hitoshi Asaeda ", replaces to (none) and sent approval email to group chairs: icnrg-chairs@ietf.org
2018-10-07
00 Hitoshi Asaeda Uploaded new revision