Discussion:
Don't Use Copy Control (1.3.6.1.4.1.4203.666.5.15 vs. 1.3.6.1.1.22)
Michael Ströder
2014-09-22 05:47:15 UTC
Permalink
HI!

Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.

Ciao, Michael.
Michael Ströder
2014-09-23 20:19:29 UTC
Permalink
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.
Filed ITS#7946 for that.

Ciao, Michael.
Howard Chu
2014-09-23 20:24:36 UTC
Permalink
Content preview: Michael Ströder wrote: > Michael Ströder wrote: >> Is there
any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use >> Copy
Control as defined in RFC 6171? Currently an experimental OpenLDAP .666 >>
OID s used which makes this control rather unusable outside OpenLDAP >> implementation.
[...]

Content analysis details: (-1.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
X-BeenThere: openldap-***@openldap.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OpenLDAP development discussion list <openldap-devel.openldap.org>
List-Unsubscribe: <http://www.openldap.org/lists/mm/options/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=unsubscribe>
List-Archive: <http://www.openldap.org/lists/openldap-devel/>
List-Post: <mailto:openldap-***@openldap.org>
List-Help: <mailto:openldap-devel-***@openldap.org?subject=help>
List-Subscribe: <http://www.openldap.org/lists/mm/listinfo/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 20:24:44 -0000
Post by Michael Ströder
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in 2.5.
2.4 releases are ended as of 2.4.40.
Post by Michael Ströder
Filed ITS#7946 for that.
Closing...
Post by Michael Ströder
Ciao, Michael.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Michael Ströder
2014-09-23 20:27:47 UTC
Permalink
Post by Howard Chu
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in 2.5.
2.4 releases are ended as of 2.4.40.
Why not in 2.4? RFC 6171 was published three years ago on Standards Track.

Ciao, Michael.
Howard Chu
2014-09-23 20:30:01 UTC
Permalink
Content preview: Michael Ströder wrote: > Howard Chu wrote: >> Michael Ströder
wrote: >>> Michael Ströder wrote: >>>> Is there any issue with using OID
1.3.6.1.1.22 as controlType for Don't Use >>>> Copy Control as defined in
RFC 6171? Currently an experimental OpenLDAP .666 >>>> OID s used which makes
this control rather unusable outside OpenLDAP >>>> implementation. >> >>
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in 2.5.
Post by Michael Ströder
2.4 releases are ended as of 2.4.40. > > Why not in 2.4? RFC 6171 was
published three years ago on Standards Track. [...]

Content analysis details: (-1.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
X-BeenThere: openldap-***@openldap.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OpenLDAP development discussion list <openldap-devel.openldap.org>
List-Unsubscribe: <http://www.openldap.org/lists/mm/options/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=unsubscribe>
List-Archive: <http://www.openldap.org/lists/openldap-devel/>
List-Post: <mailto:openldap-***@openldap.org>
List-Help: <mailto:openldap-devel-***@openldap.org?subject=help>
List-Subscribe: <http://www.openldap.org/lists/mm/listinfo/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 20:30:08 -0000
Post by Michael Ströder
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in 2.5.
2.4 releases are ended as of 2.4.40.
Why not in 2.4? RFC 6171 was published three years ago on Standards Track.
No idea. Must've fallen thru the cracks.
Post by Michael Ströder
Ciao, Michael.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Michael Ströder
2014-09-23 20:31:31 UTC
Permalink
Post by Howard Chu
Post by Michael Ströder
Post by Howard Chu
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for Don't Use
Copy Control as defined in RFC 6171? Currently an experimental OpenLDAP .666
OID s used which makes this control rather unusable outside OpenLDAP
implementation.
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in 2.5.
2.4 releases are ended as of 2.4.40.
Why not in 2.4? RFC 6171 was published three years ago on Standards Track.
No idea. Must've fallen thru the cracks.
IMO it should be in 2.4. Any issue with that?

Ciao, Michael.
Quanah Gibson-Mount
2014-09-23 20:37:32 UTC
Permalink
Content preview: --On Tuesday, September 23, 2014 11:31 PM +0200 Michael Ströder
Post by Michael Ströder
Howard Chu wrote: >>>> Michael Ströder wrote: >>>>> Michael Ströder
wrote: >>>>>> Is there any issue with using OID 1.3.6.1.1.22 as controlType
for >>>>>> Don't Use Copy Control as defined in RFC 6171? Currently an >>>>>>
experimental OpenLDAP .666 OID s used which makes this control >>>>>> rather
unusable outside OpenLDAP implementation. >>>> >>>> It's been 1.3.6.1.1.22
in git master since 2011. The change will be in >>>> 2.5. 2.4 releases are
ended as of 2.4.40. >>> >>> Why not in 2.4? RFC 6171 was published three
years ago on Standards >>> Track. >> >> No idea. Must've fallen thru the cracks.
Post by Michael Ströder
IMO it should be in 2.4. Any issue with that? [...]
Content analysis details: (-1.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-BeenThere: openldap-***@openldap.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OpenLDAP development discussion list <openldap-devel.openldap.org>
List-Unsubscribe: <http://www.openldap.org/lists/mm/options/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=unsubscribe>
List-Archive: <http://www.openldap.org/lists/openldap-devel/>
List-Post: <mailto:openldap-***@openldap.org>
List-Help: <mailto:openldap-devel-***@openldap.org?subject=help>
List-Subscribe: <http://www.openldap.org/lists/mm/listinfo/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Sep 2014 20:37:57 -0000

--On Tuesday, September 23, 2014 11:31 PM +0200 Michael Ströder
Post by Michael Ströder
Post by Howard Chu
Post by Michael Ströder
Is there any issue with using OID 1.3.6.1.1.22 as controlType for
Don't Use Copy Control as defined in RFC 6171? Currently an
experimental OpenLDAP .666 OID s used which makes this control
rather unusable outside OpenLDAP implementation.
It's been 1.3.6.1.1.22 in git master since 2011. The change will be in
2.5. 2.4 releases are ended as of 2.4.40.
Why not in 2.4? RFC 6171 was published three years ago on Standards Track.
No idea. Must've fallen thru the cracks.
IMO it should be in 2.4. Any issue with that?
2.4 is done. Howard already stated that.

--Quanah


--

Quanah Gibson-Mount
Server Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Michael Ströder
2014-09-23 20:43:35 UTC
Permalink
Post by Quanah Gibson-Mount
2.4 is done. Howard already stated that.
AFAICS 2.4.40 is not released yet.
And IIRC there were commits to RE24 after tagging 2.4.40.

Ciao, Michael.
Quanah Gibson-Mount
2014-10-31 00:38:12 UTC
Permalink
Content preview: --On Tuesday, September 23, 2014 11:43 PM +0200 Michael Ströder
<***@stroeder.com> wrote: > Quanah Gibson-Mount wrote: >> 2.4 is done.
Howard already stated that. > > AFAICS 2.4.40 is not released yet. > And
IIRC there were commits to RE24 after tagging 2.4.40. [...]

Content analysis details: (-1.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-Mailman-Approved-At: Fri, 31 Oct 2014 00:42:51 +0000
X-BeenThere: openldap-***@openldap.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OpenLDAP development discussion list <openldap-devel.openldap.org>
List-Unsubscribe: <http://www.openldap.org/lists/mm/options/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=unsubscribe>
List-Archive: <http://www.openldap.org/lists/openldap-devel/>
List-Post: <mailto:openldap-***@openldap.org>
List-Help: <mailto:openldap-devel-***@openldap.org?subject=help>
List-Subscribe: <http://www.openldap.org/lists/mm/listinfo/openldap-devel>,
<mailto:openldap-devel-***@openldap.org?subject=subscribe>
Errors-To: openldap-devel-***@openldap.org
Sender: "openldap-devel" <openldap-devel-***@openldap.org>
X-Spam-Score: -1.9 (-)
X-Spam-Report: Spam detection software, running on the system "gauss.openldap.net", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.

Content preview: --On Tuesday, September 23, 2014 11:43 PM +0200 Michael Ströder
<***@stroeder.com> wrote: > Quanah Gibson-Mount wrote: >> 2.4 is done.
Howard already stated that. > > AFAICS 2.4.40 is not released yet. > And
IIRC there were commits to RE24 after tagging 2.4.40. [...]

Content analysis details: (-1.9 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid

--On Tuesday, September 23, 2014 11:43 PM +0200 Michael Ströder
Post by Michael Ströder
Post by Quanah Gibson-Mount
2.4 is done. Howard already stated that.
AFAICS 2.4.40 is not released yet.
And IIRC there were commits to RE24 after tagging 2.4.40.
This has been committed to RE24 and will be part of 2.4.41.

--Quanah


--

Quanah Gibson-Mount
Server Architect
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration

Loading...