Re: [apps-discuss] WGLC on draft-ietf-appsawg-rfc5451bis-00

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 14 May 2013 16:33 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872A321F8B90 for <apps-discuss@ietfa.amsl.com>; Tue, 14 May 2013 09:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.601
X-Spam-Level:
X-Spam-Status: No, score=-101.601 tagged_above=-999 required=5 tests=[AWL=-0.999, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_66=0.6, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VP15XM1zziEp for <apps-discuss@ietfa.amsl.com>; Tue, 14 May 2013 09:33:20 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 0300821F84AD for <apps-discuss@ietf.org>; Tue, 14 May 2013 09:33:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1368549199; d=isode.com; s=selector; i=@isode.com; bh=KEP1JMfOcB1dYLPR/3ZqyK7QqQaoQC7TIw6pk/0TgzM=; 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=UY0aLN2MULMjqgHjHV64kBngGtI4bVKyTTCuMgeOp0cKlhQy22Ie6bcEiaL5deQeB2UAa6 OM/f/Y5EXzajCoHGw+LeINQGrH8DszxmL0VMnlgrnsBneFT82w7Bn2mD2tW4jc4BsbUBcx Fsk+CvJYpeWmnCYv9KnEPWUjW1E7iqg=;
Received: from [172.17.128.24] (richard.isode.com [62.3.217.249]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <UZJnTgA6F7g7@statler.isode.com>; Tue, 14 May 2013 17:33:18 +0100
References: <6.2.5.6.2.20130503141649.0d8252f0@elandnews.com> <51923CFB.8090702@isode.com> <CAL0qLwbF3CUfChe9C2yASW_FaOtEQwVA7+vyrU2OKpXbdXzZyw@mail.gmail.com>
In-Reply-To: <CAL0qLwbF3CUfChe9C2yASW_FaOtEQwVA7+vyrU2OKpXbdXzZyw@mail.gmail.com>
Message-Id: <67D63FBF-D54E-4C99-9A5C-F74FDD635226@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Tue, 14 May 2013 17:36:46 +0100
To: "Murray S. Kucherawy" <superuser@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-2B5F06DD-5828-4731-A959-04280162F15B
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] WGLC on draft-ietf-appsawg-rfc5451bis-00
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 16:33:25 -0000

On 14 May 2013, at 17:11, "Murray S. Kucherawy" <superuser@gmail.com> wrote:

> On Tue, May 14, 2013 at 6:32 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
>  
> In Section 2.5.4:
> 
>  LDAP needs an Informative Reference.
> 
> Are we sure about that?  It's just an example of a related service that might cause a temperror for SMTP AUTH.  I could change it to "a directory service" to avoid having to make that reference.  LDAP's not important to this specification in any way.  I'll do that, actually.

I don't particularly care. Any protocol you mention needs a reference though.

> 2.5.5.  Extension Result Codes
> 
>    Additional result codes (extension results) might be defined in the
>    future by later revisions or extensions to this specification.
>    Result codes MUST be registered with the Internet Assigned Numbers
>    Authority (IANA) and preferably published in an RFC.  See Section 6
>    for further details.
> 
>    Extension results MUST only be used within ADMDs that have explicitly
>    consented to use them.  These results and the parameters associated
>    with them are not formally documented.  Therefore, they are subject
>    to change at any time and not suitable for production use.  Any MTA,
>    MUA or downstream filter intended for production use SHOULD ignore or
>    delete any Authentication-Results header field that includes an
>    extension result.
> 
> I am mostly curious to see some examples of such extensions.
> 
> You could make one up and imagine using it.  Barry likes "banana", so:
> 
> Authentication-Results: your.example.com; banana=foobar

Ok. Are there many of these in the wild?