[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [ldapext] Kerberos Integrity behavior

To: <ldapext@ietf.org>
Subject: Re: [ldapext] Kerberos Integrity behavior
From: "David Boreham" <david_list@boreham.org>
Date: Mon, 15 Nov 2004 07:38:26 -0800
Cc: Alexey Melnikov <Alexey.Melnikov@isode.com>
References: <OF334BEA2C.2EE6EED0-ON86256F4A.0065DCAF-86256F4A.00667FF1@us.ibm.com><1c1001c4c8eb$5991e5a0$da529145@mtbrook.bozemanpass.com> <4198C40D.6080007@isode.com>

I am wondering if RFC 2222bis (SASL) has to be clarified in this area?


It says "is processed by the security layer into buffers of protected data."

I think it would be reasonable to add something to the effect that
the buffering can be done without regard to any PDU, packet,
message or other delimiters present in the protocol stream.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext

References:
- [ldapext] Kerberos Integrity behavior
  - From: John McMeeking <jmcmeek@us.ibm.com>
- Re: [ldapext] Kerberos Integrity behavior
  - From: "David Boreham" <david_list@boreham.org>
- Re: [ldapext] Kerberos Integrity behavior
  - From: Alexey Melnikov <Alexey.Melnikov@isode.com>

Prev by Date: Re: [ldapext] Password Policy OIDs
Next by Date: [ldapext] Password Policy operational attributes
Index(es):
- Chronological
- Thread