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

Alan DeKok <aland@deployingradius.com> Thu, 17 October 2013 12:18 UTC

Return-Path: <aland@deployingradius.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 B23D111E81B9 for <radext@ietfa.amsl.com>; Thu, 17 Oct 2013 05:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 laWebthKwrao for <radext@ietfa.amsl.com>; Thu, 17 Oct 2013 05:17:59 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A14511E81B5 for <radext@ietf.org>; Thu, 17 Oct 2013 05:17:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 0CCE02240130; Thu, 17 Oct 2013 14:17:06 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ko-DXKIgkNda; Thu, 17 Oct 2013 14:17:05 +0200 (CEST)
Received: from Thor-2.local (bas1-ottawa11-1176121002.dsl.bell.ca [70.26.46.170]) by power.freeradius.org (Postfix) with ESMTPSA id 5698322400E2; Thu, 17 Oct 2013 14:17:05 +0200 (CEST)
Message-ID: <525FD54A.1080202@deployingradius.com>
Date: Thu, 17 Oct 2013 08:17:14 -0400
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Sam Hartman <hartmans@painless-security.com>
References: <066.d7856f6a412e6225fc72caaacf5fd2b6@trac.tools.ietf.org> <081.5f9e1b3cafd15a1e03ba10b80f9a75fa@trac.tools.ietf.org> <baa0b0fa-cc44-4f7b-bc09-4cd8eb42aa16@email.android.com>
In-Reply-To: <baa0b0fa-cc44-4f7b-bc09-4cd8eb42aa16@email.android.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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: Thu, 17 Oct 2013 12:18:05 -0000

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

  I think this comment was about the normalization issue.

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

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

  Alan DeKok.