Talk:Recursive Internetwork Architecture

This article sounds very much like something has read John Day's book and coroborated his point of view here...

This is John Day's book and not all of this is good faith. 'The internet ceases to be an internet?' Who agrees with that besides Day and a few groupies? 2605:E000:90C5:A000:1493:686D:69D3:CBD7 (talk) 02:26, 7 April 2016 (UTC)

The comment above does not reflect the state of John's work or the level of acceptance. Day makes no claim to be 'the best' or 'the only', nor does this article. The comment above is highly prejudiced and appears to believe that the correct and proven model of RINA is mere opinion. Comments regarding the applicability and accuracy of a technology should be limited to subject matter experts who are applying correct analysis and correction. As it is the 'suggestion' that protocols or equivalent structures are implementable in RINA leave room for doubt in areas where fact is being and has been demonstrated. As such the accusation of lack of neutrality harms the content dramatically, and presents a false narrative. 2604:3D08:B780:2D0:55B8:97A9:C05B:D5DA (talk) 04:54, 18 June 2020 (UTC)

I'm curious what are your technical arguments to support that the sentence you are referring to is incorrect, maybe it is the use of language since the word "Internet" means many things to different people. In this article "Internet" is used in the context of computer network architecture. The fact that the "Internet layer" is directly on top of the data link layer in the TCP/IP protocol suite makes the current "Internet" a very large IP network. In the current Internet architecture there is no room for network-layer relaying. If you want to do your own non-IP forwarding in your network (or hide your internal network IP routers from the Internet) you have to introduce "patches" in the architecture like "layers 2.5" (MPLS) and all sorts of tunneling (GTP, etc..). RINA provides a simpler and more accurate architectural model for describing real computer networks, which, if implemented, would dramatically minimize the number of protocols and technologies required to run networks.

The number of people agreeing with a statement is not correlated to its correctness. Science is not democracy. — Preceding unsigned comment added by Edugrasa (talk • contribs) 08:54, 23 December 2016 (UTC)

POV marked

Agreed with 2605:E000:90C5:A000:1493:686D:69D3:CBD7. Marked with the POV template until the lack of neutrality is addressed. LodeRunner (talk) 13:01, 18 November 2016 (UTC)

needs rewrite to be neutral

The content is reasonable, but needs to be expressed as one potential framework for understanding network communications rather then presented as the "only and obvious" choice. — Preceding unsigned comment added by TcomptonMA (talk • contribs) 18:01, 21 February 2017 (UTC)

I believe I have enough of a grasp on the content to undertake a rewrite. Thanks in advance for signaling any inaccuracies that may have occurred. Hayazin (talk) 15:23, 6 April 2018 (UTC)

I have toned down the article considerably to present just problems faced in the current internet architecture and what RINA does to solve it. Thanks in advance for leaving an opinion on the content. Hayazin (talk) 09:48, 3 November 2020 (UTC)

I can't follow this

I'm thick, but when reading about any protocol or "layers" it's pretty easy to follow. This article really isn't. Large clumps of paragraphs not really explaining what layer does what. It's a bit of a nightmare to be honest. KenSharp (talk) 12:57, 9 March 2023 (UTC)

The point is that there aren't a fixed number of layers; the introduction states that RINA's principle is that layering should reflect network scope/scale rather than function, and that every scope operates in fundamentally the same way (routing, flow control, authentication), from applications all the way to physical layers like WiFi and Ethernet. Each scope can operate differently for performance (e.g. dummy routing and/or authentication on a point-to-point link), but any given scope's operation does not change how higher scopes use it or how lower scopes themselves operate. I find this is best illustrated in this image. Hayazin (talk) 14:11, 9 March 2023 (UTC)