< draft-bernardos-raw-joint-selection-raw-mec-01.txt   draft-bernardos-raw-joint-selection-raw-mec-02.txt >
RAW WG CJ. Bernardos RAW WG CJ. Bernardos
Internet-Draft UC3M Internet-Draft UC3M
Intended status: Standards Track A. Mourad Intended status: Standards Track A. Mourad
Expires: March 14, 2022 InterDigital Expires: 22 September 2022 InterDigital
September 10, 2021 21 March 2022
Terminal-based joint selection and configuration of MEC host and RAW Terminal-based joint selection and configuration of MEC host and RAW
network network
draft-bernardos-raw-joint-selection-raw-mec-01 draft-bernardos-raw-joint-selection-raw-mec-02
Abstract Abstract
There are several scenarios involving multi-hop heterogeneous There are several scenarios involving multi-hop heterogeneous
wireless networks requiring reliable and available features combined wireless networks requiring reliable and available features combined
with multi-access edge computing, such as Industry 4.0. This with multi-access edge computing, such as Industry 4.0. This
document discusses mechanisms to allow a terminal influencing the document discusses mechanisms to allow a terminal influencing the
selection of a MEC host for instantiation of the terminal-targeted selection of a MEC host for instantiation of the terminal-targeted
MEC applications and functions, and (re)configuring the RAW network MEC applications and functions, and (re)configuring the RAW network
lying in between the terminal and the selected MEC host. This lying in between the terminal and the selected MEC host. This
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 14, 2022. This Internet-Draft will expire on 22 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents (https://trustee.ietf.org/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Revised BSD License text as
include Simplified BSD License text as described in Section 4.e of described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as provided without warranty as described in the Revised BSD License.
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction and Problem Statement . . . . . . . . . . . . . 2 1. Introduction and Problem Statement . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Terminal-based joint selection and configuration of MEC host 3. Terminal-based joint selection and configuration of MEC host
and RAW network . . . . . . . . . . . . . . . . . . . . . . . 6 and RAW network . . . . . . . . . . . . . . . . . . . . . 6
3.1. Extended User application look-up to support reliability 3.1. Extended User application look-up to support reliability
and availability information/capabilities . . . . . . . . 7 and availability information/capabilities . . . . . . . . 7
3.2. Extended Application context create to support 3.2. Extended Application context create to support reliability
reliability and availability information/capabilities . . 9 and availability information/capabilities . . . . . . . . 9
3.3. Extended Application context update to support 3.3. Extended Application context update to support reliability
reliability and availability information/capabilities . . 11 and availability information/capabilities . . . . . . . . 11
3.4. Receiving extended notification events . . . . . . . . . 12 3.4. Receiving extended notification events . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
7. Informative References . . . . . . . . . . . . . . . . . . . 13 7. Informative References . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction and Problem Statement 1. Introduction and Problem Statement
Wireless operates on a shared medium, and transmissions cannot be Wireless operates on a shared medium, and transmissions cannot be
fully deterministic due to uncontrolled interferences, including fully deterministic due to uncontrolled interferences, including
self-induced multipath fading. RAW (Reliable and Available Wireless) self-induced multipath fading. RAW (Reliable and Available Wireless)
is an effort to provide Deterministic Networking on across a path is an effort to provide Deterministic Networking on across a path
that include a wireless interface. RAW provides for high reliability that include a wireless interface. RAW provides for high reliability
and availability for IP connectivity over a wireless medium. The and availability for IP connectivity over a wireless medium. The
wireless medium presents significant challenges to achieve wireless medium presents significant challenges to achieve
skipping to change at page 3, line 5 skipping to change at page 3, line 6
availability for an IP network utilizing scheduled wireless segments availability for an IP network utilizing scheduled wireless segments
and other media, e.g., frequency/time-sharing physical media and other media, e.g., frequency/time-sharing physical media
resources with stochastic traffic: IEEE Std. 802.15.4 timeslotted resources with stochastic traffic: IEEE Std. 802.15.4 timeslotted
channel hopping (TSCH), 3GPP 5G ultra-reliable low latency channel hopping (TSCH), 3GPP 5G ultra-reliable low latency
communications (URLLC), IEEE 802.11ax/be, and L-band Digital communications (URLLC), IEEE 802.11ax/be, and L-band Digital
Aeronautical Communications System (LDACS), etc. Similar to DetNet, Aeronautical Communications System (LDACS), etc. Similar to DetNet,
RAW technologies aim at staying abstract to the radio layers RAW technologies aim at staying abstract to the radio layers
underneath, addressing the Layer 3 aspects in support of applications underneath, addressing the Layer 3 aspects in support of applications
requiring high reliability and availability. requiring high reliability and availability.
As introduced in [I-D.pthubert-raw-architecture], RAW separates the As introduced in [I-D.ietf-raw-architecture], RAW separates the path
path computation time scale at which a complex path is recomputed computation time scale at which a complex path is recomputed from the
from the path selection time scale at which the forwarding decision path selection time scale at which the forwarding decision is taken
is taken for one or a few packets. RAW operates at the path for one or a few packets. RAW operates at the path selection time
selection time scale. The RAW problem is to decide, amongst the scale. The RAW problem is to decide, amongst the redundant solutions
redundant solutions that are proposed by the Patch Computation that are proposed by the Patch Computation Element (PCE), which one
Element (PCE), which one will be used for each packet to provide a will be used for each packet to provide a Reliable and Available
Reliable and Available service while minimizing the waste of service while minimizing the waste of constrained resources. To that
constrained resources. To that effect, RAW defines the Path effect, RAW defines the Path Selection Engine (PSE) that is the
Selection Engine (PSE) that is the counter-part of the PCE to perform counter-part of the PCE to perform rapid local adjustments of the
rapid local adjustments of the forwarding tables within the diversity forwarding tables within the diversity that the PCE has selected for
that the PCE has selected for the Track. The PSE enables to exploit the Track. The PSE enables to exploit the richer forwarding
the richer forwarding capabilities with Packet (hybrid) ARQ, capabilities with Packet (hybrid) ARQ, Replication, Elimination and
Replication, Elimination and Ordering (PAREO), and scheduled Ordering (PAREO), and scheduled transmissions at a faster time scale.
transmissions at a faster time scale.
Multi-access Edge Computing (MEC) -- formerly known as Mobile Edge Multi-access Edge Computing (MEC) -- formerly known as Mobile Edge
Computing -- capabilities deployed in the edge of the mobile network Computing -- capabilities deployed in the edge of the mobile network
can facilitate the efficient and dynamic provision of services to can facilitate the efficient and dynamic provision of services to
mobile users. The ETSI ISG MEC working group, operative from end of mobile users. The ETSI ISG MEC working group, operative from end of
2014, intends to specify an open environment for integrating MEC 2014, intends to specify an open environment for integrating MEC
capabilities with service providers' networks, including also capabilities with service providers' networks, including also
applications from 3rd parties. These distributed computing applications from 3rd parties. These distributed computing
capabilities will make available IT infrastructure as in a cloud capabilities will make available IT infrastructure as in a cloud
environment for the deployment of functions in mobile access environment for the deployment of functions in mobile access
skipping to change at page 4, line 45 skipping to change at page 4, line 45
| ------- | RAW | ------- ^ (o | | ------- | RAW | ------- ^ (o |
| | MEC |------|node | | RAW | / \ -\---- | | | MEC |------|node | | RAW | / \ -\---- |
| ------- ------- |node | / \ |term| | | ------- ------- |node | / \ |term| |
| o) o) ------- ------- -0--0- | | o) o) ------- ------- -0--0- |
| ----/- ----/- | RAW | | | ----/- ----/- | RAW | |
| |term| |term| |node | | | |term| |term| |node | |
| -0--0- -0--0- ------- | | -0--0- -0--0- ------- |
|_______________________________________________________| |_______________________________________________________|
Figure 1: Exemplary scenario depicting MEC and RAW in an industrial Figure 1: Exemplary scenario depicting MEC and RAW in an industrial
environments environments
Figure 1 depicts an exemplary scenario that integrates a 3GPP 5G Figure 1 depicts an exemplary scenario that integrates a 3GPP 5G
network, with ETSI MEC deployed at the edge, and an IETF RAW-capable network, with ETSI MEC deployed at the edge, and an IETF RAW-capable
wireless multi-hop backhaul segment connecting the RAN and the MEC wireless multi-hop backhaul segment connecting the RAN and the MEC
hosts and UPFs. This setup can be used for example in a factory hosts and UPFs. This setup can be used for example in a factory
where multiple robots and AGVs are wirelessly connected, and where multiple robots and AGVs are wirelessly connected, and
controlled via remote apps. Control applications running in the edge controlled via remote apps. Control applications running in the edge
(implemented as MEC applications) require bounded low latencies and a (implemented as MEC applications) require bounded low latencies and a
guaranteed availability, despite the mobility of the terminals and guaranteed availability, despite the mobility of the terminals and
the changing wireless conditions. An heterogeneous wireless mesh the changing wireless conditions. An heterogeneous wireless mesh
skipping to change at page 7, line 14 skipping to change at page 7, line 14
------------ ------------
| MEC host | | MEC host |
------+----- ------+-----
------------ ---------- | ------------ ---------- |
| User | | Mobile | ------+--------------------- | User | | Mobile | ------+---------------------
| App. LCM +---+ edge | | MEC host | | App. LCM +---+ edge | | MEC host |
| Proxy | | orch. | | ----------------- | | Proxy | | orch. | | ----------------- |
------------ ---------- | + ------ ------ | | ------------ ---------- | + ------ ------ | |
| RAW | | ----- | | ME | |RAW | | | | RAW | | ----- | | ME | |RAW | | |
| ctrl| -----------+ |app+..+ |serv| |ctrl| | | | ctrl| -----------+ |app+··+ |serv| |ctrl| | |
---+--- | | ----- | ------ ------ | | ---+--- | | ----- | ------ ------ | |
| +--+--+ | |app+..+ MEC platform | | | +--+--+ | |app+··+ MEC platform | |
| | RAW | | ----- ----------------- | | | RAW | | ----- ----------------- |
+-----.+ PSE | ---------------------------- +-----.+ PSE | ----------------------------
+-+-+-+ +-+-+-+
| | ( ( o ) ) ( ( o ) ) | | ( ( o ) ) ( ( o ) )
| | ^ ^ | | ^ ^
| | / \ / \ | | / \ / \
| | / \ / \ | | / \ / \
| | ------- ------- | | ------- -------
| +-----------| RAW |-------+ RAW | | +-----------| RAW |-------+ RAW |
+-------------+node | |node | +-------------+node | |node |
skipping to change at page 8, line 12 skipping to change at page 8, line 12
Figure 3 shows an exemplary signaling flow diagram. Figure 3 shows an exemplary signaling flow diagram.
+--------------+ +--------------+
+----------+ | MEC host | +----------+ | MEC host |
+--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ | +--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ |
|UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | | |UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | |
+--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| | +--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| |
| | |ctrl| +---+ | +----+ +----+ | +---+ +----+ | | | |ctrl| +---+ | +----+ +----+ | +---+ +----+ |
| | +----+ | | | | +---|------|---+ | | +----+ | | | | +---|------|---+
| | | |<...RAW........>| | | | | | | |<···RAW········>| | | |
| | | |<...signalling.........>| | | | | | |<···signalling·········>| | |
| | | | | | | | | | | | | | | | | |
|1.GET ../app_list | | | | | | |1.GET ../app_list | | | | | |
|....>| | | | | | | | |····>| | | | | | | |
| |........MEC...........>|.....MEC................>| | | |········MEC···········>|·····MEC················>| |
| |<.......signalling.....|<....signalling..........| | | |<·······signalling·····|<····signalling··········| |
| | | | | | | | | | | | | | | | | |
| |2.RAW info req.| | | | | | | |2.RAW info req.| | | | | |
| |...>|.........>| | | | | | | |···>|·········>| | | | | |
| |<...|<.........| | | | | | | |<···|<·········| | | | | |
| | | | | | | | | | | | | | | | | |
|2.200 OK | | | | | | | |2.200 OK | | | | | | |
|(Application List) | | | | | | |(Application List) | | | | | |
| | | | | | | | | | | | | | | | | |
Figure 3: Extended User application look-up Figure 3: Extended User application look-up
We next explain each of the steps illustrated in the figure: We next explain each of the steps illustrated in the figure:
1. An application that requires use of a MEC app with specific 1. An application that requires use of a MEC app with specific
skipping to change at page 9, line 33 skipping to change at page 9, line 33
request the creation of a MEC app including requirements about request the creation of a MEC app including requirements about
reliability and availability. reliability and availability.
+--------------+ +--------------+
+----------+ | MEC host | +----------+ | MEC host |
+--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ | +--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ |
|UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | | |UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | |
+--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| | +--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| |
| | |ctrl| +---+ | +----+ +----+ | +---+ +----+ | | | |ctrl| +---+ | +----+ +----+ | +---+ +----+ |
| | +----+ | | | | +---|------|---+ | | +----+ | | | | +---|------|---+
| | | |<..RAW.........>| | | | | | | |<··RAW·········>| | | |
| | | |<..signalling..........>| | | | | | |<··signalling··········>| | |
| | | | | | | | | | | | | | | | | |
|1.POST ../app_context| | | | | | |1.POST ../app_context| | | | | |
|....>| | | | | | | | |····>| | | | | | | |
| |..MEC signalling......>|..MEC signalling........>| | | |··MEC signalling······>|··MEC signalling········>| |
| | | | | | | 2.MEC-to-RAW | | | | | | | 2.MEC-to-RAW
| | | | | | | |.....>| | | | | | | | |·····>|
| | | |<..2.RAW................................| | | | |<··2.RAW································|
| | |<.........|....signalling.>| | | | | | |<·········|····signalling·>| | | |
| | | |.......................>| | | | | | |·······················>| | |
| | | | | | | |<.....| | | | | | | | |<·····|
| |<......MEC.signalling..|<........MEC signalling..| | | |<······MEC·signalling··|<········MEC signalling··| |
| | | | | | | | | | | | | | | | | |
|3.201 Created | | | | | | |3.201 Created | | | | | |
|(AppContext) | | | | | | |(AppContext) | | | | | |
| | | | | | | | | | | | | | | | | |
Figure 4: Application context create Figure 4: Application context create
Figure 4 shows an exemplary signaling flow diagram. We next explain Figure 4 shows an exemplary signaling flow diagram. We next explain
each of the steps illustrated in the figure: each of the steps illustrated in the figure:
1. The UE submits the POST request to the UALCMP. The message body 1. The UE submits the POST request to the UALCMP. The message body
contains the data structure for the application context to be contains the data structure for the application context to be
created, which is extended to include reliability and created, which is extended to include reliability and
availability attributes: availability attributes:
* The assured round trip time in milliseconds supported by the * The assured round trip time in milliseconds supported by the
skipping to change at page 11, line 20 skipping to change at page 11, line 20
about reliability and availability. One example would be about reliability and availability. One example would be
communicating new reliability/availability requirements. communicating new reliability/availability requirements.
+--------------+ +--------------+
+----------+ | MEC host | +----------+ | MEC host |
+--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ | +--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ |
|UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | | |UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | |
+--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| | +--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| |
| | |ctrl| +---+ | +----+ +----+ | +---+ +----+ | | | |ctrl| +---+ | +----+ +----+ | +---+ +----+ |
| | +----+ | | | | +---|------|---+ | | +----+ | | | | +---|------|---+
| | | |<..RAW.........>| | | | | | | |<··RAW·········>| | | |
| | | |<..signalling..........>| | | | | | |<··signalling··········>| | |
| | | | | | | | | | | | | | | | | |
|1.PUT ../app_contexts| | | | | | |1.PUT ../app_contexts| | | | | |
| {contextID} (AppContext) | | | | | | {contextID} (AppContext) | | | | |
|....>| | | | | | | | |····>| | | | | | | |
| |..MEC signalling......>|..MEC signalling........>| | | |··MEC signalling······>|··MEC signalling········>| |
| | | | | | | 2.MEC-to-RAW | | | | | | | 2.MEC-to-RAW
| | | | | | | |.....>| | | | | | | | |·····>|
| | | |<..2.RAW................................| | | | |<··2.RAW································|
| | |<.........|...signalling..>| | | | | | |<·········|···signalling··>| | | |
| | | |.......................>| | | | | | |·······················>| | |
| | | | | | | |<.....| | | | | | | | |<·····|
| |<......MEC.signalling..|<........MEC signalling..| | | |<······MEC·signalling··|<········MEC signalling··| |
| | | | | | | | | | | | | | | | | |
|3.204 No Content | | | | | | |3.204 No Content | | | | | |
|<....| | | | | | | | |<····| | | | | | | |
| | | | | | | | | | | | | | | | | |
Figure 5: Application context update Figure 5: Application context update
Figure 5 shows an exemplary signaling flow diagram. We next explain Figure 5 shows an exemplary signaling flow diagram. We next explain
each of the steps illustrated in the figure: each of the steps illustrated in the figure:
1. An application running on the UE making use of a MEC app might 1. An application running on the UE making use of a MEC app might
change its requirements for the MEC app and associated change its requirements for the MEC app and associated
reliability and availability (for example, in an Industry 4.0 reliability and availability (for example, in an Industry 4.0
scenario, a robot control app might be required less latency to scenario, a robot control app might be required less latency to
improve its precision). The UE updates a specific application improve its precision). The UE updates a specific application
context by sending a PUT request to the resource within the MEC context by sending a PUT request to the resource within the MEC
skipping to change at page 12, line 27 skipping to change at page 13, line 12
time (e.g., implementing changes at the application level or time (e.g., implementing changes at the application level or
selecting another point of attachment/slice). selecting another point of attachment/slice).
+--------------+ +--------------+
+----------+ | MEC host | +----------+ | MEC host |
+--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ | +--+ | UALCMP | +---+ +----+ +----+ +----+ | +----+ |
|UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | | |UE| +---+----+-+ |RAW| |MEAO| |RAW | |RAW | | +---+ |RAW | |
+--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| | +--+ | |RAW | |PSE| +----+ |node| |node| | |MEP| |ctrl| |
| | |ctrl| +---+ | +----+ +----+ | +---+ +----+ | | | |ctrl| +---+ | +----+ +----+ | +---+ +----+ |
| | +----+ | | | | +---|------|---+ | | +----+ | | | | +---|------|---+
| | | |<..RAW.........>| | | | | | | |<··RAW·········>| | | |
| | | |<..signalling..........>| | | | | | |<··signalling··········>| | |
| | | | | | | | | | | | | | | | | |
| | | Event occurs (e.g., it is no longer | | | | | Event occurs (e.g., it is no longer | |
| | | to keep assured RAW conditions) | | | | | to keep assured RAW conditions) | |
| | | | | | | | | | | | | | | | | |
| | | |1.MEC-to-RAW | | | | | | | |1.MEC-to-RAW | | | |
| | | |.......................................>| | | | |·······································>|
| | | | | | | |<.....| | | | | | | | |<·····|
| |<......MEC signalling..|<........MEC signalling..| | | |<······MEC signalling··|<········MEC signalling··| |
| | | | | | | | | | | | | | | | | |
|2.POST ../callback_ref | | | | | |2.POST ../callback_ref | | | | |
| ({Notification}) | | | | | | | ({Notification}) | | | | | |
|<....| | | | | | | | |<····| | | | | | | |
|3.204 No Content | | | | | | |3.204 No Content | | | | | |
|....>| | | | | | | | |····>| | | | | | | |
| | | | | | | | | | | | | | | | | |
Figure 6: Receiving notification events Figure 6: Receiving notification events
Figure 5 shows an exemplary signaling flow diagram. We next explain Figure 5 shows an exemplary signaling flow diagram. We next explain
each of the steps illustrated in the figure: each of the steps illustrated in the figure:
1. If a change of the assured RAW conditions happens (which is 1. If a change of the assured RAW conditions happens (which is
detected via RAW OAM mechanisms, out of the scope of this detected via RAW OAM mechanisms, out of the scope of this
document, and then notified to the MEC platform), this event document, and then notified to the MEC platform), this event
skipping to change at page 14, line 7 skipping to change at page 14, line 36
6. Acknowledgments 6. Acknowledgments
The work in this draft will be further developed and explored under The work in this draft will be further developed and explored under
the framework of the H2020 5Growth (Grant 856709). the framework of the H2020 5Growth (Grant 856709).
7. Informative References 7. Informative References
[I-D.bernardos-raw-mec] [I-D.bernardos-raw-mec]
Bernardos, C. J. and A. Mourad, "Extensions to enable Bernardos, C. J. and A. Mourad, "Extensions to enable
wireless reliability and availability in multi- access wireless reliability and availability in multi-access edge
edge deployments", draft-bernardos-raw-mec-02 (work in deployments", Work in Progress, Internet-Draft, draft-
progress), July 2021. bernardos-raw-mec-03, 27 January 2022,
<https://www.ietf.org/archive/id/draft-bernardos-raw-mec-
03.txt>.
[I-D.ietf-raw-use-cases] [I-D.ietf-raw-architecture]
Papadopoulos, G. Z., Thubert, P., Theoleyre, F., and C. J. Thubert, P. and G. Z. Papadopoulos, "Reliable and
Bernardos, "RAW use cases", draft-ietf-raw-use-cases-02 Available Wireless Architecture", Work in Progress,
(work in progress), July 2021. Internet-Draft, draft-ietf-raw-architecture-04, 4 March
2022, <https://www.ietf.org/archive/id/draft-ietf-raw-
architecture-04.txt>.
[I-D.pthubert-raw-architecture] [I-D.ietf-raw-use-cases]
Thubert, P., Papadopoulos, G. Z., and L. Berger, "Reliable Bernardos, C. J., Papadopoulos, G. Z., Thubert, P., and F.
and Available Wireless Architecture/Framework", draft- Theoleyre, "RAW use-cases", Work in Progress, Internet-
pthubert-raw-architecture-09 (work in progress), July Draft, draft-ietf-raw-use-cases-05, 23 February 2022,
2021. <https://www.ietf.org/archive/id/draft-ietf-raw-use-cases-
05.txt>.
Authors' Addresses Authors' Addresses
Carlos J. Bernardos Carlos J. Bernardos
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad, 30 Av. Universidad, 30
Leganes, Madrid 28911 28911 Leganes, Madrid
Spain Spain
Phone: +34 91624 6236 Phone: +34 91624 6236
Email: cjbc@it.uc3m.es Email: cjbc@it.uc3m.es
URI: http://www.it.uc3m.es/cjbc/ URI: http://www.it.uc3m.es/cjbc/
Alain Mourad Alain Mourad
InterDigital Europe InterDigital Europe
Email: Alain.Mourad@InterDigital.com Email: Alain.Mourad@InterDigital.com
URI: http://www.InterDigital.com/ URI: http://www.InterDigital.com/
 End of changes. 34 change blocks. 
93 lines changed or deleted 94 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/