Re: DBIS commentary
Jordan Brown <[email protected]> Wed, 2 Dec 2015 08:39:14 -0800
| Newsgroups | gmane.ietf.ldapext |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============8209660321982460555==
Content-Type: multipart/alternative;
boundary="------------060600090203030008030702"
This is a multi-part message in MIME format.
--------------060600090203030008030702
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
On 12/2/2015 12:59 AM, Bannister, Mark wrote:
>
> Jordan Brown wrote:
>
> > Do note again that RFC 4876 mapping would let you redirect the client=
s to use a custom
>
> > case-sensitive attribute, or attributes from different auxiliary clas=
ses.
>
> I should really have made it clear that DBIS supersedes RFC 4876, and i=
ntroduces=20
> more
>
> powerful mapping constructs. With DBIS, you can support an RFC2307 sch=
ema (case
>
> insensitive) and the DBIS schema (case sensitive) from the same client =
if you so=20
> choose,
>
> and at several levels. You could have groups of hosts with case sensit=
ive maps=20
> vs. groups
>
> of host with case insensitive maps. You could have a host where some m=
aps are case
>
> sensitive and some are not. You can even have parts of a map provided =
via one=20
> schema
>
> and parts from another, i.e. case sensitivity for some entries and inse=
nsitivity=20
> for others
>
> if that=E2=80=99s really what you wished to do. If you use DBIS, you c=
ertainly have no=20
> need to
>
> use RFC 4876.
>
Ah, indeed. So if there were case-sensitive and case-insensitive attribu=
tes=20
available (presumably in different auxiliary classes), you could use thos=
e mapping=20
constructs to choose the non-default variation.
It doesn't look like you've got 4876 completely covered, though. Attribut=
e mapping=20
is only one of the things it does - it also tells the clients which serve=
rs to=20
connect to and what authentication schemes to use. If you're replacing 4=
876,=20
there should be a plan for replacing that capability.
> Jordan Brown wrote:
>
> > Mark Bannister wrote:
>
> > > Btw, what was your plan for case sensitivity in filesystems?
>
> >
>
> > Baby steps :-)
>
> >
>
> > I do think that that's inevitable too, just not as soon as user names
>
> Wow. Good luck with that. (Boiling oceans comes to mind).
>
I work in name services, not file systems, so it's not an active project.=
I just=20
think it'll happen eventually, that interoperability with Windows will fo=
rce it.
--------------060600090203030008030702
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">On 12/2/2015 12:59 AM, Bannister, Mark
wrote:<br>
</div>
<blockquote
cite=3D"mid:[email protected].=
com"
type=3D"cite">
<!-- Template generated by Exclaimer Template Editor on 03:59:31 Wo=
ensdag, 2 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";}
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;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";
color:black;
mso-fareast-language:EN-GB;}
span.EmailStyle23
{mso-style-type:personal-reply;
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">
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">Jordan Brown wrote:<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> Do note again
that RFC 4876 mapping would let you redirect the clients to
use a custom<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> case-sensitive
attribute, or attributes from different auxiliary classes.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D"><o:p>=C2=A0</o:p></s=
pan></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">I should really have
made it clear that DBIS supersedes RFC 4876, and introduces
more<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">powerful mapping
constructs.=C2=A0 With DBIS, you can support an RFC2307 schem=
a
(case<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">insensitive) and the
DBIS schema (case sensitive) from the same client if you so
choose,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">and at several
levels.=C2=A0 You could have groups of hosts with case sensit=
ive
maps vs. groups<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">of host with case
insensitive maps.=C2=A0 You could have a host where some maps=
are
case<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">sensitive and some
are not.=C2=A0 You can even have parts of a map provided via =
one
schema<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">and parts from
another, i.e. case sensitivity for some entries and
insensitivity for others<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">if that=E2=80=99s re=
ally what
you wished to do.=C2=A0 If you use DBIS, you certainly have n=
o
need to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">use RFC 4876.</span>=
</p>
</div>
</blockquote>
<br>
Ah, indeed.=C2=A0 So if there were case-sensitive and case-insensitiv=
e
attributes available (presumably in different auxiliary classes),
you could use those mapping constructs to choose the non-default
variation.<br>
<br>
It doesn't look like you've got 4876 completely covered, though.=C2=A0
Attribute mapping is only one of the things it does - it also tells
the clients which servers to connect to and what authentication
schemes to use.=C2=A0 If you're replacing 4876, there should be a pla=
n
for replacing that capability.<br>
<br>
<blockquote
cite=3D"mid:[email protected].=
com"
type=3D"cite">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">Jordan Brown wrote:<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> Mark Bannister
wrote:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> > Btw, what
was your plan for case sensitivity in filesystems?<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> <o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> Baby steps :-)<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> <o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">> I do think that
that's inevitable too, just not as soon as user names<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D"><o:p>=C2=A0</o:p></s=
pan></p>
<p class=3D"MsoNormal"><span
style=3D"font-size:11.0pt;color:#1F497D">Wow.=C2=A0 Good luck=
with
that.=C2=A0 (Boiling oceans comes to mind).</span></p>
</div>
</blockquote>
<br>
I work in name services, not file systems, so it's not an active
project.=C2=A0 I just think it'll happen eventually, that
interoperability with Windows will force it.<br>
<br>
</body>
</html>
--------------060600090203030008030702--
--===============8209660321982460555==
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
--===============8209660321982460555==--