Update AIP 2.0 links to point to clarified RFCs -- notably refs to main branch

[swcurran]

Signed-off-by: Stephen Curran swcurran@gmail.com

[swcurran]

This PR updates the AIP 2 RFC links to specific commits to add in clarifications made since AIP 2.0 was created. This PR covers RFCs that changed references to the "main" branch of this or other repos ONLY. The only additions:

• RFC 0005 DIDComm changed two links from pull requests to the merged document referenced in those pull requests.
• RFC 0005 Agents, RFC 0046 Mediators and Relays, and RFC 0211 Route Coordination also each added an implementation table entry.

The full list of diffs from the documents linked from the existing AIP 2.0 version to those in this pull request is provided below. Those approving this PR should review this list to ensure changes other than those listed above were changed. This listed was generated from the code/aipUpdates.py script.

Aries Interop Profile: 2.0
>>>>>>>> Changed protocol: concepts/0003-protocols, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0003-protocols/tictactoe/README.md b/concepts/0003-protocols/tictactoe/README.md
index 8dce429..cbfb064 100644
--- a/concepts/0003-protocols/tictactoe/README.md
+++ b/concepts/0003-protocols/tictactoe/README.md
@@ -29,7 +29,7 @@ capture 3 cells of the grid in a straight line.
 ### Name and Version
 
 This defines the `tictactoe` protocol, version 1.x, as identified by the
-following [PIURI](https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0003-protocols#message-type-and-protocol-identifier-uris):
+following [PIURI](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0003-protocols#message-type-and-protocol-identifier-uris):
 
     did:sov:SLfEi9esrjzybysFxQZbfq;spec/tictactoe/1.0
 

>>>>>>>> Changed protocol: concepts/0004-agents, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0004-agents/README.md b/concepts/0004-agents/README.md
index b1147aa..dabe7e4 100644
--- a/concepts/0004-agents/README.md
+++ b/concepts/0004-agents/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2019-01-15
 - Status Note: On a standards track and beginning to influence many mental models, but not yet [ADOPTED](/README.md#rfc-lifecycle). 
-- Supersedes: [Indy HIPE 0002](https://github.com/hyperledger/indy-hipe/tree/master/text/0002-agents)
+- Supersedes: [Indy HIPE 0002](https://github.com/hyperledger/indy-hipe/tree/main/text/0002-agents)
 - Start Date: 2017-11-01 (approx, backdated)
 - Tags: [concept](/tags.md#concept)
 
@@ -169,7 +169,7 @@ Here are some thought questions to clarify intent:
 We said it's hard to provide a recipe for an agent without specifics.
 However, the majority of agents _do_ have two things in common:
 they listen to and process A2A messages, and they use a [wallet](
-https://github.com/hyperledger/indy-hipe/blob/master/text/0013-wallets/README.md)
+https://github.com/hyperledger/indy-hipe/blob/main/text/0013-wallets/README.md)
 to manage keys, credentials, and other sensitive material. Unless you have
 uses cases that involve IoT, cron jobs, or web hooks, your agent is
 likely to fit this mold.
@@ -236,7 +236,7 @@ in the DID Doc of the recipient, and finding an intersection
 between transports they use, and transports the sender can
 speak. Line 3 requires the keys of the sender, which would
 normally be held in a [wallet](
-https://github.com/hyperledger/indy-hipe/blob/master/text/0013-wallets/README.md).
+https://github.com/hyperledger/indy-hipe/blob/main/text/0013-wallets/README.md).
 If you are building this sort of code using Aries technology, you
 will certainly want to use [Aries Agent SDK](
@@ -253,7 +253,7 @@ or in its Getting Started Guide.
 
 * Hang out and ask questions on `#aries` on [chat.hyperledger.org](https://chat.hyperledger.org).
 * Use the mailing list: [aries@lists.hyperledger.org](mailto:aries@lists.hyperledger.org)
-* Follow the Aries Cloud Agent - Python [Getting Started Guide (for developers)](https://github.com/hyperledger/aries-cloudagent-python/tree/master/docs/GettingStartedAriesDev)
+* Follow the Aries Cloud Agent - Python [Getting Started Guide (for developers)](https://github.com/hyperledger/aries-cloudagent-python/tree/main/docs/GettingStartedAriesDev)
 * Study the [Aries Protocol Test Suite](https://github.com/hyperledger/aries-protocol-test-suite) |
 * Study the sample mobile agent at [github.com/sovrin-foundation/connector-app](https://github.com/sovrin-foundation/connector-app).
 * Browse other [RFCs](../../index.md).
@@ -365,7 +365,7 @@ that gap.
 ###### Identity Wallets
 
 "Identity wallet" is a term that's [carefully defined](
-https://github.com/hyperledger/indy-hipe/blob/master/text/0013-wallets/README.md#what-is-an-identity-wallet)
+https://github.com/hyperledger/indy-hipe/blob/main/text/0013-wallets/README.md#what-is-an-identity-wallet)
 in our ecosystem, and in strict, technical usage it maps to a
 concept much closer to "database" than "agent". This is because
 it is an inert storage container, not an active interacter. However, in
@@ -398,7 +398,7 @@ A cron job that runs once a night at Faber, scanning a database
 and revoking credentials that have changes status during the day,
 is an agent for Faber. This is true even though it doesn't listen
 for incoming messages (it only talks [revocation protocol](
-https://github.com/hyperledger/indy-hipe/tree/master/text/0011-cred-revocation) to the ledger). In order to
+https://github.com/hyperledger/indy-hipe/tree/main/text/0011-cred-revocation) to the ledger). In order to
 talk that protocol, it must hold keys delegated by Faber, and it
 is surely Faber's fiduciary.
 
@@ -503,4 +503,4 @@ Name / Link | Implementation Notes
 [Verity](https://www.evernym.com/products/) | Commercially licensed enterprise agent, SaaS or on-prem.
 [Aries Protocol Test Suite](https://github.com/hyperledger/aries-protocol-test-suite) | 
 [Pico Labs](http://picolabs.io/) | [Pico Agents](https://github.com/Picolab/G2S) protocols: connections, trust_ping, basicmessage, routing
- 
+[Rust Agent](https://github.com/tatmanblue/rust-aries-agent) | Rust implementation of a framework for building agents of all types

>>>>>>>> Changed protocol: concepts/0005-didcomm, latest commit to protocol: 1b4b014246d19c865c9b5520b97fe0376a86d8c4

diff --git a/concepts/0005-didcomm/README.md b/concepts/0005-didcomm/README.md
index ac65bfa..d105e16 100644
--- a/concepts/0005-didcomm/README.md
+++ b/concepts/0005-didcomm/README.md
@@ -28,14 +28,14 @@ We need a standard high-level reference.
 >This discussion assumes that you have a reasonable grasp on topics like
 [self-sovereign identity](https://medium.com/evernym/the-three-models-of-digital-identity-relationships-ca0727cb5186),
 [DIDs and DID docs](https://w3c-ccg.github.io/did-spec/), and [agents](
-https://github.com/hyperledger/indy-hipe/pull/86). If you find yourself
+https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0004-agents/README.md). If you find yourself
 lost, please review that material for background and starting assumptions.
 
 Agent-like things have to interact with one another to get work done. How they
 talk in general is DIDComm, the subject of this RFC. The specific interactions enabled by
 DIDComm--connecting and maintaining relationships, issuing credentials,
 providing proof, etc.--are called __protocols__; they are described [elsewhere](
-https://github.com/hyperledger/indy-hipe/pull/69).
+https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0003-protocols/README.md).
 
 ### Rough Overview
 

>>>>>>>> Changed protocol: concepts/0020-message-types, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0020-message-types/README.md b/concepts/0020-message-types/README.md
index 5ffd13f..18d119b 100644
--- a/concepts/0020-message-types/README.md
+++ b/concepts/0020-message-types/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2019-05-24
 - Status Note:  
-- Supersedes: [HIPE 0021 Message Types](https://github.com/hyperledger/indy-hipe/tree/master/text/0021-message-types)
+- Supersedes: [HIPE 0021 Message Types](https://github.com/hyperledger/indy-hipe/tree/main/text/0021-message-types)
 - Start Date: 2018-07-06
 - Tags: [concept](/tags.md#concept)
 

>>>>>>>> Changed protocol: concepts/0046-mediators-and-relays, latest commit to protocol: 45b4233fcffda14f1339380ae2233289f21296b0

diff --git a/concepts/0046-mediators-and-relays/README.md b/concepts/0046-mediators-and-relays/README.md
index fe7f389..c20572d 100644
--- a/concepts/0046-mediators-and-relays/README.md
+++ b/concepts/0046-mediators-and-relays/README.md
@@ -245,3 +245,4 @@ Name / Link | Implementation Notes
 --- | ---
 [Connect.Me](https://www.evernym.com/blog/connect-me-sovrin-digital-wallet/) | Free mobile app from Evernym. Installed via app store on iOS and Android. 
 [Verity](https://www.evernym.com/products/) | Commercially licensed enterprise agent, SaaS or on-prem.
+[DIDComm mediator](https://github.com/Sirius-social/didcomm-mediator) | Open source cloud-based mediator with Firebase support.

>>>>>>>> Changed protocol: concepts/0047-json-ld-compatibility, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0047-json-ld-compatibility/README.md b/concepts/0047-json-ld-compatibility/README.md
index 4c3961f..d6c2749 100644
--- a/concepts/0047-json-ld-compatibility/README.md
+++ b/concepts/0047-json-ld-compatibility/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2019-02-20
 - Status Note: Has guided Indy design choices for several months. Not yet ratified by greater Aries community. 
-- Supersedes: [Indy HIPE 0035](https://github.com/hyperledger/indy-hipe/tree/master/text/0035-json-ld-compatibility)
+- Supersedes: [Indy HIPE 0035](https://github.com/hyperledger/indy-hipe/tree/main/text/0035-json-ld-compatibility)
 - Start Date: 2019-01-23
 - Tags: [concept](/tags.md#concept), [decorator](/tags.md#decorator)
 

>>>>>>>> Changed protocol: concepts/0050-wallets, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0050-wallets/README.md b/concepts/0050-wallets/README.md
index 5610348..ee8b903 100644
--- a/concepts/0050-wallets/README.md
+++ b/concepts/0050-wallets/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2018-07-01
 - Status Note: Fully implemented in Indy SDK, but not yet socialized well in the broader Aries community. Needs some updates to promote better key management; see related RFC about [lox](../../features/0042-lox/README.md). 
-- Supersedes: [Indy HIPE 0013]( https://github.com/hyperledger/indy-hipe/tree/master/text/0013-wallets)
+- Supersedes: [Indy HIPE 0013]( https://github.com/hyperledger/indy-hipe/tree/main/text/0013-wallets)
 - Start Date: 2018-05-22
 - Tags: [concept](/tags.md#concept)
 

>>>>>>>> Changed protocol: features/0019-encryption-envelope, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/features/0019-encryption-envelope/README.md b/features/0019-encryption-envelope/README.md
index 3eee1b0..a2e89a4 100644
--- a/features/0019-encryption-envelope/README.md
+++ b/features/0019-encryption-envelope/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2019-05-04
 - Status Note:  
-- Supersedes: [INDY 0028 Wire Level Format](https://github.com/hyperledger/indy-hipe/tree/master/text/0028-wire-message-format)
+- Supersedes: [INDY 0028 Wire Level Format](https://github.com/hyperledger/indy-hipe/tree/main/text/0028-wire-message-format)
 - Start Date: 2018-07-10 (approximate, backdated)
 - Tags: [feature](/tags.md#feature)
 

>>>>>>>> Changed protocol: features/0023-did-exchange, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/features/0023-did-exchange/README.md b/features/0023-did-exchange/README.md
index fe81b54..583df63 100644
--- a/features/0023-did-exchange/README.md
+++ b/features/0023-did-exchange/README.md
@@ -415,7 +415,7 @@ When Peer DIDs are used in an exchange, it is likely that both the _requester_ a
 * [Agent to Agent Communication Video](https://drive.google.com/file/d/1PHAy8dMefZG9JNg87Zi33SfKkZvUvXvx/view)
 * [Agent to Agent Communication Presentation](https://docs.google.com/presentation/d/1H7KKccqYB-2l8iknnSlGt7T_sBPLb9rfTkL-waSCux0/edit#slide=id.p)
 * Problem_report message adopted into message family, following form defined by the [Problem Report HIPE](https://github.com/hyperledger/indy-hipe/blob/6a5e4fe2d7e14953cd8e3aed07d886176332e696/text/error-handling/README.md)
-* [RFC0519 Goal Codes](https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0519-goal-codes/README.md)
+* [RFC0519 Goal Codes](https://github.com/hyperledger/aries-rfcs/blob/main/concepts/0519-goal-codes/README.md)
 
 ## Drawbacks
 

>>>>>>>> Changed protocol: features/0048-trust-ping, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/features/0048-trust-ping/README.md b/features/0048-trust-ping/README.md
index c608483..8eb9485 100644
--- a/features/0048-trust-ping/README.md
+++ b/features/0048-trust-ping/README.md
@@ -4,7 +4,7 @@
 - Status: [ACCEPTED](/README.md#accepted)
 - Since: 2019-02-01
 - Status Note: Numerous implementations. 
-- Supersedes: [Indy HIPE 0032](https://github.com/hyperledger/indy-hipe/tree/master/text/0032-trust-ping)
+- Supersedes: [Indy HIPE 0032](https://github.com/hyperledger/indy-hipe/tree/main/text/0032-trust-ping)
 - Start Date: 2018-12-11
 - Tags: [feature](/tags.md#feature), [protocol](/tags.md#protocol), [test-anomaly](/tags.md#test-anomaly)
 
@@ -110,7 +110,7 @@ messages are encrypted with suitable algorithms and keys.
 
 2. Messages may be targeted at any known agent in the other party's sovereign
 domain, using [cross-domain routing conventions](
-https://github.com/hyperledger/indy-hipe/blob/master/text/0022-cross-domain-messaging/README.md),
+https://github.com/hyperledger/indy-hipe/blob/main/text/0022-cross-domain-messaging/README.md),
 and may be encrypted and
 packaged to expose exactly and only the information desired, at each hop
 along the way. This allows two parties to evaluate the completeness of

>>>>>>>> Changed protocol: features/0183-revocation-notification, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/features/0183-revocation-notification/README.md b/features/0183-revocation-notification/README.md
index 8d94940..7691041 100644
--- a/features/0183-revocation-notification/README.md
+++ b/features/0183-revocation-notification/README.md
@@ -50,17 +50,17 @@ The `revoke` message sent by the `issuer` to the `holder` is as follows:
 
 Description of fields:
 
-* `~please_ack` (optional) -- as described by the [Please ACK Decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/master/features/0317-please-ack).  If `OUTCOME` is specified, the `holder` should send an ack when the holder's agent has successfully notified the holder of the revocation.
+* `~please_ack` (optional) -- as described by the [Please ACK Decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/main/features/0317-please-ack).  If `OUTCOME` is specified, the `holder` should send an ack when the holder's agent has successfully notified the holder of the revocation.
 
-* `thread_id` (required) -- the [thread ID](https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0008-message-id-and-threading#thread-id-thid) of the [issue-credential-v2](https://github.com/hyperledger/aries-rfcs/tree/master/features/0453-issue-credential-v2) protocol which was used to issue one or more credentials that have been revoked by the issuer.  If multiple credentials were issued, each credential has a different credential format but contains the same claims as described [here](https://github.com/hyperledger/aries-rfcs/tree/b982c24b9083dd5dddff6343dbf534cd1cfe36a6/features/0453-issue-credential-v2#message-attachments); therefore, this message notifies the holder that all of these credentials have been revoked.
+* `thread_id` (required) -- the [thread ID](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0008-message-id-and-threading#thread-id-thid) of the [issue-credential-v2](https://github.com/hyperledger/aries-rfcs/tree/main/features/0453-issue-credential-v2) protocol which was used to issue one or more credentials that have been revoked by the issuer.  If multiple credentials were issued, each credential has a different credential format but contains the same claims as described [here](https://github.com/hyperledger/aries-rfcs/tree/b982c24b9083dd5dddff6343dbf534cd1cfe36a6/features/0453-issue-credential-v2#message-attachments); therefore, this message notifies the holder that all of these credentials have been revoked.
 
 * `comment` (optional) -- a field that provides some human readable information about the revocation notification.  This is typically the reason for the revocation as deemed appropriate by the issuer.
 
 ## Reference
 
-* See the [issue-credential-v2](https://github.com/hyperledger/aries-rfcs/tree/master/features/0453-issue-credential-v2) protocol.
-* See the [thread ID](https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0008-message-id-and-threading#thread-id-thid) description.
-* See the [Please ACK Decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/master/features/0317-please-ack).
+* See the [issue-credential-v2](https://github.com/hyperledger/aries-rfcs/tree/main/features/0453-issue-credential-v2) protocol.
+* See the [thread ID](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0008-message-id-and-threading#thread-id-thid) description.
+* See the [Please ACK Decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/main/features/0317-please-ack).
 
 ## Drawbacks
 

>>>>>>>> Changed protocol: features/0360-use-did-key, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/features/0360-use-did-key/README.md b/features/0360-use-did-key/README.md
index 76d30de..c927fe0 100644
--- a/features/0360-use-did-key/README.md
+++ b/features/0360-use-did-key/README.md
@@ -27,7 +27,7 @@ Note that simply knowing the key type is not necessarily sufficient to be able t
 
 ## Tutorial
 
-An example of the use of the replacement of a verkey with `did:key` can be found in the [~service decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/master/features/0056-service-decorator). Notably in the example at the beginning of the [tutorial](https://github.com/hyperledger/aries-rfcs/tree/master/features/0056-service-decorator#tutorial) section, the verkeys in the `recipientKeys` and `routingKeys` items would be changed from native keys to use `did:key` as follows:
+An example of the use of the replacement of a verkey with `did:key` can be found in the [~service decorator RFC](https://github.com/hyperledger/aries-rfcs/tree/main/features/0056-service-decorator). Notably in the example at the beginning of the [tutorial](https://github.com/hyperledger/aries-rfcs/tree/main/features/0056-service-decorator#tutorial) section, the verkeys in the `recipientKeys` and `routingKeys` items would be changed from native keys to use `did:key` as follows:
 
 ``` jsonc
 {
@@ -57,17 +57,17 @@ The `did:key` method uses the strings that are the DID, public key and key type
 
 The following currently implemented RFCs would be affected by acceptance of this RFC. In these RFCs, the JSON items that currently contain naked public keys (mostly the items `recipientKeys` and `routingKeys`) would be changed to use `did:key` references where applicable. Note that in these items public DIDs could also be used if applicable for a given use case.
 
-- [0023-did-exchange](https://github.com/hyperledger/aries-rfcs/tree/master/features/0023-did-exchange) - Invitation Message
-- [0028-introduce](https://github.com/hyperledger/aries-rfcs/tree/master/features/0028-introduce)
-- [0056-service-decorator](https://github.com/hyperledger/aries-rfcs/tree/master/features/0056-service-decorator)
-- [0160-connection-protocol](https://github.com/hyperledger/aries-rfcs/tree/master/features/0160-connection-protocol)
-- [0434-out-of-band-protocols](https://github.com/hyperledger/aries-rfcs/blob/master/features/0434-outofband/README.md)
-- [0211-mediator-coordination-protocol](https://github.com/hyperledger/aries-rfcs/blob/master/features/0211-route-coordination/README.md)
+- [0023-did-exchange](https://github.com/hyperledger/aries-rfcs/tree/main/features/0023-did-exchange) - Invitation Message
+- [0028-introduce](https://github.com/hyperledger/aries-rfcs/tree/main/features/0028-introduce)
+- [0056-service-decorator](https://github.com/hyperledger/aries-rfcs/tree/main/features/0056-service-decorator)
+- [0160-connection-protocol](https://github.com/hyperledger/aries-rfcs/tree/main/features/0160-connection-protocol)
+- [0434-out-of-band-protocols](https://github.com/hyperledger/aries-rfcs/blob/main/features/0434-outofband/README.md)
+- [0211-mediator-coordination-protocol](https://github.com/hyperledger/aries-rfcs/blob/main/features/0211-route-coordination/README.md)
 
 Service entries in `did:peer` DIDDocs (such as in RFCs
-[0094-cross-domain-messaging](https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0094-cross-domain-messaging)
+[0094-cross-domain-messaging](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0094-cross-domain-messaging)
 and
-[0067-didcomm-diddoc-conventions](https://github.com/hyperledger/aries-rfcs/tree/master/features/0067-didcomm-diddoc-conventions))
+[0067-didcomm-diddoc-conventions](https://github.com/hyperledger/aries-rfcs/tree/main/features/0067-didcomm-diddoc-conventions))
 should **NOT** use a `did:key` public key representation. Instead, service
 entries in the DIDDoc should reference keys defined internally in the DIDDoc
 where appropriate.




>>>>>>>> Changed protocol: features/0211-route-coordination, latest commit to protocol: 55e1e1c6e339ef0843268b4f3349b95cb7bd49a5

diff --git a/features/0211-route-coordination/README.md b/features/0211-route-coordination/README.md
index 0741aa7..c73b76f 100644
--- a/features/0211-route-coordination/README.md
+++ b/features/0211-route-coordination/README.md
@@ -200,3 +200,4 @@ The following lists the implementations (if any) of this RFC. Please do a pull r
 Name / Link | Implementation Notes
 --- | ---
 [Aries Cloud Agent - Python](https://github.com/hyperledger/aries-cloudagent-python/blob/main/Mediation.md) | Added in ACA-Py 0.6.0 [MISSING test results](/tags.md#test-anomaly)****
+[DIDComm mediator](https://github.com/Sirius-social/didcomm-mediator) | Open source cloud-based mediator.

>>>>>>>> Changed protocol: concepts/0441-present-proof-best-practices, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

diff --git a/concepts/0441-present-proof-best-practices/README.md b/concepts/0441-present-proof-best-practices/README.md
index 1073f6c..92e4468 100644
--- a/concepts/0441-present-proof-best-practices/README.md
+++ b/concepts/0441-present-proof-best-practices/README.md
@@ -103,7 +103,7 @@ are semantically equivalent.
 
 ##### Verifier Non-Revocation Interval Formulation
 
-The verifier MUST specify, as current [INDY-HIPE 11](https://github.com/hyperledger/indy-hipe/blob/master/text/0011-cred-revocation/README.md) notes, the same integer EPOCH time for both ends of the interval, or else omit the `"from"` key and value. In effect, where the presentation request specifies a non-revocation interval, the verifier MUST request a non-revocation instant.
+The verifier MUST specify, as current [INDY-HIPE 11](https://github.com/hyperledger/indy-hipe/blob/main/text/0011-cred-revocation/README.md) notes, the same integer EPOCH time for both ends of the interval, or else omit the `"from"` key and value. In effect, where the presentation request specifies a non-revocation interval, the verifier MUST request a non-revocation instant.
 
 ##### Prover Non-Revocation Interval Processing
 
@@ -164,7 +164,7 @@ When constructing a proof request, the verifier SHOULD express the minimum/maxim
 ## Reference
 
 * [RFC 0037](../../features/0037-present-proof/README.md): Present Proof protocol
-* [INDY-HIPE 11](https://github.com/hyperledger/indy-hipe/blob/master/text/0011-cred-revocation/README.md): Indy revocation.
+* [INDY-HIPE 11](https://github.com/hyperledger/indy-hipe/blob/main/text/0011-cred-revocation/README.md): Indy revocation.
 
 ## Implementations
 

[swcurran]

This same activity could be done for AIP 1.0 links, but I suspect only one (0050 Wallet) will contain ONLY "main" branch URL updates. After this PR is merged, the following AIP 2.0 links could be updated (in a follow up PR), but would need a more substantive discussion.

>>>>>>>> Changed protocol: features/0025-didcomm-transports, latest commit to protocol: f39481e92ad1a10dbc499cd4931a08c3497cee3f
>>>>>>>> Changed protocol: features/0434-outofband, latest commit to protocol: 9091848746e68416f1ddd2718314c1185a3900ae
>>>>>>>> Changed protocol: features/0454-present-proof-v2, latest commit to protocol: 8d798766e06ecdf997a62d4ad3c462c2af400ceb
>>>>>>>> Changed protocol: features/0587-encryption-envelope-v2, latest commit to protocol: 4e78319e5f79df2003ddf37f8f497d0fae20cc63

[TimoGlastra]

LGTM