diff options
author | Christian Grothoff <christian@grothoff.org> | 2020-11-17 13:50:11 +0100 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2020-11-17 13:50:11 +0100 |
commit | 6d32f55adbe7be445bf3e252043cba910d5ea03b (patch) | |
tree | df75bf6324ce8faa12fa0fe99c89b1b76974aeb2 /payto-payment-target-types | |
parent | aef5dac1c9a1945c1605a92f552d8a184d09e3ed (diff) | |
download | gana-6d32f55adbe7be445bf3e252043cba910d5ea03b.tar.gz gana-6d32f55adbe7be445bf3e252043cba910d5ea03b.zip |
register LDAP payment target type
Diffstat (limited to 'payto-payment-target-types')
-rw-r--r-- | payto-payment-target-types/ldap.txt | 75 | ||||
-rw-r--r-- | payto-payment-target-types/registry.rec | 4 |
2 files changed, 79 insertions, 0 deletions
diff --git a/payto-payment-target-types/ldap.txt b/payto-payment-target-types/ldap.txt new file mode 100644 index 0000000..bac0319 --- /dev/null +++ b/payto-payment-target-types/ldap.txt | |||
@@ -0,0 +1,75 @@ | |||
1 | # Payto Payment Target Type for LDAP addressing | ||
2 | |||
3 | ## Target Type "ldap" | ||
4 | |||
5 | Name: ldap | ||
6 | |||
7 | Description: Lightweight Directory Access Protocol (LDAP) | ||
8 | |||
9 | The path consists of two components: The routing server and the | ||
10 | Distinguished Name. | ||
11 | |||
12 | This is used for transfers within the SWIFT network or likewise | ||
13 | networks. Limitations on the length and character set of option | ||
14 | values are defined by the implementation of the handler. Language | ||
15 | tagging and internationalization of options are not supported. | ||
16 | |||
17 | The client MAY choose a different connection method than ldap for | ||
18 | passing the request to the routing server. If no routing server is | ||
19 | explicitly referenced, the request is routed to a server of the | ||
20 | client's choice. | ||
21 | |||
22 | |||
23 | Syntax: | ||
24 | |||
25 | payto-ldap-URI = "payto://ldap/" [host] "/" dn [ "?" opts ] | ||
26 | |||
27 | 'host' is defined in | ||
28 | [Section 5 of RFC 1738](https://tools.ietf.org/html/rfc1738#section-5). | ||
29 | |||
30 | 'dn' is an LDAP Distinguished Name using the string format | ||
31 | described in | ||
32 | [Section 3 of RFC 2253](https://tools.ietf.org/html/rfc2253#section-3) | ||
33 | |||
34 | 'opts' is defined in | ||
35 | [Section 2 of RFC 8905](https://tools.ietf.org/html/rfc8905#section-2). | ||
36 | |||
37 | |||
38 | Examples: | ||
39 | |||
40 | payto://ldap//cn=enitest,o=saaabebb,o=swift | ||
41 | payto://ldap//cn=the-nichname?amount=EUR:50 | ||
42 | payto://ldap/ldap.swift.com/cn=mx01,o=pqvbusda,o=swift | ||
43 | |||
44 | |||
45 | Motivation - not normative | ||
46 | |||
47 | Thy syntax is modeled after the LDAP URL Format | ||
48 | [RFC 2255](https://tools.ietf.org/html/rfc2255). | ||
49 | |||
50 | SWIFT uses several addressing methods in the message formats they define: | ||
51 | * Business Identifier Code (BIC), which is already defined in RFC 8905, | ||
52 | * Distinguished Name (DN) and | ||
53 | * Nickname - which can be an arbitrary string. | ||
54 | |||
55 | |||
56 | Contact: <mailto:ietf@pep.security> | ||
57 | |||
58 | |||
59 | Normative References | ||
60 | |||
61 | * [RFC 2253] Lightweight Directory Access Protocol (v3): UTF-8 String | ||
62 | Representation of Distinguished Names | ||
63 | <https://tools.ietf.org/html/rfc2253> | ||
64 | |||
65 | * [RFC 2255] The LDAP URL Format | ||
66 | <https://tools.ietf.org/html/rfc2255> | ||
67 | |||
68 | * [RFC 8905] The 'payto' URI Scheme for Payments | ||
69 | <https://tools.ietf.org/html/rfc8905> | ||
70 | |||
71 | Informative References | ||
72 | |||
73 | * Alliance Access 7.5 Configuration Guide. | ||
74 | Appendix A.2 "Message Formats", esp. A.2.6.3.9. "AddressInfo" | ||
75 | <https://www2.swift.com/knowledgecentre/publications/aa_7_5_conf_guid/1.0> | ||
diff --git a/payto-payment-target-types/registry.rec b/payto-payment-target-types/registry.rec index 730bc14..f91ab9c 100644 --- a/payto-payment-target-types/registry.rec +++ b/payto-payment-target-types/registry.rec | |||
@@ -33,3 +33,7 @@ Reference: RFC 8905 | |||
33 | 33 | ||
34 | Name: void | 34 | Name: void |
35 | Reference: RFC 8905 | 35 | Reference: RFC 8905 |
36 | |||
37 | Name: ldap | ||
38 | Reference: ldap.txt | ||
39 | Contact: ietf@pep.security | ||