IETF Logo Mail Archive

Re: [kitten] Alexey's comments Re: WGLC of draft-ietf-kitten-sasl-oauth-18

Alexey Melnikov <alexey.melnikov@isode.com> Sun, 04 January 2015 11:37 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF1D51A8739 for <kitten@ietfa.amsl.com>; Sun, 4 Jan 2015 03:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.111
X-Spam-Level:
X-Spam-Status: No, score=-0.111 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwLFGn906b_Z for <kitten@ietfa.amsl.com>; Sun, 4 Jan 2015 03:37:41 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9011A8710 for <kitten@ietf.org>; Sun, 4 Jan 2015 03:37:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1420371460; d=isode.com; s=selector; i=@isode.com; bh=afhGWEGTJ1ILPNykr2RSMrJHpxwQCjsYHg7Ij6V89IU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=SCNH2V2plSLhkbq5vVOc7qhieV+5C0ZluMjw/AEveAExPSOrg6vvxB8zQWp4yYtZym0wO9 QHHAHRaL+Bwl0Eq/niI1Kav9OIh73jN8soe8G/ihrpQkHS2M78JrnCOHxob6pUZtTyW1/Y wzy3svBl/9tbg6JzHFNXctH6bXVJZ+U=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <VKkmAwAKaEH-@waldorf.isode.com>; Sun, 4 Jan 2015 11:37:40 +0000
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (12B435)
In-Reply-To: <377717803.3860512.1420246607276.JavaMail.yahoo@jws10611.mail.bf1.yahoo.com>
Date: Sun, 04 Jan 2015 11:42:22 +0000
Message-Id: <F4209A2F-CEB5-498B-9DA9-1C4628C64BE4@isode.com>
References: <3D9D6627-F6B2-456C-9C24-F224989B1979@isode.com> <377717803.3860512.1420246607276.JavaMail.yahoo@jws10611.mail.bf1.yahoo.com>
To: Bill Mills <wmills_92105@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/iq5GQniAEM6xwdTAZqAnSb-c8l8
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] Alexey's comments Re: WGLC of draft-ietf-kitten-sasl-oauth-18
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jan 2015 11:37:43 -0000

Hi Bill,

> On 3 Jan 2015, at 00:56, Bill Mills <wmills_92105@yahoo.com> wrote:
> 
> 3.2.3 and an explicit message:  Long ago in the life of this doc I was told that some implementations may not support an empty message, so we put the single character message there to have an explicit payload.  I'm a bit leery of changing this now since there are implementations in play that use it this way.

I didn't suggest you should be sending empty message. I said you should be using SASL cancellation token, which is a mandatory RFC 4422 feature.

Any implementation would have to support this mode of operation anyway, because a SASL client can cancel any exchange.

v2.23.0 | Report a Bug | By Email