[Gen-art] Re: review of draft-ietf-rtgwg-rfc3682bis-09.txt

Pekka Savola <psavola@funet.fi> Mon, 11 June 2007 18:44 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 1Hxosn-0008HC-Tq; Mon, 11 Jun 2007 14:44:53 -0400
Received: from gen-art by megatron.ietf.org with local (Exim 4.43) id 1Hxosm-00080G-12 for gen-art-confirm+ok@megatron.ietf.org; Mon, 11 Jun 2007 14:44:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxosl-000804-NU for gen-art@ietf.org; Mon, 11 Jun 2007 14:44:51 -0400
Received: from smtp2.csc.fi ([193.166.3.97]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxosj-0003fv-8L for gen-art@ietf.org; Mon, 11 Jun 2007 14:44:51 -0400
Received: from imap1.csc.fi (imap1.csc.fi [193.166.7.56]) by smtp2.csc.fi (MAILSERVER) with ESMTP id l5BIhRU0026316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Jun 2007 21:43:29 +0300
Received: from myrsky.csc.fi (myrsky.csc.fi [193.166.7.58]) (authenticated as psavola) by imap1.csc.fi (MAILSERVER) with ESMTP id l5BIhQOa016673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 21:43:26 +0300
Date: Mon, 11 Jun 2007 21:43:26 +0300
From: Pekka Savola <psavola@funet.fi>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
In-Reply-To: <200706111617.l5BGH7pd039057@givry.fdupont.fr>
Message-ID: <Pine.LNX.4.62.0706112138100.28228@sampo3.csc.fi>
References: <200706111617.l5BGH7pd039057@givry.fdupont.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-CanItPRO-Stream: 00_Opt_Out (inherits from default)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: cpignata@cisco.com, gen-art@ietf.org, vijay@umbc.edu, dmm@1-4-5.net, heas@shrubbery.net, rcallon@juniper.net
Subject: [Gen-art] Re: review of draft-ietf-rtgwg-rfc3682bis-09.txt
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

Hi Francis,

Thanks for your review.  The draft does say 'obsoletes' in the Abstract 
and includes Appendix B on Changes since RFC 3682, but I guess we can say 
this explicitly.

Wrt. your TrustRadius comment, the intent was to say that you would 
accept any value within TrustRadius from 255.  I.e., with trustradius 1, 
255-1 = 254 would be OK.  The simplest possible fix would be replacing "of 
255" with "from 255", but I'm not sure whether that would be much clearer; 
in fact the whole "TrustRadius" concept could be reworded out of the text 
given that it isn't mentioned anywhere else (anymore)

The text was:

    The main applicability of GTSM is for directly connected peers.  GTSM
    could be used for non-directly connected sessions as well, where the
    recipient would check that the TTL is within "TrustRadius" (e.g., 1)
    of 255 instead of 255. [...]

On Mon, 11 Jun 2007, Francis Dupont wrote:
> 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 resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-rtgwg-rfc3682bis-09.txt
> Reviewer: Francis Dupont
> Review Date: 2007/06/10
> IETF LC End Date: 2007/06/15
> IESG Telechat date: not known
>
> Summary: Almost Ready
>
> Comments: I have only one major comment: the document does not explain
> it is a revision of RFC 3682, I propose to add a sentence at the
> beginning of the introduction stating that with a reference.
> Other points (minor/editorial/for the RFC editor):
> - 2 page 4 in:
>   "The possibility of denial-of-service (DoS) attack prevention,
>   however, is based on the assumption that packet classification and
>   separation of their paths is done before they go through a scarce
>   resource in the system."
>   two proposals: "is" -> "are" and "packet classification" ->
>   "classification of (the?) packets"
>
> - 2.2 page 5: (i.e., trusted) -> (i.e., are trusted)
>
> - 5.1 page 7: hasn't -> has not
>
> - 5.5 page 12: multi-hop -> multi-hop case
>
> - 6.1 page 12: add a reference for RFC 3682 here (in fact, everywhere
>   at the exception of the abstract).
>
> - A page 14: I can't parse "within "TrustRadius" (e.g., 1)
>   of 255 instead of 255"
>
> Regards
>
> Francis.Dupont@fdupont.fr
>


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art