Merge pull request #834 from TelegramSam/oob_transition_update

Update 496 OOB transition with dates and title

features/0160-connection-protocol/README.md

@@ -107,6 +107,8 @@ The *invitee* sends the *inviter* an ack or any other message that confirms the
 
 [0-invitation]: #0-invitation
 
+> Note: This Invitation message is deprecated, and should use an invitation message from the [Out Of Band Protocol](../0434-outofband/README.md)
+
 An invitation to connect may be transferred using any method that can reliably transmit text. The result  must be the essential data necessary to initiate a [Connection Request](#1-connection-request) message. A connection invitation is an agent message with agent plaintext format, but is an **out-of-band communication** and therefore not communicated using wire level encoding or encryption. The necessary data that an invitation to connect must result in is:
 
 - suggested label

features/0496-transition-to-oob-and-did-exchange/README.md

@@ -1,9 +1,9 @@
-# Aries RFC 0496: Transition to the Out of Band and DID Exchange Protocols
+# Aries RFC 0496: Transition to the Out of Band Protocol
 
 - Authors: [Stephen Curran](mailto:[email protected])
-- Status: [ACCEPTED](/README.md#accepted)
+- Status: [ADOPTED](/README.md#adopted)
 - Since: 2021-11-24
-- Status Note: In step 1 - update all implementations to accept Connection and OOB Invitations. **Target Completion Date: 2022-03-31**
+- Status Note: In step 2 - All systems using OOB. **Target Completion Date: 2024-07-02**
 - Supersedes:
 - Start Date: 2020-06-07
 - Tags: [feature](/tags.md#feature), [community-update](/tags.md#community-update), [test-anomaly](/tags.md#test-anomaly)
@@ -28,10 +28,10 @@ The transition from the old to new messages will occur in four steps:
   - See the section below on [Step 1 out-of-band messages](#step-1-out-of-band-messages)
   - During Step 1, all agents should continue to send the current invitation and connection-less protocol messages.
   - Each agent builder SHOULD notify the community they have completed Step 1 by submitting a PR to update their entry in the [implementations](#implementations) section of this RFC.
-- **Step 2**: Agent builders update all agent code bases and deployments to send out out-of-band invitations equivalent to the current invitation and connection-less protocol messages, and Agent builders add full out-of-band and did-exchange ([RFC 0023](../0023-did-exchange/README.md)) protocol support to all agent code bases and deployments.
+- **Step 2**: Agent builders update all agent code bases and deployments to send out out-of-band invitations equivalent to the current invitation and connection-less protocol messages, and Agent builders add full out-of-band protocol support to all agent code bases and deployments.
   - Messages from existing RFCs being replaced by the out-of-band protocol are marked as `deprecated`.
   - Full out-of-band support is **NOT** required—just support for the out-of-band equivalents of the old `invitation` messages.
-  - When sending or receiving `did:peer` DIDs, the DIDs MUST conform to [RFC 627 Static Peer DIDs](../0627-static-peer-dids/README.md).
+  - When sending or receiving `did:peer` DIDs, the DIDs MUST conform to the [Peer DID Specification](https://identity.foundation/peer-did-method-spec/).
   - Each agent builder SHOULD notify the community they have completed Step 2 by submitting a PR to update their entry in the [implementations](#implementations) section.
 - **Step 3**: Support for the current invitation and connection-less protocol messages can be removed from all implementations and deployments, and all out-of-band `invitation` capabilities that align with the then current Aries Interop Profile (AIP) may be offered.