RE: [Gen-art] Gen-ART review of draft-ietf-mip4-radius-requirements-03.txt
"Avi Lior" <avi@bridgewatersystems.com> Thu, 21 June 2007 13:57 UTC
Return-path: <gen-art-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1NAP-00060L-Lg; Thu, 21 Jun 2007 09:57:45 -0400
Received: from gen-art by megatron.ietf.org with local (Exim 4.43) id 1I1NAO-00060G-J1 for gen-art-confirm+ok@megatron.ietf.org; Thu, 21 Jun 2007 09:57:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1NAO-000608-9e for gen-art@ietf.org; Thu, 21 Jun 2007 09:57:44 -0400
Received: from bws14.bridgewatersystems.com ([216.113.7.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1NAK-0000wL-U6 for gen-art@ietf.org; Thu, 21 Jun 2007 09:57:44 -0400
MIME-Version: 1.0
Subject: RE: [Gen-art] Gen-ART review of draft-ietf-mip4-radius-requirements-03.txt
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 09:57:27 -0400
Message-ID: <E7CCE8A83907104ABEE91AC3AE3709A00DD6E9AA@exchange.bridgewatersys.com>
In-Reply-To: <467A76CE.3080704@piuha.net>
References: <46730513.3030503@lucent.com> <467A76CE.3080704@piuha.net>
From: Avi Lior <avi@bridgewatersystems.com>
To: Jari Arkko <jari.arkko@piuha.net>, "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: kchowdhury@starentnetworks.com, kleung@cisco.com, henrik@levkowetz.com, mccap@petoni.org, gen-art@ietf.org, mnakhjiri@huawei.com
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org
I am okay with that. Regarding the last comment though. It may not be always REQUIRED that the FA operate as a RADIUS Client (or NAS). I think the ultimate solution will allow for a couple of different scenarios. I don't want to be bound to that statement. So I don't know if we need to make changes to this document. Just as an example, if we use proxy mobile IP4, then the FA does not need to make a AAA dip. Similarly, if we bootstrap MIP type information during access authentication, then the FA does not need to make a AAA dip. -----Original Message----- From: Jari Arkko [mailto:jari.arkko@piuha.net] Sent: Thursday, June 21, 2007 9:02 AM To: Vijay K. Gurbani Cc: mnakhjiri@huawei.com; kchowdhury@starentnetworks.com; Avi Lior; kleung@cisco.com; gen-art@ietf.org; henrik@levkowetz.com; mccap@petoni.org Subject: Re: [Gen-art] Gen-ART review of draft-ietf-mip4-radius-requirements-03.txt Authors, I would like to take these comments directly as instructions for the RFC Editor. If there's any objection, let me know. Jari Vijay K. Gurbani kirjoitti: > I have been selected as the General Area Review Team (Gen-ART) > reviewer for this draft (for background on Gen-ART, please see > http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). > > Please wait for direction from your document shepherd or AD before > posting a new version of the draft. > > Document: draft-ietf-mip4-radius-requirements-03.txt > Reviewer: Vijay K. Gurbani > Review Date: 15 Jun 2007 > IESG Telechat date: 21 Jun 2007 > > Summary: This draft is ready for publication as an Informational. > Three nits: > > 1) Section 1: s/[RFC3957] all based/[RFC3957], all based > (The comma improves readibility) > > 2) Section 3: s/reqiuired/required > > 3) Section 3.1: In the first and third bullet item, it appears > appropriate that the word "required" be upper-cased to denote its use > as a normative declaration. More so since bullet item two contains > the word "MUST" in normative fashion. I believe that the authors are > making a normative set of declarations for the goals, so it appears > uneven to have a MUST in the second bullet item and not a pair of > REQUIREDs in the other two bullets. > > Thanks, > > - vijay _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-ietf-mip4-radiu… Vijay K. Gurbani
- Re: [Gen-art] Gen-ART review of draft-ietf-mip4-r… Jari Arkko
- RE: [Gen-art] Gen-ART review of draft-ietf-mip4-r… Avi Lior
- RE: [Gen-art] Gen-ART review of draft-ietf-mip4-r… Madjid Nakhjiri