Re: [AAA-DOCTORS] [radext] RFC 6158 Reviews: how does it work in practice?
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 10 January 2012 20:03 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@ietfa.amsl.com
Delivered-To: aaa-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5DAA21F882D; Tue, 10 Jan 2012 12:03:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.312
X-Spam-Level:
X-Spam-Status: No, score=-103.312 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 kwuH449YB6MC; Tue, 10 Jan 2012 12:03:25 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 80ADF1F0C41; Tue, 10 Jan 2012 12:03:24 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAPyYDE/GmAcF/2dsb2JhbAA5CqxagQWBcgEBAQEDAQEBDwoRAzcHCwwEAgEIDQQEAQEBCgYMDAYBJigIAQEEARIIGodgm0ibJQSIVoJaYwSIB5J2jEo
X-IronPort-AV: E=Sophos; i="4.71,489,1320642000"; d="scan'208,217"; a="285598778"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jan 2012 15:03:22 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 10 Jan 2012 14:59:02 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCCFD2.E67F2165"
Date: Tue, 10 Jan 2012 21:03:20 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040153198C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [radext] RFC 6158 Reviews: how does it work in practice?
Thread-Index: AczP0WVUyRyUfU8NT4GUZo2TzzLlNgAAK72m
References: <BLU152-W6235FB1671EB3578461C7893990@phx.gbl><BLU152-W620A82A68D4AC6C485B60E93990@phx.gbl> <4F0C96D1.4090609@deployingradius.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Alan DeKok <aland@deployingradius.com>, Bernard Aboba <bernard_aboba@hotmail.com>
Cc: aaa-doctors@ietf.org, radext@ietf.org
Subject: Re: [AAA-DOCTORS] [radext] RFC 6158 Reviews: how does it work in practice?
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jan 2012 20:03:26 -0000
Yes. The AAA-Doctors team secretary should scan all documents that enter IETF Last Call and identify those who have any trace of RADIUS/Diameter/other_AAA content, and then dispatch them to the AAA-Doctors team for review according to some algorithm of his own. OPS-DIR use this method and it works pretty well for them. It's still best-effort, as all volunteer work we do in the IETF. Dan -----Original Message----- From: radext-bounces@ietf.org on behalf of Alan DeKok Sent: Tue 1/10/2012 9:51 PM To: Bernard Aboba Cc: radext@ietf.org Subject: Re: [radext] RFC 6158 Reviews: how does it work in practice? Bernard Aboba wrote: > [BA] How do we ensure that these reviews are actually carried out? cron? $ rsync -avz --delete ftp.rfc-editor.org::internet-drafts . $ perl -ne 'next if !/^draft-ietf-/;next if /^draft-ietf-radext/;next if /^draft-ietf-dime/;chop;split;next if ($_[2] eq "RFC");next if ($_[2] eq "Expired");next if ! -f "$_[0].txt";print $_[0],".txt\n";' < all_id.txt > radius.txt $ for x in `cat radius.txt`; do \ egrep -l RADIUS $x >> radext-review.txt; \ done That gives us a list (below). We could post the list once a month to radext and aaa-doctors. That would at least ensure the documents get noted in IESG review, or IETF last call. draft-ietf-emu-eaptunnel-req-09.txt draft-ietf-mip4-generic-notification-message-16.txt draft-ietf-mip6-bootstrapping-integrated-dhc-06.txt draft-ietf-mip6-hiopt-17.txt draft-ietf-netconf-access-control-07.txt draft-ietf-netext-radius-pmip6-06.txt draft-ietf-softwire-dslite-radius-ext-07.txt draft-ietf-abfab-aaa-saml-02.txt draft-ietf-abfab-arch-00.txt draft-ietf-abfab-gss-eap-04.txt draft-ietf-abfab-gss-eap-naming-01.txt draft-ietf-emu-chbind-12.txt draft-ietf-emu-eap-tunnel-method-01.txt draft-ietf-geopriv-held-measurements-04.txt draft-ietf-hokey-rfc5296bis-06.txt draft-ietf-karp-ops-model-01.txt draft-ietf-nea-pt-tls-01.txt draft-ietf-opsawg-management-stds-03.txt draft-ietf-precis-framework-01.txt draft-ietf-softwire-6rd-radius-attrib-04.txt draft-ietf-softwire-dslite-deployment-01.txt draft-ietf-storm-iscsi-cons-04.txt Alan DeKok. _______________________________________________ radext mailing list radext@ietf.org https://www.ietf.org/mailman/listinfo/radext
- Re: [AAA-DOCTORS] [radext] RFC 6158 Reviews: how … Romascanu, Dan (Dan)