ise mail draft

1 files changed, 50 insertions, 0 deletions

diff --git a/standards/rfc-ise.txt b/standards/rfc-ise.txt
new file mode 100644
index 0000000..f515244
--- /dev/null
+++ b/standards/rfc-ise.txt
@@ -0,0 +1,50 @@
+To: rfc-ise@rfc-editor.org
+
+Dear IS Editor,
+
+This is a message for the submission of draft-dold-payto to the
+independent stream.  We intend this to be an experimental RFC.
+
+Previous drafts have seen review by the IETF communities, and we
+addressed the various comments we have received. As no WG was
+happy to pick up the topic, IESG/ADs suggested to us that we submit
+this to the independent stream, in particular to generate an FCFS
+registry at IANA and to hopefully inspire more parties to implement
+the scheme and gain more implementation experience as a community.
+
+
+First, there were discussions on [uri-review], starting April 30th 2017:
+https://mailarchive.ietf.org/arch/msg/uri-review/YFzsOq9kbU4Lt7IV9QWwnuVzDaw
+
+A second round of reviews happened in April 2018:
+https://mailarchive.ietf.org/arch/msg/uri-review/D_IeQiXnWzT53dCPCh13zXR6LC4
+
+Next, RFC editor privided an independent technical review as
+well (private e-mail, IANA #1133677, via Amanda Baber).
+
+Finally, there was a recent discussion on [Dispatch]:
+https://mailarchive.ietf.org/arch/msg/dispatch/nERmRZ8AtDQLSo1KMW-4W6zmvFo
+
+We believe to have adequately addressed the comments received
+at this time (as well as other comments received in private).
+
+
+We assert that the IANA allocation of payto:// does not require
+IETF consensus or standards action. In fact, we believe the
+allocation is already in effect.
+
+
+The purpose of publishing the document is to create a uniform standard
+for the specification of pro-forma invoices that allows the invocing
+party to specify account details, amounts and other wire-transfer meta
+data.  We believe this standard is urgently needed, and have had
+discussions with various parties in the financial industry that support
+this assertion. We also implemented this in our own payment system.
+
+The intended audience are thus developers for applications that deal
+with payments and are seeking a simple standard for specifying wire
+transfer information.
+
+Best regards,
+
+Florian & Christian