[xmpp] #40: mandatory to support TLS server_name extension

"xmpp issue tracker" <trac@tools.ietf.org> Tue, 22 June 2010 00:16 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: xmpp@core3.amsl.com
Delivered-To: xmpp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97D2C3A6914 for <xmpp@core3.amsl.com>; Mon, 21 Jun 2010 17:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.426
X-Spam-Level:
X-Spam-Status: No, score=-102.426 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toqeezXD7I20 for <xmpp@core3.amsl.com>; Mon, 21 Jun 2010 17:16:32 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id D91AF3A6911 for <xmpp@ietf.org>; Mon, 21 Jun 2010 17:16:32 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OQrAM-0003GW-Pn; Mon, 21 Jun 2010 17:16:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: xmpp issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: stpeter@stpeter.im
X-Trac-Project: xmpp
Date: Tue, 22 Jun 2010 00:16:38 -0000
X-URL: http://tools.ietf.org/xmpp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/xmpp/trac/ticket/40
Message-ID: <057.b4f1b6eafe04871966a9d302c3491860@tools.ietf.org>
X-Trac-Ticket-ID: 40
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: stpeter@stpeter.im, xmpp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: xmpp@ietf.org
Subject: [xmpp] #40: mandatory to support TLS server_name extension
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.9
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2010 00:16:33 -0000

#40: mandatory to support TLS server_name extension
--------------------------------+-------------------------------------------
 Reporter:  stpeter@…           |       Owner:  stpeter@…         
     Type:  defect              |      Status:  new               
 Priority:  major               |   Milestone:                    
Component:  3920bis             |     Version:                    
 Severity:  In WG Last Call     |    Keywords:                    
--------------------------------+-------------------------------------------
 Section 5.2.6 (TLS Extensions) states:

 > Because XMPP services are often provided in so-called virtual
 > hosting deployments, it is RECOMMENDED for the initiating entity
 > to include an extension of type "server_name" as defined in
 > [TLS-EXT].  If an XMPP service hosts multiple domains on the same
 > IP address, it MUST enable support for the "server_name" extension.

 Matthew Wild commented: "Says that servers MUST support the server_name
 extension, however it doesn't give much information on how it would be
 used. It seems only useful in the context of 5223, which has never been
 standardized. Perhaps drop this requirement? Or at least reduce it to
 MAY."

 Dave Cridland commented: "Mandating server_name? This seems
 unsatisfactory, not least because XMPP has its own perfectly sound method
 for selecting server name which works perfectly well."

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/xmpp/trac/ticket/40>
xmpp <http://tools.ietf.org/xmpp/>