Re: [Gen-art] GenART LC review of draft-ietf-appsawg-rfc3462bis-01

"Murray S. Kucherawy" <msk@cloudmark.com> Mon, 03 October 2011 05:26 UTC

Return-Path: <msk@cloudmark.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A1321F8663; Sun, 2 Oct 2011 22:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.974
X-Spam-Level:
X-Spam-Status: No, score=-102.974 tagged_above=-999 required=5 tests=[AWL=-0.376, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 pqAOyZq+zvKd; Sun, 2 Oct 2011 22:26:05 -0700 (PDT)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id 429ED21F85EF; Sun, 2 Oct 2011 22:26:05 -0700 (PDT)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Sun, 2 Oct 2011 22:29:06 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-appsawg-rfc3462bis.all@tools.ietf.org" <draft-ietf-appsawg-rfc3462bis.all@tools.ietf.org>
Date: Sun, 02 Oct 2011 22:29:05 -0700
Thread-Topic: GenART LC review of draft-ietf-appsawg-rfc3462bis-01
Thread-Index: AcyAPlbBDH5dlWMQStOjcRPEol3dZwBTq87Q
Message-ID: <F5833273385BB34F99288B3648C4F06F19C45D9DD7@EXCH-C2.corp.cloudmark.com>
References: <4e87169c.8e2bdf0a.01d9.20f0@mx.google.com>
In-Reply-To: <4e87169c.8e2bdf0a.01d9.20f0@mx.google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5833273385BB34F99288B3648C4F06F19C45D9DD7EXCHC2corpclo_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 'IETF-Discussion list' <ietf@ietf.org>
Subject: Re: [Gen-art] GenART LC review of draft-ietf-appsawg-rfc3462bis-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2011 05:26:06 -0000

Hi Roni, thanks for your comments.
Two things in reply:
First, this is not an Informational document, it's Standards Track.  I don't know if that changes anything in your review, however.
Second, Section 1 does describe the change being made between RFC3462 and this document, and the rationale for doing so.  Was there some detail missing from there that was in the Appendix that you feel should be added?
Thanks,
-MSK
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Roni Even
Sent: Saturday, October 01, 2011 6:31 AM
To: draft-ietf-appsawg-rfc3462bis.all@tools.ietf.org
Cc: gen-art@ietf.org; 'IETF-Discussion list'
Subject: GenART LC review of draft-ietf-appsawg-rfc3462bis-01

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Please resolve these comments along with any other Last Call comments you may receive.

Document: draft-ietf-appsawg-rfc3462bis-01

Reviewer: Roni Even

Review Date: 2011-10-1

IETF LC End Date: 2011-10-10

IESG Telechat date:



Summary: This draft is almost ready for publication as an informational RFC.



Major issues:





Minor issues:

I noticed that the major change from RFC 3462 in the current version is to remove requirement that multipart/report not be contained in anything. The changes appear in appendix B which is to be removed in the published document.  I think that it will be better to have the change from RFC 3462 be part of the main text and also discuss what are the backward interoperability issues if any.





Nits/editorial comments: