diff --git a/draft-ymbk-sidrops-rpki-has-no-identity.xml b/draft-ymbk-sidrops-rpki-has-no-identity.xml
index b01edb9..881a363 100644
--- a/draft-ymbk-sidrops-rpki-has-no-identity.xml
+++ b/draft-ymbk-sidrops-rpki-has-no-identity.xml
@@ -35,12 +35,12 @@
Vigil Security, LLC
- 516 Dranesville Road
- Herndon
- VA
- 20170
- USA
-
+ 516 Dranesville Road
+ Herndon
+ VA
+ 20170
+ USA
+
housley@vigilsec.com
@@ -59,11 +59,12 @@
- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
- "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
- "OPTIONAL" in this document are to be interpreted as described in
- BCP 14 when,
- and only when, they appear in all capitals, as shown here.
+ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
+ NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
+ "MAY", and "OPTIONAL" in this document are to be interpreted as
+ described in BCP 14 when, and only when, they appear in all capitals,
+ as shown here.
@@ -106,7 +107,7 @@
The RPKI was designed and specified to sign certificates for use
- within the RPKI itself and to generate Route Origin Authorizations
+ within the RPKI itself and to generate Route Origin Authorizations
(ROAs), , for use in routing. It's design
intentionally precluded use for attesting to real world identity as,
among other issues, it would expose the Certification Authority (CA)