[apps-discuss] AppsDir review of draft-dbider-sha2-mac-for-ssh-05

S Moonesamy <sm+ietf@elandsys.com> Tue, 10 April 2012 23:24 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9D221F8652; Tue, 10 Apr 2012 16:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level:
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, 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 7xIUGB1SpzkG; Tue, 10 Apr 2012 16:24:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1407721F8650; Tue, 10 Apr 2012 16:24:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.8]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q3ANOHxA020579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Apr 2012 16:24:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1334100270; i=@elandsys.com; bh=/LZu0MXIwDkl7dt2NG7/Px7Jz3Rssw7APmfhIKzeX3g=; h=Date:To:From:Subject:Cc; b=p0TdAGMvgMjnb2qOKh+ucTFSHPX5PPHPxHNLLIZKA7lhtpJkvPaxhapHwi80/vdtN S4gU75x3uE9pDhEZmRWtrMT+0KXhMli/oy2YXOTnOEhu/4vvApx4awkfNxbUu26p4b ob1PYb2DRhQ5SzdZDDOuDn2qyqzlG7HZB5zK8Wyk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1334100270; i=@elandsys.com; bh=/LZu0MXIwDkl7dt2NG7/Px7Jz3Rssw7APmfhIKzeX3g=; h=Date:To:From:Subject:Cc; b=v0ziZ4eiMLZ8kAhiDmsWIx7nNqcstWQdt1kkOmSv2DNyXbhPFKIrGXiYbP1oZnyia ZP5zhRsvM4lzTqn1PaKWh7MHIXKe+rClNMVBd5d8JN0KrAhan3JGBncGvTIxcJ0/Bu hWYDsPa88llEwhdZhVyX6w51/a23PcWHGNWLBOw4=
Message-Id: <6.2.5.6.2.20120410153427.08d5c3b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Apr 2012 16:20:23 -0700
To: apps-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: draft-dbider-sha2-mac-for-ssh.all@tools.ietf.org, iesg@ietf.org
Subject: [apps-discuss] AppsDir review of draft-dbider-sha2-mac-for-ssh-05
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Apr 2012 23:24:33 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on appsdir, please 
see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-dbider-sha2-mac-for-ssh-05
Title: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport
        Layer Protocol

Reviewer: S. Moonesamy
Review Date: April 10, 2012
IETF Last Call Date: April 16, 2012
IESG Telechat Date: April 26, 2012

Summary:  This draft is ready for publication as a Proposed Standard.

The draft defines algorithm names and parameters for use of some of 
the SHA-2 family of secure hash algorithms for data integrity 
verification in SSH protocol.  It updates RFC 4253.

Nits:

In the Abstract Section:

   "It also updates RFC4253 by specifying a new RECOMMENDED data
    integrity algorithm."

Should the word "RECOMMENDED" be interpreted as a RFC 2119 key word?

In Section 3:

  "IANA is requested to update the SSH algorithm registry with the
   following entries."

Shouldn't that be the Secure Shell MAC Algorithm Names registry?

Regards,
S. Moonesamy