Re: [radext] #162: Section 2.6
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Thu, 17 October 2013 00:09 UTC
Return-Path: <trac+radext@trac.tools.ietf.org>
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 C522C21F9A72 for <radext@ietfa.amsl.com>; Wed, 16 Oct 2013 17:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.874
X-Spam-Level:
X-Spam-Status: No, score=-100.874 tagged_above=-999 required=5 tests=[AWL=-0.575, BAYES_00=-2.599, MANGLED_NAIL=2.3, 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 s985oVcWaKUd for <radext@ietfa.amsl.com>; Wed, 16 Oct 2013 17:09:20 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBD011E8153 for <radext@ietf.org>; Wed, 16 Oct 2013 17:09:12 -0700 (PDT)
Received: from localhost ([127.0.0.1]:46690 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1VWb9I-0007Uz-O6; Thu, 17 Oct 2013 02:09:09 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: radext issue tracker <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-radext-nai@tools.ietf.org, aland@deployingradius.com
X-Trac-Project: radext
Date: Thu, 17 Oct 2013 00:09:08 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/radext/trac/ticket/162#comment:1
Message-ID: <081.43eeef839b36be21c73a616b67aacfc1@trac.tools.ietf.org>
References: <066.aea3cacc2610a00b8086f12c64529e3a@trac.tools.ietf.org>
X-Trac-Ticket-ID: 162
In-Reply-To: <066.aea3cacc2610a00b8086f12c64529e3a@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-radext-nai@tools.ietf.org, aland@deployingradius.com, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: aland@freeradius.org
Resent-Message-Id: <20131017000913.1BBD011E8153@ietfa.amsl.com>
Resent-Date: Wed, 16 Oct 2013 17:09:12 -0700
Resent-From: trac+radext@trac.tools.ietf.org
Cc: radext@ietf.org
Subject: Re: [radext] #162: Section 2.6
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: radext@ietf.org
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 00:09:20 -0000
#162: Section 2.6 Changes (by aland@deployingradius.com) * status: new => closed * resolution: => fixed Comment: My approach would be to discuss the preferred design, and then explain why it's difficult to achieve. I would suggest splitting the section into two pieces. The first would discuss the ideal process. The second would discuss what we can do in reality. We're also waiting for input from i18n people on what's possible. Their answer will have a large impact on the text in this section. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-radext- bernard_aboba@hotmail.com | nai@tools.ietf.org Type: defect | Status: closed Priority: blocker | Milestone: milestone1 Component: nai | Version: 1.0 Severity: In WG Last Call | Resolution: fixed Keywords: | -------------------------------------+------------------------------------- Ticket URL: <http://tools.ietf.org/wg/radext/trac/ticket/162#comment:1> radext <http://tools.ietf.org/radext/>
- [radext] #162: Section 2.6 radext issue tracker
- Re: [radext] #162: Section 2.6 radext issue tracker