[drinks] SOAP draft - proposed changes based on IESG comments

Alexander Mayrhofer <alexander.mayrhofer@nic.at> Thu, 24 March 2016 14:51 UTC

Return-Path: <alexander.mayrhofer@nic.at>
X-Original-To: drinks@ietfa.amsl.com
Delivered-To: drinks@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0514612DB6B for <drinks@ietfa.amsl.com>; Thu, 24 Mar 2016 07:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_HTML_ATTACH=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3d4bRVCu7M4M for <drinks@ietfa.amsl.com>; Thu, 24 Mar 2016 07:51:32 -0700 (PDT)
Received: from mail.sbg.nic.at (mail.sbg.nic.at []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8FE912DCB6 for <drinks@ietf.org>; Thu, 24 Mar 2016 07:38:42 -0700 (PDT)
Received: from nics-exch2.sbg.nic.at ([]) by mail.sbg.nic.at with XWall v3.52f ; Thu, 24 Mar 2016 15:38:36 +0100
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id 14.03.0279.002; Thu, 24 Mar 2016 15:38:34 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: "drinks@ietf.org" <drinks@ietf.org>
Thread-Topic: SOAP draft - proposed changes based on IESG comments
Thread-Index: AdGF1MsnxwJv2zfBRAqLQD1ivgpqkg==
Date: Thu, 24 Mar 2016 14:38:33 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE075643337C2@NICS-EXCH2.sbg.nic.at>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/mixed; boundary="_002_19F54F2956911544A32543B8A9BDE075643337C2NICSEXCH2sbgnic_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/drinks/jCMZ5Amq5lPupkfm-at7XbBkNc0>
Subject: [drinks] SOAP draft - proposed changes based on IESG comments
X-BeenThere: drinks@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DRINKS WG <drinks.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/drinks>, <mailto:drinks-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/drinks/>
List-Post: <mailto:drinks@ietf.org>
List-Help: <mailto:drinks-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/drinks>, <mailto:drinks-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 14:51:37 -0000

Hello everyone,

I'm working with Ben Campbell (our responsible area director) to clear out final comments from the IESG review in order to get the SOAP draft into the RFC editor queue. I'm posting the proposed changes to WG list, so that everybody  has a chance to  review them. 

In the unlikely case you  violently disagree with any of the changes, please let me know ASAP - and, at the same time, please propose alternative text in order to resolve the comment.

The IESG comments can be reviewed on https://datatracker.ietf.org/doc/draft-ietf-drinks-spp-protocol-over-soap/ballot/ - here are my proposed changes:

- Spencer on mandatory-to-implement versions of SOAP and WSDL:  Based on Ben's suggestion, I changed the text so that SOAP 1.2 is mandatory to implement, and WDSL 1.1 should be the preferred version (no earlier version). 

- Stephen on "Identifier" vs "Identity": I've changed that to "Identifier", like we did in the Framework document.

- Stephen on weakness of the Security Considerations section: I've added a backreference to the Security Considerations section of the Framework draft, stating that those considerations also apply to the protocol implementation.

- Barry on the obsolete RFC2616 reference: The reference is now changed to RFC7230 / RFC7231

- Kathleen on SSL vs TLS:  All occurences of SSL have been changed to TLS

- Kathleen on the UTA BCP:  RFC7525 is a new normative reference, and use of TLS MUST follow that BCP.

- Kathleen on invalid XML response code: I've added text that "2000" is to be used in such cases.

Please find a diff against version -08 attached in case you want to review the full changes.