Re: [radext] #146: Terminology and RFC 6365

Sam Hartman <hartmans@painless-security.com> Fri, 18 October 2013 15:01 UTC

Return-Path: <hartmans@painless-security.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6662111E82CB for <radext@ietfa.amsl.com>; Fri, 18 Oct 2013 08:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 ge7hh3ZoywGi for <radext@ietfa.amsl.com>; Fri, 18 Oct 2013 08:01:12 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE4A21F8F9A for <radext@ietf.org>; Fri, 18 Oct 2013 08:01:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 6C193204F9; Fri, 18 Oct 2013 10:59:22 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTlHZyemaliA; Fri, 18 Oct 2013 10:59:20 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 18 Oct 2013 10:59:20 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2594F83781; Fri, 18 Oct 2013 11:01:05 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Alan DeKok <aland@deployingradius.com>
References: <066.d7856f6a412e6225fc72caaacf5fd2b6@trac.tools.ietf.org> <081.5f9e1b3cafd15a1e03ba10b80f9a75fa@trac.tools.ietf.org> <baa0b0fa-cc44-4f7b-bc09-4cd8eb42aa16@email.android.com> <525FD54A.1080202@deployingradius.com>
Date: Fri, 18 Oct 2013 11:01:05 -0400
In-Reply-To: <525FD54A.1080202@deployingradius.com> (Alan DeKok's message of "Thu, 17 Oct 2013 08:17:14 -0400")
Message-ID: <tsleh7i39ou.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: bernard_aboba@hotmail.com, radext@ietf.org, radext issue tracker <trac+radext@trac.tools.ietf.org>
Subject: Re: [radext] #146: Terminology and RFC 6365
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 15:01:17 -0000

>>>>> "Alan" == Alan DeKok <aland@deployingradius.com> writes:

    Alan> Sam Hartman wrote:
    >> It does not make sense to close an issue if you are still waiting
    >> for input

    Alan>   I think this comment was about the normalization issue.

    Alan>   The text in the current draft addresses Bernards comments
    Alan> directly.  It's the best we can do given our current
    Alan> knowledge.  So IMHO, the issue should be closed.

    Alan>   We could track a separate issue to "get feedback from i18n
    Alan> people".  But that's already on my short list for Vancouver.
    Alan> As soon as I get an answer, I'll report it to the list, and do
    Alan> a final update of the document.

I think I'd be fine with a new issue opened to track i18n review.
I agree additional review is required and don't believe we're done until
 we get that review.