Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EADE42009F3 for ; Fri, 20 May 2016 22:29:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E988D160A25; Fri, 20 May 2016 20:29:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1676D1607AA for ; Fri, 20 May 2016 22:29:08 +0200 (CEST) Received: (qmail 61684 invoked by uid 500); 20 May 2016 20:29:08 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Delivered-To: moderator for users@qpid.apache.org Received: (qmail 49669 invoked by uid 99); 20 May 2016 20:27:07 -0000 X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=oasis-open-org.20150623.gappssmtp.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oasis-open-org.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to; bh=PiONdd+M4sFgqe+G+9J6hdQGoy1tXwBO9NGuelvEl2s=; b=Z4ZWkSXk/gjEKLoElsqnkuWEbuncerbqeVstIWXprEtbrb8K/6pjhe4CZPeceJ6F85 v9yXy71gMzCQ7r2JoM2cUypm2+P2hF52e/4QYv+blCPIeu8JRs3Z1XEUcI2TK2MtSHuF W96yD5p31xCyOSTsfuNoFkSRrNt3JzgLZkczFs00jKFyfvZi9sCQecRRnBhlbymDvPwH 5Ql+eeZ2fyLzE0Qj++QNDI6sc9zXJ4c1BA6vJkc+xqxZhzFbWH89GOIibFhZhaufyPMH FLARP5sIUluIfVcxzvUvUlgoJig9ezrAbbocxt01zfJViHoJqRJQV9Js7WxC+d3AMrAU EG6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=PiONdd+M4sFgqe+G+9J6hdQGoy1tXwBO9NGuelvEl2s=; b=MFTvgRbbt6Q5cE+WnOFD4GaXBdgg6XQ3fVTMhuFToZa5vp2CYkoiHKtXLgsIti6P+v EUMwJSW/+r3YqCE6F5IJd999WvtIggYkBmb0tD8X/82iCZMfezCrpY0xsLm1PEk745Cn WbQ+lIl3MHOWsCj3OmmXTk8aMYq3owIGM64dxHfyesswghnt5UDntjjZfv5jgg0VIL87 Tm+j+a42FPrFkOunl2VCAj+HVthTfqjXyhLXxbcGiR2DezqCo5tosviGmXBT+SI0G+MQ zqCaXaj6JRRXHXMjTP3S0wu2xPCnapkkjLhap2U9Y7PJMi9oiIX4QC7SX7cFx03iCUhA 5+EQ== X-Gm-Message-State: AOPr4FVmwXRUX7hr2hKKpEpwcEsW3HVleXdLZWHQGCaa3RgU0Iz4UsJqQsZC5uC5apoVFv7OUjf/SBN07UZWzA== MIME-Version: 1.0 X-Received: by 10.50.108.45 with SMTP id hh13mr4487116igb.27.1463776014632; Fri, 20 May 2016 13:26:54 -0700 (PDT) Date: Fri, 20 May 2016 16:26:54 -0400 Message-ID: Subject: Public Review for AMQP WebSocket Binding V1.0 - ends June 6th From: Chet Ensign To: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, amqp-bindmap@lists.oasis-open.org, amqp-bindmap-comment@lists.oasis-open.org Content-Type: multipart/alternative; boundary=089e01493b52624d4405334be980 archived-at: Fri, 20 May 2016 20:29:10 -0000 --089e01493b52624d4405334be980 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable OASIS members and other interested parties, The OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.= 0 Committee Specification Draft 02 / Public Review Draft 02 19 April 2016 Specification Overview: This specification describes how the WebSocket protocol can be used as a transport for AMQP 1.0 protocol traffic. It is applicable for two main scenarios: - Firewall traversal. Since WebSocket connection establishment is implemented as standard HTTP traffic using the default ports (80 and 443), it is often able to pass through network security devices without requiring special configuration or opening of additional ports. When WebSocket is used as a transport for AMQP 1.0 protocol traffic, this enables communication between arbitrary AMQP peers such as an application using an AMQP client library and an AMQP message broker, separated by a firewall. - Browser-based messaging. HTML5 compatible Web browsers have built-in support for the WebSocket protocol, thereby enabling a broad range of browser-based AMQP messaging scenarios. About the TC: The purpose of the AMQP Bindings and Mappings (AMQP-BINDMAP) TC is to define bindings of AMQP 1.0 core protocol to underlying transports other than TCP, to define mappings of the AMQP 1.0 core protocol to existing well-known programming APIs, and to define representations of the AMQP 1.0 message format in existing well-known languages. Public Review Period: The public review starts 23 May 2016 at 00:00 UTC and ends 06 June 2016 at 11:59 UTC. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in the included red-lined DIFF file [3]. This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work. Reviewers may provide comments directly from the comment-tag version of document. The file amqp-wsb-v1.0-csprd02-COMMENT-TAGS.html contains the HTML version of the draft with a =E2=80=9C[comment?]=E2=80=9D = link next to each section heading. Clicking on this link will launch your email application and begin a message to amqp-bindmap-comment@lists.oasis-open.or= g with the specific section number and title in the subject line. Simply enter your comment and click send. Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=3Damqp-b= indmap . URIs: The prose specification document and related files are available here: PDF (Authoritative): http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02.pdf HTML: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02.html HTML with in-line comment tags: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02-COMMENT-TAGS.html Editable source: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02.doc ZIP distribution files (complete): For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02.zip Additional information about this specification and the AMQP-BINDMAP TC may be found on the TC's public home page located at: http://www.oasis-open.org/committees/amqp-bindmap/ Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at: http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=3Damqp-bin= dmap Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at: http://lists.oasis-open.org/archives/amqp-bindmap-comment/ All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of 'Advanced Message Queuing Protocol (AMQP) WebSocket Binding (WSB) Version 1.0', we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Additional references: [1] OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC http://www.oasis-open.org/committees/amqp-bindmap/ [2] Previous public reviews: 30-day public review, 20 June 2014: https://lists.oasis-open.org/archives/members/201406/msg00011.html - Comment resolution log: http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd01/amqp-wsb-v1.0= -csprd01-comment-resolution-log.txt [3] Red-lined DIFF file http://docs.oasis-open.org/amqp-bindmap/amqp-wsb/v1.0/csprd02/amqp-wsb-v1.0= -csprd02-DIFF.pdf [4] http://www.oasis-open.org/policies-guidelines/ipr [4] http://www.oasis-open.org/committees/amqp-bindmap/ipr.php RF on RAND Mode https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode --=20 /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 --089e01493b52624d4405334be980--