Re: [apps-discuss] Proposal for a Finance Area Mailing List

[=JeffH <[e-mail]>]

 > ============================================================
 >  Certain functionality required by modern financial systems is not
 >  presently available in open, legacy-free, adequately globalized
 >  protocols.
 >
 >  This functionality includes:
 >   * Settlement and reversal / cancellation term negotiation
 >   * Exchange rate negotiation
 >   * Latency calculation / negotiation
 >   * Fee, tax and discount calculation / negotiation
 >   * Arbitrary currency / asset support
 >   * Multi-currency / asset transaction support
 >   * Quotation support
 >   * Multiple settlement path support
 >   * Optional support for in-band settlement (sometimes known as DVP)
 >   * High precision decimal value support
 >   * Arbitrary financial settlement topology support
 >   * Arbitrary communications topology support
 >
 >  Given this situation, it makes sense to propose a legacy-free,
 >  adequately extensible protocol for internet-based financial exchange.
 > ============================================================

All of the above are application-specific, and can be conveyed IMHO over 
existing specified protocols.

So it isn't clear that the above /needs/ to be specified in the IETF. It can be 
done "anywhere".  (and I've been directly involved in efforts that were defined 
"elsewhere" and were layered over IETF protocols)

Again, the crux is whether you can get a critical mass of subject matter 
experts to convene wherever you decide to attempt to address the subject matter 
that concerns you.

You ought to go ask them if they're interested in working in the IETF context 
to address the above. Perhaps allocating an IETF mailing list and seeing who 
shows up and what occurs is one way to do that. But as far as I can tell, those 
folks are not at this time active participants overall in the IETF. Tho, 
perhaps I'm wrong, I dunno.

=JeffH

ps: with respect to IANA, one does /NOT/ need to be affiliated with the IETF in 
order to register things with IANA. I know this from personal experience in 
that I wrote and shepherded the registrations for 
"application/samlassertion+xml" and "application/samlmetadata+xml" from the 
context of the OASIS Security Services Technical Committee (SSTC).