<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Names that have been proposed so far are:<o:p></o:p></p>
<p class="MsoNormal"> POST<o:p></o:p></p>
<p class="MsoNormal"> html_form<o:p></o:p></p>
<p class="MsoNormal"> html<o:p></o:p></p>
<p class="MsoNormal"> form_post<o:p></o:p></p>
<p class="MsoNormal">SAML calls this binding “HTTP POST” (see <a href="http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf">
http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf</a> Section 3.5).<o:p></o:p></p>
<p class="MsoNormal">WS-Federation doesn’t appear to explicitly name the binding (see
<a href="http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175014">
http://docs.oasis-open.org/wsfed/federation/v1.2/os/ws-federation-1.2-spec-os.html#_Toc223175014</a>) but also says that the HTTP form is sent via HTTP POST.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Given that colloquially, people tend to refer to this binding as a POST binding, I think we really want to keep POST in the name. I’ll grant Nat’s point that just “POST” is probably misleading. Therefore, I think we should choose from
among these names:<o:p></o:p></p>
<p class="MsoNormal"> form_post<o:p></o:p></p>
<p class="MsoNormal"> html_post<o:p></o:p></p>
<p class="MsoNormal"> http_post<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I prefer “form_post” from among these choices because it clearly differentiates it from just simply using the HTTP POST verb, by saying what is being posted. “html_post” is less specific and odd sounding. “http_post” sounds like we’re
just using the HTTP POST verb, and so is misleading in the same way that simply “POST” is.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So I’d choose “form_post”. Are people good with that, or do people want to advocate a different name? (If so, please say why.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>