Re: [radext] Call for WG Adoption for draft-dekok-radext-nai-02; The Network Access Identifier

Benoit Claise <bclaise@cisco.com> Thu, 20 December 2012 16:17 UTC

Return-Path: <bclaise@cisco.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 C41E221F896B for <radext@ietfa.amsl.com>; Thu, 20 Dec 2012 08:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.368
X-Spam-Level:
X-Spam-Status: No, score=-10.368 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mx1FbJOT7pYp for <radext@ietfa.amsl.com>; Thu, 20 Dec 2012 08:17:31 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id D46A221F8972 for <radext@ietf.org>; Thu, 20 Dec 2012 08:17:30 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qBKGHOJ3007405; Thu, 20 Dec 2012 17:17:24 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qBKGHMO0025002; Thu, 20 Dec 2012 17:17:24 +0100 (CET)
Message-ID: <50D33A12.9040608@cisco.com>
Date: Thu, 20 Dec 2012 17:17:22 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Alan DeKok <aland@freeradius.org>
References: <0AA5F862-FC51-43E8-9099-2F3F15406164@gmail.com> <50CCB073.1090009@freeradius.org>
In-Reply-To: <50CCB073.1090009@freeradius.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: radext@ietf.org, "radext-chairs@tools.ietf.org" <radext-chairs@tools.ietf.org>, Jouni Korhonen <jounikor@gmail.com>
Subject: Re: [radext] Call for WG Adoption for draft-dekok-radext-nai-02; The Network Access Identifier
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, 20 Dec 2012 16:17:32 -0000

On 15/12/2012 18:16, Alan DeKok wrote:
> Jouni Korhonen wrote:
>> Folks,
>>
>> As discussed in Atlanta, we are ready to ask for the WG adoption of draft-dekok-radext-nai-02 (The Network Access Identifier "bis") starting today. The plan is that once we have had the adoption call finished we can move the document straight into WGLC (knowing there are already reviews done).
>>
>> The WG adoption call ends 20th Dec. This is a quick one week call since we have had the document around quite long already. If you have concerns against the document, raise them in the mailing list. Silence will be counted as acceptance. Of course folks are encouraged to endorse the document in the mailing list.
>    As discusses early, the document should be split in two.
Have we discussed this at the last meeting? I don't recall.
And the meeting minutes don't indicate this: 
http://www.ietf.org/proceedings/85/minutes/minutes-85-radext
We just rechartered to include THIS document, and the next thing is that 
we need to split it???

Regards, Benoit


>
>    My $0.02 is to accept the document as-is, rename it to
> draft-ietf-radext-naibis-00.txt, and then split it.
>
>    All of the RADIUS / Diameter text will then be removed, and placed
> into a second document: draft-iet-radext-naiusage-00.txt
>
>    The goal is to get the NAI-bis document published quickly.  Then,
> discuss the usage of NAI within RADIUS as a slightly longer-term project.
>
>    Alan DeKok.
>
>