Design Considerations for Name Resolution Service in Information-Centric Networking (ICN)
draft-irtf-icnrg-nrs-requirements-06

Received changes through RFC Editor sync (created alias RFC 9138, changed title to 'Design Considerations for Name Resolution Service in Information-Centric Networking (ICN)', changed abstract to 'This document provides the functionalities and design considerations for a Name Resolution Service (NRS) in Information-Centric Networking (ICN).  The purpose of an NRS in ICN is to translate an object name into some other information such as a locator, another name, etc.  in order to forward the object request.  This document is a product of the Information-Centric Networking Research Group (ICNRG).', changed pages to 17, changed standardization level to Informational, changed state to RFC, added RFC published event at 2021-12-01, changed IRTF state to Published RFC)

(Via drafts-eval@iana.org): IESG/Authors/ISE:

The IANA Functions Operator has reviewed draft-irtf-icnrg-nrs-requirements-06 and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Amanda Baber
IANA Operations Manager

[Ballot comment]
This document is ready for publication. The only question I has is why this document draft-irtf-icnrg-nrsarch-considerations are two different documents?

In section 4, you can probably remove the following sentence given no upper letter MUSTs or SHOULDs are used:
"The key words "MUST", "MAY", and "SHOULD" in this
  section are used consistently with [RFC2119]."

Also in the sentence before you say:
"This section presents the design considerations for NRS in ICN, not
  requirements."
Not sure what that actually means... what's the important difference for you?

[Ballot comment]

I have a nit and a question that doesn't need to be answered:-)

Nit: The intro says "uniquely identified by IP address" but
anycast exists and doesn't match that (and multicast wouldn't
really either.)

Question: I don't understand how an NRS can do access control
in any realistic context. (The reason that doesn't need to be
answered is that I don't think there really is an answer that
works.) That definitely ought not block the document though.

Request for posting confirmation emailed to previous authors: Taewan You , Cedric Westphal , Jungha Hong , Lijun Dong , Yong-Geun Hong , irtf-chair@irtf.org, icnrg-chairs@ietf.org, Borje Ohlman

This and its companion document https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/ passed ICNRG Last call in January, and has the support of the RG to progress toward publication as an Informational RFC. The two documents have had a long gestation period, and the RG debated multiple times the general importance of name resolution services as a distinct set of capabilities for ICN networks, and exactly what the scope of those services ought to be for different ICN architectures, including CCNx and NDN. While there is no strong consensus on that issue, from the last call comments (only a few) and the sidebar discussions, the chairs assess that on balance these documents provide useful background and a valuable discussion of various tradeoffs and approaches to the subject.

We therefore believe these are ready for IRSG Review and hopefully progression toward publication.

Request for posting confirmation emailed to previous authors: Jungha Hong , icnrg-chairs@ietf.org, Lijun Dong , Cedric Westphal , Borje Ohlman , irtf-chair@irtf.org, Yong-Geun Hong , Taewan You

Request for posting confirmation emailed to previous authors: Ved Kafle , Jungha Hong , icnrg-chairs@ietf.org, Lijun Dong , Cedric Westphal , Borje Ohlman , irtf-chair@irtf.org, Yong-Geun Hong , Taewan You

Request for posting confirmation emailed to previous authors: Ved Kafle , Jungha Hong , icnrg-chairs@ietf.org, Cedric Westphal , irtf-chair@irtf.org, Yong-Geun Hong , Taewan You