Re: Case sensitivity of user/group names (was Re: DBIS commentary)

Jordan Brown <[email protected]> Thu, 3 Dec 2015 09:17:26 -0800
Newsgroups gmane.ietf.ldapext
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============7283413237735097314==
Content-Type: multipart/alternative;
 boundary="------------080309080407040105060800"

This is a multi-part message in MIME format.
--------------080309080407040105060800
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

[ Trying to keep case sensitivity discussions on their own thread ]

On 12/3/2015 2:42 AM, Bannister, Mark wrote:
>
> ... and let=E2=80=99s not also forget:
>
> http://pubs.opengroup.org/onlinepubs/000095399/xrat/xbd_chap04.html#tag=
_01_04_06
>
> I think some of the locale considerations given in these two links can =
be=20
> applied to the discussion
>
> of case insensitivity in LDAP attributes too.
>

If we were starting from NIS and /etc/passwd, yes.
If we were not concerned with directory interoperability between differen=
t=20
platforms, yes.
If we were not concerned with consistency with names as used in the rest =
of the=20
industry and in normal human practice, yes.

But none of those things are true.


--------------080309080407040105060800
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">[ Trying to keep case sensitivity
      discussions on their own thread ]<br>
      <br>
      On 12/3/2015 2:42 AM, Bannister, Mark wrote:<br>
    </div>
    <blockquote
cite=3D"mid:[email protected].=
com"
      type=3D"cite">
      <!-- Template generated by Exclaimer Template Editor on 05:42:56 Do=
nderdag, 3 Desember 2015 -->
      <style type=3D"text/css">P.ae8b49d9-d5d8-4b09-a975-5128f74bda5d {
	MARGIN: 0cm 0cm 0pt
}
LI.ae8b49d9-d5d8-4b09-a975-5128f74bda5d {
	MARGIN: 0cm 0cm 0pt
}
DIV.ae8b49d9-d5d8-4b09-a975-5128f74bda5d {
	MARGIN: 0cm 0cm 0pt
}
TABLE.ae8b49d9-d5d8-4b09-a975-5128f74bda5dTable {
	MARGIN: 0cm 0cm 0pt
}
DIV.Section1 {
	page: Section1
}
</style>
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DU=
TF-8">
      <meta name=3D"Generator" content=3D"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:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
	{mso-style-priority:1;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
span.Code
	{mso-style-name:Code;
	mso-style-priority:1;
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";
	color:black;}
p.ae8b49d9-d5d8-4b09-a975-5128f74bda5d, li.ae8b49d9-d5d8-4b09-a975-5128f7=
4bda5d, div.ae8b49d9-d5d8-4b09-a975-5128f74bda5d
	{mso-style-name:ae8b49d9-d5d8-4b09-a975-5128f74bda5d;
	mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.cafa858c-a64a-4018-b357-eb8084b6b267, li.cafa858c-a64a-4018-b357-eb8084=
b6b267, div.cafa858c-a64a-4018-b357-eb8084b6b267
	{mso-style-name:cafa858c-a64a-4018-b357-eb8084b6b267;
	mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle26
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
      <p>
      </p>
      <div class=3D"WordSection1">... and let=E2=80=99s not also forget:<=
o:p></o:p>
        <p class=3D"MsoPlainText"><a moz-do-not-send=3D"true"
href=3D"http://pubs.opengroup.org/onlinepubs/000095399/xrat/xbd_chap04.ht=
ml#tag_01_04_06">http://pubs.opengroup.org/onlinepubs/000095399/xrat/xbd_=
chap04.html#tag_01_04_06</a><o:p></o:p></p>
        <p class=3D"MsoPlainText"><o:p>=C2=A0</o:p></p>
        <p class=3D"MsoPlainText">I think some of the locale
          considerations given in these two links can be applied to the
          discussion<o:p></o:p></p>
        <p class=3D"MsoPlainText">of case insensitivity in LDAP attribute=
s
          too.</p>
      </div>
    </blockquote>
    <br>
    If we were starting from NIS and /etc/passwd, yes.<br>
    If we were not concerned with directory interoperability between
    different platforms, yes.<br>
    If we were not concerned with consistency with names as used in the
    rest of the industry and in normal human practice, yes.<br>
    <br>
    But none of those things are true.<br>
    <br>
  </body>
</html>

--------------080309080407040105060800--


--===============7283413237735097314==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ldapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ldapext

--===============7283413237735097314==--