Re: [hybi] RFC 6455 - conflicting statements
"Nataraju A.B" <nataraju.sip@gmail.com> Sun, 29 April 2012 17:02 UTC
Return-Path: <nataraju.sip@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D38521F84EC for <hybi@ietfa.amsl.com>; Sun, 29 Apr 2012 10:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 CqH3Mo+swEw0 for <hybi@ietfa.amsl.com>; Sun, 29 Apr 2012 10:02:52 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id ED66121F84E7 for <hybi@ietf.org>; Sun, 29 Apr 2012 10:02:51 -0700 (PDT)
Received: by lagj5 with SMTP id j5so1606805lag.31 for <hybi@ietf.org>; Sun, 29 Apr 2012 10:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HJoPi2tAtxdqrRW+w3LlR7RcpvsLzFsQC98Yq9ywzvk=; b=OZHUez82Go704Jgl/yuj0Fr8Q/Jp2TnpsGnWM8/NOUe2t2FNrDGYJ4Ru2NsN6zi7GI jBSBvyIOBYbI0xO5Hh7/QyN/EDavOhFI1bylOOG52xREhXJrhW8bIVWwIxfv12HR8ubK dDAzwH6k9wxKWETAazZf3suBd0DReelZPWEvc/EDS6QsOL9pPem772dQDXZhv8OHC+jv XT51ihvwJmR12AYu+g0ru+4l2lzhSHjKjSVlIuf4aPNwJvhsMmh+Lg2bmQd25IViQMKf VL/IYZBP1h1+mBJizGZd9QgkE0FF8Q9c02gzKO/NAtGgDIarpSFggJtw3tIq6Hgdfkxg mkzg==
MIME-Version: 1.0
Received: by 10.112.101.162 with SMTP id fh2mr8808461lbb.20.1335718970832; Sun, 29 Apr 2012 10:02:50 -0700 (PDT)
Received: by 10.112.36.104 with HTTP; Sun, 29 Apr 2012 10:02:50 -0700 (PDT)
In-Reply-To: <D52647B3-2DFB-42D8-AF6C-F9EBE494672E@isode.com>
References: <CA+rAfUO1MPJcpKv+uHk0BD6sUo55SsUg_u+3ypeLdkdLGcQwEw@mail.gmail.com> <CA+rAfUPkLG=CAekZrVaVvNSQPX7+8FCnvyrAds_mA7swKQGHvw@mail.gmail.com> <996C3E66-90B8-4C86-885C-AD436D94E61C@isode.com> <CA+rAfUOej-e_=7O32i3UmZkvcUuh3OP-OBMx1QH7VJ9Atzv=3g@mail.gmail.com> <D52647B3-2DFB-42D8-AF6C-F9EBE494672E@isode.com>
Date: Sun, 29 Apr 2012 22:32:50 +0530
Message-ID: <CA+rAfUPp3KNQ9fMdxjXDVCOtYktuzdJqoXN_7MiL9Ub7RGOtKQ@mail.gmail.com>
From: "Nataraju A.B" <nataraju.sip@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary="f46d04016a77c6b9a404bed44e10"
Cc: "hybi@ietf.org" <hybi@ietf.org>, "ifette+ietf@google.com" <ifette+ietf@google.com>
Subject: Re: [hybi] RFC 6455 - conflicting statements
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Apr 2012 17:02:54 -0000
Alex, Sorry for confusion. The comment should have been other way round. I mean sections 1.1-1.9 shall be normative like other sections. For example, Opening Handshake, Closing Handshake, Establishing a Connection are mandatory to implement. Hence these sections must be mentioned as normative text. therefore the text "_This section is non-normative._" shall be removed in these sections. Thanks, Nataraju A B On Sun, Apr 29, 2012 at 9:55 PM, Alexey Melnikov <alexey.melnikov@isode.com>wrote: > Hi, > > > On 27 Apr 2012, at 11:21, "Nataraju A.B" <nataraju.sip@gmail.com> wrote: > > > > On Fri, Apr 27, 2012 at 3:11 PM, Alexey Melnikov < > alexey.melnikov@isode.com> wrote: > >> On 27 Apr 2012, at 10:05, "Nataraju A.B" <nataraju.sip@gmail.com> wrote: >> >> Hi All, >> >> >> Hi, >> >> >> Following is the snippet from the RFC6455. >> >> <RFC6455> >> >> 2. Conformance Requirements >> >> All diagrams, examples, and notes in this specification are non- >> normative, as are all sections explicitly marked non-normative. >> *Everything *else in this specification is normative. >> >> >> 1.9. Subprotocols Using the WebSocket Protocol >> >> _This section is non-normative._ >> >> The client can request that the server use a specific subprotocol by >> including the |Sec-WebSocket-Protocol| field in its handshake. If it >> is specified, the server needs to include the same field and one of >> the selected subprotocol values in its response for the connection to >> be established. >> >> >> 3. WebSocket URIs >> >> This specification defines two URI schemes, using the ABNF syntax >> defined in RFC 5234 [RFC5234], and terminology and ABNF productions >> defined by the URI specification RFC 3986 [RFC3986]. >> >> ws-URI = "ws:" "//" host [ ":" port ] path [ "?" query ] >> wss-URI = "wss:" "//" host [ ":" port ] path [ "?" query ] >> >> host = <host, defined in [RFC3986], Section 3.2.2> >> port = <port, defined in [RFC3986], Section 3.2.3> >> path = <path-abempty, defined in [RFC3986], Section 3.3> >> query = <query, defined in [RFC3986], Section 3.4> >> >> </RFC6455> >> >> *Comment*: According to statement in sec 2, section 3 - WebSocket URIs >> (for example) is normative. But I don't think that it correct. Section >> 3, 4, 5, 6, 7, 8 must also be changed as non-normative text by inserting >> the text "_This section is non-normative._". >> >> >> Can you elaborate why you think that these sections are non-normative? >> > > [ABN] In this context, We understand normative means informative text. It > is not mandatory to implement or refer normative text. But it is mandatory > to follow syntax and semantics of non-normative text / information. AFAIU > sections 3-8 of rfc6455 are mandatory to implement. Hence it must be > mentioned as non-normative text "_This section is non-normative._", like > mentioned for sections 1.1-1.9 > > > Sorry, I am very confused. Non-normative and Informative have the say > meaning. They definitely don't equate to "normative". Specific syntax, like > ws: URI in Section 3 is normative, as it defines specific rules that are > necessary to follow to implement ws: URI parsing, generation or processing. > > >> Otherwise, Am I missing something here ??? >> >> Thanks, >> Nataraju A.B. >> >> > -- Thanks, Nataraju A.B.
- Re: [hybi] RFC 6455 - conflicting statements Nataraju A.B
- Re: [hybi] RFC 6455 - conflicting statements Alexey Melnikov
- [hybi] Fwd: RFC 6455 - conflicting statements Nataraju A.B
- Re: [hybi] Fwd: RFC 6455 - conflicting statements IƱaki Baz Castillo
- Re: [hybi] RFC 6455 - conflicting statements Alexey Melnikov
- Re: [hybi] RFC 6455 - conflicting statements Nataraju A.B
- Re: [hybi] RFC 6455 - conflicting statements Alexey Melnikov