[icnrg] FW: New Version Notification for draft-rahman-icnrg-deployment-guidelines-05.txt

["Rahman, Akbar" <[e-mail]>]

Hi Dave/ Börje,


We have updated our draft as described below.  Please review and confirm that the draft is ready to go for RG adoption call as per the decision in IETF-100 (Singapore).  Or please tell us if you think that further changes are needed.

Also, we tried to close major comments off-line with the people who gave them, but we would be happy to hear from anyone who felt that more changes are required.

-----------------------------------------------------

   o  Added this Change Log in Appendix A.

   o  Removed references to Hybrid ICN from section 3.2 (ICN-as-an-
      Overlay definition).  Instead, consolidated all Hybrid ICN info in
      the Deployment Trial Experiences under a new subsection 5.3 (Other
      Configurations).

   o  Updated ICN2020 description in Section 5.1.4 with text received
      from Mayutan Arumaithurai and Hitoshi Asaeda.

   o  Clarified in ICN-as-a-Slice description (section 3.4) that it may
      be deployed on either the Edge (RAN) or Core Network, or the ICN-
      as-a-Slice may be deployed end-to-end through the entire Mobile
      network.

   o  Added several new references in various sections.

   o  Various minor editorial updates.

-----------------------------------------------------


Best Regards,

Akbar

-----Original Message-----
From: [e-mail] [mailto:[e-mail]]
Sent: Tuesday, January 16, 2018 12:42 AM
To: Ravi Ravindran <[e-mail]>; Dirk Kutscher <[e-mail]>; Trossen, Dirk <[e-mail]>; Rahman, Akbar <[e-mail]>; Trossen, Dirk <[e-mail]>
Subject: New Version Notification for draft-rahman-icnrg-deployment-guidelines-05.txt


A new version of I-D, draft-rahman-icnrg-deployment-guidelines-05.txt
has been successfully submitted by Akbar Rahman and posted to the IETF repository.

Name:draft-rahman-icnrg-deployment-guidelines
Revision:05
Title:Deployment Considerations for Information-Centric Networking (ICN)
Document date:2018-01-15
Group:Individual Submission
Pages:26
URL:            https://www.ietf.org/internet-drafts/draft-rahman-icnrg-deployment-guidelines-05.txt
Status:         https://datatracker.ietf.org/doc/draft-rahman-icnrg-deployment-guidelines/
Htmlized:       https://tools.ietf.org/html/draft-rahman-icnrg-deployment-guidelines-05
Htmlized:       https://datatracker.ietf.org/doc/html/draft-rahman-icnrg-deployment-guidelines-05
Diff:           https://www.ietf.org/rfcdiff?url2=draft-rahman-icnrg-deployment-guidelines-05

Abstract:
   Information-Centric Networking (ICN) is now reaching technological
   maturity after many years of fundamental research and
   experimentation.  This document provides a number of deployment
   considerations in the interest of helping the ICN community move
   forward to the next step of live deployments.  First, the major
   deployment configurations for ICN are described including the key
   overlay and underlay approaches.  Then proposed deployment migration
   paths are outlined to address major practical issues such as network
   and application migration.  Next, selected ICN trial experiences are
   summarized.  Finally, protocol areas that require further
   standardization are identified to facilitate future interoperable ICN
   deployments.




Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

[Banner]<http://www.interdigital.com>
[Banner]<http://ir.interdigital.com/File/Index?KeyFile=37447876>
This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.