| Internet-Draft | RAW Use-Case Scenarios | October 2022 |
| Bernardos, et al. | Expires 25 April 2023 | [Page] |
The wireless medium presents significant specific challenges to achieveproperties similar to those of wired deterministic networks. At the same time, anumber of use-cases cannot be solved with wires and justify the extra effort ofgoing wireless. This document presents wireless use-cases (such as aeronauticalcommunications, amusement parks, industrial applications, pro audio and video,gaming, UAV and V2V control, edge robotics and emergency vehicles) demandingreliable and available behavior.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is athttps://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 25 April 2023.¶
Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Based on time, resource reservation, and policy enforcement by distributedshapers, Deterministic Networking provides the capability to carry specifiedunicast or multicast data streams for real-time applications with extremely lowdata loss rates and bounded latency, to support time-sensitive andmission-critical applications on a converged enterprise infrastructure.¶
Deterministic Networking in the IP world is an attempt to eliminate packet lossfor a committed bandwidth while ensuring a worst case end-to-end latency,regardless of the network conditions and across technologies. By leveraginglower layer (Layer 2 and below) capabilities, L3 can exploit the use of a service layer,steering over multiple technologies, and using media independent signaling toprovide high reliability, precise time delivery, and rate enforcement.Deterministic networking can be seen as a set of new Quality of Service (QoS)guarantees of worst-case delivery. IP networks become more deterministic whenthe effects of statistical multiplexing (jitter and collision loss) are mostlyeliminated. This requires a tight control of the physical resources to maintainthe amount of traffic within the physical capabilities of the underlyingtechnology, e.g., using time-shared resources (bandwidth and buffers)per circuit, and/or by shaping and/or scheduling the packets at every hop.¶
Key attributes of Deterministic Networking include:¶
Wireless operates on a shared medium, and transmissions cannot be guaranteed tobe fully deterministic due to uncontrolled interferences, including self-inducedmultipath fading. Reliable and Available Wireless (RAW) is an effort to provideDeterministic Networking Mechanisms on a multi-hop path that includes awireless physical layer. Making Wireless Reliable and Available is even morechallenging than it is with wires, due to the numerous causes of loss intransmission that add up to the congestion losses and the delays caused byoverbooked shared resources.¶
The wireless and wired media are fundamentally different at the physical level,and while the generic Problem Statement[RFC8557] for DetNetapplies to the wired as well as the wireless medium, the methods to achieve RAWnecessarily differ from those used to support Time-Sensitive Networking overwires, e.g., due to the wireless radio channel specifics.¶
So far, Open Standards for Deterministic Networking have prevalently beenfocused on wired media, with Audio/Video Bridging (AVB) and Time SensitiveNetworking (TSN) at the IEEE and DetNet[RFC8655] at the IETF. But wires cannot be used inseveral cases, including mobile or rotating devices, rehabilitatedindustrial buildings, wearable or in-body sensory devices, vehicle automationand multiplayer gaming.¶
Purpose-built wireless technologies such as[ISA100], whichincorporates IPv6, were developed and deployed to cope with the lack of openstandards, but they yield a high cost in OPEX and CAPEX and are limited tovery few industries, e.g., process control, concert instruments or racing.¶
This is now changing[I-D.ietf-raw-technologies]:¶
Experiments have already been conducted with IEEE802.1 TSN over IEEE802.11be[IEEE80211BE].This mode enables time synchronization, and time-aware scheduling(trigger based access mode) to support TSN flows.¶
This document extends the "Deterministic Networking use-cases" document[RFC8578] and describes several additional use-cases which require"reliable/predictable and available" flows over wireless links and possiblycomplex multi-hop paths called Tracks. This is covered mainly by the "Wirelessfor Industrial Applications" use-case, as the "Cellular Radio" is mostlydedicated to the (wired) link part of a Radio Access Network (RAN). Whereasthe "Wireless for Industrial Applications" use-case certainly covers an area ofinterest for RAW, it is limited to 6TiSCH, and thus its scope is narrower thanthe use-cases described next in this document.¶
Aircraft are currently connected to ATC (Air-Traffic Control) and AOC (AirlineOperational Control) via voice and data communication systems through allphases of a flight. Within the airport terminal, connectivity is focused on highbandwidth communications while en-route high reliability, robustness andrange are the focus.¶
Up to 2020, civil air traffic has been growing constantly at a compound rate of5.8% per year[ACI19] and despite the severe impact of theCOVID-19 pandemic, air traffic growth is expected to resume very quickly inpost-pandemic times[IAT20][IAC20]. Thus, legacysystems in air traffic management (ATM) are likely to reach their capacitylimits and the need for new aeronautical communication technologies becomesapparent. Especially problematic is the saturation of VHF band in high densityareas in Europe, the US, and Asia[KEAV20][FAA20]calling for suitable new digital approaches such as AeroMACS for airportcommunications, SatCOM for remote domains, and LDACS as long-range terrestrialaeronautical communication system. Making the frequency spectrum's usage moreefficient a transition from analog voice to digital data communication[PLA14] is necessary to cope with the expected growth of civil aviationand its supporting infrastructure. A promising candidate for long rangeterrestrial communications, already in the process of being standardized in theInternational Civil Aviation Organization (ICAO), is the L-band DigitalAeronautical Communication System (LDACS)[ICAO18][I-D.ietf-raw-ldacs].¶
During the creation process of new communication system, analog voice isreplaced by digital data communication. This sets a paradigm shift from analogto digital wireless communications and supports the related trend towardsincreased autonomous data processing that the Future CommunicationsInfrastructure (FCI) in civil aviation must provide. The FCI is depicted inFigure 1:¶
Satellite# ## # ## # ## # ## # ## # ## # ## Satellite-based # ## Communications # ## SatCOM (#) # ## # Aircraft# # % %# # % %# # % Air-Air %# # % Communications %# # % LDACS A/A (%) %# # % %# Aircraft % % % % % % % % % % Aircraft# | Air-Ground |# | Communications |# | LDACS A/G (|) |# Communications in | |# and around airports | |# AeroMACS (-) | |# | |# Aircraft-------------+ | |# | | |# | | |# Ground network | | Ground network |SatCOM <---------------------> Airport <----------------------> LDACSground ground groundtransceiver transceiver transceiver
This paradigm change brings a lot of new challenges:¶
In a high mobility environment such as aviation, the envisioned solutions toprovide worldwide coverage of data connections with in-flight aircraft require amulti-system, multi-link, multi-hop approach. Thus air, ground and space-baseddatalink providing technologies will have to operate seamlessly together to copewith the increasing needs of data exchange between aircraft, air trafficcontroller, airport infrastructure, airlines, air network service providers(ANSPs) and so forth. Thus, making use of wireless technologies is a must intackling this enormous need for a worldwide digital aeronautical datalinkinfrastructure.¶
Different safety levels need to be supported, from extremely safety criticalones requiring low latency, such as a WAKE warning - a warning that two aircraftcome dangerously close to each other - and high resiliency, to less safetycritical ones requiring low-medium latency for services such as WXGRAPH -graphical weather data.¶
Overhead needs to be kept at a minimum since aeronautical data links providecomparatively small data rates on the order of kbit/s.¶
Policy needs to be supported when selecting data links. The focus of RAW hereshould be on the selectors, responsible for the track a packet takes toreach its end destination. This would minimize the amount of routing informationthat must travel inside the network because of precomputed routing tables withthe selector being responsible for choosing the most appropriate optionaccording to policy and safety.¶
Achieving low latency is a requirement for aeronautics communications, thoughthe expected latency is not extremely low and what is important is to keepthe overall latency bounded under a certain threshold. This use-case is notlatency-critical from that view point. On the other hand, given the controlledenvironment, end-to-end mechanisms can be applied to guarantee bounded latencywhere needed.¶
The digitalization of Amusement Parks is expected to decrease significantly thecost for maintaining the attractions. Such deployment is a mix betweenindustrial automation (i.e., Smart Factories) and multimedia entertainmentapplications.¶
Attractions may rely on a large set of sensors and actuators, which react inreal time. Typical applications comprise:¶
Amusement parks comprise a variable number of attractions, mostly outdoor, overa large geographical area. The IT infrastructure is typically multi-scale:¶
Amusement parks cover large areas, and a global interconnection would require ahuge length of cables. Wireless also increases the reconfigurability, enablingto update an attraction at a lower cost. The frequent renewal helps to increasethe customer loyalty.¶
Some parts of the attraction are mobile, like trucks of a roller-coaster orrobots. Since cables are prone to frequent failures in this situation, wirelesstransmissions are recommended.¶
Wearable devices are extensively used for a user experience personalization.They typically need to support wireless transmissions. Personal tags may help toreduce the operating costs[DISNEY15] and to increase the numberof charged services provided to the audience (e.g., VIP tickets orinteractivity). Some applications rely on more sophisticated wearable devicessuch as digital glasses or Virtual Reality (VR) headsets for an immersiveexperience.¶
The network infrastructure must support heterogeneous traffic, with verydifferent critical requirements. Thus, flow isolation must be provided.¶
The transmissions must be scheduled appropriately even in presence of mobiledevices. While the[RFC9030] already proposes an architecture forsynchronized, IEEE Std. 802.15.4 Time-Slotted Channel Hopping (TSCH) networks,the industry requires a multi-technology solution, able to guarantee end-to-endrequirements across heterogeneous technologies, with strict SLA requirements.¶
Nowadays, long-range wireless transmissions are used mostly for best-efforttraffic. On the contrary,[IEEE802.1TSN] is used for criticalflows using Ethernet devices. However, IP enabled technology is required tointerconnect large areas, independent of the PHY and MAC layers.¶
It is expected that several different technologies (long vs. short range) aredeployed, which have to cohabit in the same area. Thus, we need to providelayer-3 mechanisms able to exploit multiple co-interfering technologies (i.e., different radio technologies using overlapping spectrum, and therefore, potentially interfering to each other).¶
While some of the applications in this use-case involve control loops (e.g.,sensors and actuators) that require bounded latencies below 10 ms, that cantherefore be considered latency critical, there are other applications as wellthat mostly demand reliability (e.g., safety related, or maintenance).¶
A major use-case for networking in Industrial environments is the controlnetworks where periodic control loops operate between a collection of sensorsthat measure a physical property such as the temperature of a fluid, aProgrammable Logic Controller (PLC) that decides an action such as warm up themix, and actuators that perform the required action, such as the injection ofpower in a resistor.¶
Process Control designates continuous processing operations, like heating oilin a refinery or mixing drinking soda. Control loops in the Process Controlindustry operate at a very low rate, typically four times per second. FactoryAutomation, on the other hand, deals with discrete goods such as individualautomobile parts, and requires faster loops, on the order of milliseconds.Motion control that monitors dynamic activities may require even faster rates onthe order of and below the millisecond. Finally, some industries exhibit hybridbehaviors, like canned soup that will start as a process industry while mixingthe food and then operate as a discrete manufacturing when putting the finalproduct in cans and shipping them.¶
In all those cases, a packet must flow reliably between the sensor and the PLC,be processed by the PLC, and sent to the actuator within the control loopperiod. In some particular use-cases that inherit from analog operations, jittermight also alter the operation of the control loop. A rare packet loss isusually admissible, but typically 4 losses in a row will cause an emergency haltof the production and incur a high cost for the manufacturer.¶
Additional details and use-cases related to Industrial applications and theirRAW requirements can be found in[I-D.ietf-raw-industrial-requirements].¶
A secondary use-case deals with monitoring and diagnostics. This data is essential to improve the performance of a production line,e.g., by optimizing real-time processing or maintenance windows using MachineLearning predictions. For the lack of wireless technologies, some specificindustries such as Oil and Gas have been using serial cables, literally by themillions, to perform their process optimization over the previous decades. Butfew industries would afford the associated cost and the Holy Grail of theIndustrial Internet of Things is to provide the same benefits to all industries,including SmartGrid, Transportation, Building, Commercial and Medical. Thisrequires a cheap, available and scalable IP-based access technology.¶
Inside the factory, wires may already be available to operate the ControlNetwork. But monitoring and diagnostics data are not welcome in that network for severalreasons. On the one hand it is rich and asynchronous, meaning that it mayinfluence the deterministic nature of the control operations and impact theproduction. On the other hand, this information must be reported to the carpetedfloor over IP, which means the potential for a security breach via theinterconnection of the Operational Technology (OT) network with the Internettechnology (IT) network and possibly enable a rogue access.¶
Ethernet cables used on a robot arm are prone to breakage after a few thousandsof flexions, a lot faster than a power cable that is wider in diameter, and moreresilient. In general, wired networking and mobile parts are not a good match,mostly in the case of fast and recurrent activities, as well as rotation.¶
When refurbishing older premises that were built before the Internet age, poweris usually available everywhere, but data is not. It is often impractical, timeconsuming and expensive to deploy an Ethernet fabric across walls and betweenbuildings. Deploying a wire may take months and cost tens of thousands of USDollars.¶
Even when wiring exists, like in the case of an existing control network,asynchronous IP packets such as diagnostics may not be welcome for operationaland security reasons. For those packets, the option to create a parallelwireless network offers a credible solution that can scale with the many sensorsand actuators that equip every robot, every valve and fan that are deployed onthe factory floor. It may also help detect and prevent a failure that couldimpact the production, like the degradation (vibration) of a cooling fan on theceiling. IEEE Std. 802.15.4 Time-Slotted Channel Hopping (TSCH)[RFC7554] is a promising technology for that purpose, mostly if thescheduled operations enable to use the same network by asynchronous anddeterministic flows in parallel.¶
As stated by the"Deterministic Networking ProblemStatement" [RFC8557], a Deterministic Network is backwards compatible with(capable of transporting) statistically multiplexed traffic while preserving theproperties of the accepted deterministic flows. While the6TiSCH Architecture [RFC9030] serves that requirement, the work at6TiSCH was focused on best-effort IPv6 packet flows. RAW should be able to lockso-called hard cells (i.e., scheduled cells[I-D.ietf-6tisch-terminology]) for use by a centralized scheduler, andleverage time and spatial diversity over a graph of end-to-end paths called aTrack that is based on those cells.¶
Over the course of the recent years, major Industrial Protocols (e.g.,[ODVA] with EtherNet/IP[EIP] and[PROFINET]) have been migrating towards Ethernet and IP. In order tounleash the full power of the IP hourglass model, it should be possible todeploy any application over any network that has the physical capacity totransport the industrial flow, regardless of the MAC/PHY technology, wired orwireless, and across technologies. RAW mechanisms should be able to setup aTrack over a wireless access segment and a wired or wireless backbone to reportboth sensor data and critical monitoring within a bounded latency and maintainthe high reliability of the flows over time. It is also important to ensure thatRAW solutions are interoperable with existing wireless solutions in place, andwith legacy equipment whose capabilities can be extended using retrofitting.Maintainability, as a broader concept than reliability is also important inindustrial scenarios[MAR19].¶
Monitoring and diagnostics applications do not require latency criticalcommunications, but demand reliable and scalable communications. On the otherhand, process control applications involve control loops that require a boundedlatency, thus are latency critical, but can be managed end-to-end, and thereforeDetNet mechanisms can be applied in conjunction with RAW mechanisms.¶
Many devices support audio and video streaming by employing 802.11 wireless LAN.Some of these applications require low latency capability. For instance, whenthe application provides interactive play, or when the audio plays in realtime - meaning live for public addresses in train stations or in theme parks.¶
The professional audio and video industry ("ProAV") includes:¶
Considering the uninterrupted audio or video stream, a potential packet lossduring the transmission of audio or video flows cannot be tackled by re-tryingthe transmission, as it is done with file transfer, because by the time thepacket lost has been identified it is too late to proceed with packetre-transmission. Buffering might be employed to provide a certain delay whichwill allow for one or more re-transmissions, however such approach is notviable in application where delays are not acceptable.¶
In the context of ProAV over packet networks, latency is the time between the transmitted signal over a stream and its reception. Thus, for sound to remain synchronized to the movement in the video, the latency of both the audio and video streams must be bounded and consistent.¶
The devices need the wireless communication to support video streaming via IEEE802.11 wireless LAN for instance. Wireless communications provide hugeadvantages in terms of simpler deployments in many scenarios, where the use of awired alternative would not be feasible. Similarly, in live events, mobilitysupport makes wireless communications the only viable approach.¶
Deployed announcement speakers, for instancealong the platforms of the train stations, need the wireless communication toforward the audio traffic in real time.¶
The network infrastructure needs to support heterogeneous types of traffic(including QoS).¶
Content delivery with bounded (lowest possible) latency.¶
The deployed network topology should allow for multipath. This will enable formultiple streams to have different (and multiple) paths (tracks) through thenetwork to support redundancy.¶
For synchronized streaming, latency must be bounded, and therefore, depending onthe actual requirements, this can be considered as latency critical. However,the most critical requirement of this use-case is reliability, by the networkproviding redundancy. Note that in many cases, wireless is only present in theaccess, where RAW mechanisms could be applied, but other wired segments are alsoinvolved (like the Internet), and therefore latency cannot be guaranteed.¶
The gaming industry includes[IEEE80211RTA] real-time mobilegaming, wireless console gaming and cloud gaming. For RAW, wireless consolegaming is the most relevant one. We next summarize the three:¶
While a lot of details can be found on[IEEE80211RTA], we nextsummarize the main requirements in terms of latency, jitter and packet loss:¶
Gaming is evolving towards wireless, as players demand beingable to play anywhere, and the game requires a more immersive experienceincluding body movements. Besides, the industry is changing towards playing frommobile phones, which are inherently connected via wireless technologies.Wireless controllers are the rule in modern gaming, with increasingly sophisticatedinteractions (e.g., haptic feedback, augmented reality).¶
Depending on the actual scenario, and on use of Internet to interconnectdifferent users, the communication requirements of this use-case might beconsidered as latency critical due to the need of bounded latency. But note thatin most of these scenarios, part of the communication path is not wireless andDetNet mechanisms cannot be applied easily (e.g., when the public Internet isinvolved), and therefore in these cases, reliability is the criticalrequirement.¶
Unmanned Aerial Vehicles (UAVs) are becoming very popular for many differentapplications, including military and civil use-cases. The term drone is commonlyused to refer to a UAV.¶
UAVs can be used to perform aerial surveillance activities, traffic monitoring(i.e., the Spanish traffic control has recently introduced a fleet of drones forquicker reactions upon traffic congestion related events), support of emergencysituations, and even transportation of small goods (e.g., medicine in ruralareas).¶
Many types of vehicles, including UAVs but also others, such as cars, can travelin platoons, driving together with shorter distances between vehicles toincrease efficiency. Platooning imposes certain vehicle-to-vehicleconsiderations, most of these are applicable to both UAVs and other vehicletypes.¶
UAVs/vehicles typically have various forms of wireless connectivity:¶
Note that autonomous cars share many of the characteristics of the aforementionUAV case, and therefore it is of interest for RAW.¶
Some of the use-cases/tasks involving UAVs require coordination among UAVs.Others involve complex compute tasks that might not be performed using thelimited computing resources that a drone typically has. These two aspectsrequire continuous connectivity with the control center and among UAVs.¶
Remote maneuvering of a drone might be performed over a cellular network in somecases, however, there are situations that need very low latency anddeterministic behavior of the connectivity. Examples involve platooning ofdrones or sharing of computing resources among drones (like, a drone offload somefunction to a neighboring drone).¶
UAVs cannot be connected through any type of wired media, so it is obvious thatwireless is needed.¶
The network infrastructure is composed by the UAVs themselves, requiringself-configuration capabilities.¶
Heterogeneous types of traffic need to be supported, from extremely criticalones requiring ultra-low latency and high resiliency, to traffic requiringlow-medium latency.¶
When a given service is decomposed into functions -- hosted at different UAVs --chained, each link connecting two given functions would have a well-defined setof requirements (e.g., latency, bandwidth and jitter) that must be met.¶
Today's solutions keep the processing operations that are critical local (i.e.,they are not offloaded). Therefore, in this use-case, the critical requirementis reliability, and only for some platooning and inter-drone communicationslatency is critical.¶
The Edge Robotics scenario consists of several robots, deployed in a given area(like a shopping mall), inter-connected via an access network to anetwork edge device or a data center. The robots are connected to the edge socomplex computational activities are not executed locally at the robots butoffloaded to the edge. This brings additional flexibility in the type of tasksthat the robots do, as well as reducing the costs of robot manufacturing (due totheir lower complexity), and enabling complex tasks involving coordination amongrobots (that can be more easily performed if robots are centrally controlled).¶
Simple examples of the use of multiple robots are cleaning, video surveillance,search and rescue operations, and delivering of goods from warehouses to shops.Multiple robots are simultaneously instructed to perform individual tasks bymoving the robotic intelligence from the robots to the network's edge. Thatenables easy synchronization, scalable solution, and on-demand option to createflexible fleet of robots.¶
Robots would have various forms of wireless connectivity:¶
Some of the use-cases/tasks involving robots might benefit from decomposition ofa service in small functions that are distributed and chained among robots andthe edge. These require continuous connectivity with the control center andamong drones.¶
Robot control is an activity requiring very low latency between the robot andthe location where the control intelligence resides (which might be the edge oranother robot).¶
Deploying robots in scenarios such as shopping malls for the applicationsmentioned cannot be done via wired connectivity.¶
The network infrastructure needs to support heterogeneous types of traffic, fromrobot control to video streaming.¶
When a given service is decomposed into functions -- hosted at different robots-- chained, each link connecting two given functions would have a well-definedset of requirements (latency, bandwidth and jitter) that must be met.¶
This use-case might combine multiple communication flows, with some of thembeing latency critical (like those related to robot control tasks). Note thatthere are still many communication flows (like some offloading tasks) that onlydemand reliability and availability.¶
An instrumented ambulance would be one that has a LAN to which are connectedthese end systems such as:¶
The LAN needs to be routed through radio-WANs to complete the networklinkage.¶
What we have today is multiple communication systems to reach the vehicle via:¶
This redundancy of systems does not contribute to availability.¶
Most of the scenarios involving the use of an instrumented ambulance arecomposed of many different flows, each of them with slightly differentrequirements in terms of reliability and latency. Destinations might be eitherat the ambulance itself (local traffic), at a near edge cloud or at the generalInternet/cloud.¶
Local traffic between the first responders/ambulance staff and the ambulanceequipment cannot be done via wired connectivity as the responders performinitial treatment outside of the ambulance. The communications from theambulance to external services must be wireless as well.¶
We can derive some pertinent requirements from this scenario:¶
In this case, all applications identified do not require latency criticalcommunication, but do need high reliability and availability.¶
This document enumerates several use-cases and applications that need RAWtechnologies, focusing on the requirements from reliability, availability andlatency. Whereas some use-cases are latency-critical, there are also severalapplications that are non-latency critical, but that do pose strict reliabilityand availability requirements.¶
This document has no IANA actions.¶
This document covers several representative applications and network scenariosthat are expected to make use of RAW technologies. Each of the potential RAWuse-cases will have security considerations from both the use-specificperspective and the RAW technology perspective.[RFC9055]provides a comprehensive discussion of security considerations in the context ofDeterministic Networking, which are generally applicable also to RAW.¶
Nils Maeurer, Thomas Graeupl and Corinna Schmitt have contributedsignificantly to this document, providing input for the Aeronauticalcommunication section. Rex Buddenberg has also contributed to the document,providing input to the Emergency: instrumented emergency vehicle section.¶
The authors would like to thank Toerless Eckert, Xavi Vilajosana Guillen, RuteSofia, Corinna Schmitt, Victoria Pritchard, John Scudder, Joerg Ott and Stewart Bryant for their valuable comments on previous versions of this document.¶
The work of Carlos J. Bernardos in this document has been partially supported bythe H2020 5Growth (Grant 856709) and 5G-DIVE projects (Grant 859881), and UNICO5G I+D 6G-DATADRIVEN-04 project.¶
draft-ietf-raw-use-cases-08
| Document | Document type | This is an older version of an Internet-Draft that was ultimately published asRFC 9450. | |
|---|---|---|---|
| Select version | |||
| Compare versions | |||
| Authors | Carlos J. Bernardos,Georgios Z. Papadopoulos,Pascal Thubert,Fabrice Theoleyre | ||
| Replaces | draft-bernardos-raw-use-cases | ||
| RFC stream | |||
| Other formats | |||
| Additional resources | Mailing list discussion |