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:41 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 E7F9B1A876C for <kitten@ietfa.amsl.com>; Sun, 4 Jan 2015 03:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.408
X-Spam-Level:
X-Spam-Status: No, score=-1.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, MIME_QP_LONG_LINE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 pe2-q20MsLI6 for <kitten@ietfa.amsl.com>; Sun, 4 Jan 2015 03:41:28 -0800 (PST)
Received: from waldorf.isode.com (ext-bt.isode.com [217.34.220.158]) by ietfa.amsl.com (Postfix) with ESMTP id 9BD881A8710 for <kitten@ietf.org>; Sun, 4 Jan 2015 03:41:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1420371687; d=isode.com; s=selector; i=@isode.com; bh=YiPVmPc4EfyNftEsb4a6BB9yU/6WxCpqP885bNvLTT4=; 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=r9IP1hdZWuKdRpT5eMa6RnE1bscroaLqVcXEaCn6NA2mYQj1HXuhOyGXT9H/GRSaqcNQx7 JwPKkHMe4/6V/nfFOEuf8j4cFwCK++RuDUMZox8BK/3tqzPePJ1F6uaxfIW8EfBZWU2crH X6GvIQoZZK62C5MtLSPdyb2mfW0b1EE=;
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 <VKkm5wAKaH8M@waldorf.isode.com>; Sun, 4 Jan 2015 11:41:27 +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:46:10 +0000
Message-Id: <78174425-E391-4E6D-85DD-99D3B3A715EC@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: multipart/alternative; boundary="Apple-Mail-81320BF5-E536-4662-8B48-BE6163C124A0"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/kitten/uWGvVh5gsQkxAuUdFfoEgafy-_o
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:41:30 -0000

Hi Bill,

> On 3 Jan 2015, at 00:56, Bill Mills <wmills_92105@yahoo.com> wrote:
> 
> On requiring TLS and adding STARTTLS to the examples: your'e not happy with the current "Note that line 	breaks are inserted for readability and the underlying TLS establishment is not shown either."?  I'd prefer to add text saying something like "These Bearer token examples assume encrypted transport, if the underlying connection is not already TLS then STARTTLS MUST be used as required in the Bearer Token specification.".

Yes, that would work and I think your expanded text is better.

>  I can also easily specify that this is IMAP over 995

993
> or SMTP over 465.

I suggest you don't do that, because neither port 993 nor 465 are registered with IANA. I know it is not your problem, but there is no point in potentially getting this document delayed by this.

v2.23.0 | Report a Bug | By Email