[Gen-art] Gen-ART LC review of draft-ietf-uta-xmpp-05

"Roni Even" <ron.even.tlv@gmail.com> Fri, 03 April 2015 09:59 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DDD01A7022; Fri, 3 Apr 2015 02:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7o_YDjULRWz; Fri, 3 Apr 2015 02:59:57 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B011E1A7017; Fri, 3 Apr 2015 02:59:56 -0700 (PDT)
Received: by wgin8 with SMTP id n8so17907590wgi.0; Fri, 03 Apr 2015 02:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=1qfIi4/iR6Ys5e8VMVL4xUlDVAmvTVjOhSHHm5Ma67U=; b=POsKrxsHc8AInevzbcGWtYZn1PZtx2F+tULuEbBInibZnb7GRAP8R/2c1+SUd4Y+RM pimiIXZgpRhJU8cfXSRzPtcdOY9nGYwz6mYyUdzaYSls0MJA1sME7jcqyKAMTG4x1Z/+ zUZOj0OcE0IiJamKT16JUdHWMZ626W1tCfbZk559oaBo6raaqpZ1EDQ9vY/DtJ3K2ei2 wtVHeugtTZw3T+H0V/TRBtxBs3GMTJMRCmc5XmEW/kagUYAvW02t3iTfRorZSc9r25Fh 85j9WBmpmXKiZ4Z60KeE/O7+bRinezck9QQ3ffm5oJE4BQ3Vpc3hP3glxxqUaYhuPr55 AIIA==
X-Received: by 10.194.223.5 with SMTP id qq5mr3402138wjc.152.1428055195505; Fri, 03 Apr 2015 02:59:55 -0700 (PDT)
Received: from RoniE (bzq-79-177-166-235.red.bezeqint.net. [79.177.166.235]) by mx.google.com with ESMTPSA id fa8sm784839wib.14.2015.04.03.02.59.53 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 03 Apr 2015 02:59:54 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: draft-ietf-uta-xmpp.all@tools.ietf.org
Date: Fri, 03 Apr 2015 12:59:48 +0300
Message-ID: <020b01d06df4$ed64fa10$c82eee30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_020C_01D06E0E.12B2F560"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBt9MKyGXRuCGRNT2+a1sIryuuRAw==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/X2fkgx36di8yhsT9WbRMG9BDcps>
Cc: gen-art@ietf.org, ietf@ietf.org
Subject: [Gen-art] Gen-ART LC review of draft-ietf-uta-xmpp-05
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 03 Apr 2015 09:59:59 -0000

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-uta-xmpp-05

Reviewer: Roni Even

Review Date:2015-4-3

IETF LC End Date: 2015-4-13

IESG Telechat date: 

 

Summary: This draft is not ready for publication as an Standard Track  RFC.

 

 

Major issues:

I am wondering why this document is a standard track and not Informational,
reading it I get the impression that it repeats text from RFC6120 and does
not provide new normative information.

 

Section 3.1 talks about TLS support and say that it SHOULD be tried  but
since it is a SHOULD I assume that failure may happen and non TLS
connections may be used ( I am not sure what RFC6120 say about it.

 

Section 3.4 may look like authentication is a MUST but section 3.5 talks
about  unauthenticated connections

 

On section 3.7 I assume that providing e2e information is based on the XMPP
architecture that may have only one server to server hop.  Are there other
cases?

 

Minor issues: