Re: [hybi] RFC 6455 - conflicting statements
"Nataraju A.B" <nataraju.sip@gmail.com> Fri, 27 April 2012 10:21 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 C15AF21F8835 for <hybi@ietfa.amsl.com>; Fri, 27 Apr 2012 03:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level:
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.460, 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 FzyNedOoLqxa for <hybi@ietfa.amsl.com>; Fri, 27 Apr 2012 03:21:02 -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 635D621F87A8 for <hybi@ietf.org>; Fri, 27 Apr 2012 03:21:01 -0700 (PDT)
Received: by lagj5 with SMTP id j5so422954lag.31 for <hybi@ietf.org>; Fri, 27 Apr 2012 03:21:00 -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=E9EwQZJQ8IQcFN5qClQrE7U5ibnY4A2TMDeoOp40io8=; b=Vz78zQZ49tHy5pO9gmCXxMyYs+gla5WBONwvEeXVSP8ngJy7RVz5XqTpNHTn9jn/P7 owMohZEafMX/LlPMeTwnqUtlYQO7t5LwErkAv2RPg0DUeXhnmthm/Ckg4zMKC4hS+6CY j1vgaIeoE1T4Po+e7zuOvIITJoWM2RkNJeV7LwFaC442uJNVfy4iuAT0QmaFHp/CLvjg U/MY1DWtlAJCBkCYuXpMStgSZw8vgnyVDOoiNRDJp1DlnkF/i/Lj0AIVktb+oVgCz+86 crUp01LHowrMRQB7g74RKvsJ+GDyknET2Rc7/FSfcZpI0o8TEMFBNcvt3Uh0aB4pPcin qTqg==
MIME-Version: 1.0
Received: by 10.152.128.201 with SMTP id nq9mr3361227lab.26.1335522060315; Fri, 27 Apr 2012 03:21:00 -0700 (PDT)
Received: by 10.112.36.104 with HTTP; Fri, 27 Apr 2012 03:21:00 -0700 (PDT)
In-Reply-To: <996C3E66-90B8-4C86-885C-AD436D94E61C@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>
Date: Fri, 27 Apr 2012 15:51:00 +0530
Message-ID: <CA+rAfUOej-e_=7O32i3UmZkvcUuh3OP-OBMx1QH7VJ9Atzv=3g@mail.gmail.com>
From: "Nataraju A.B" <nataraju.sip@gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary="f46d042d0596feac7304bea675f2"
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: Fri, 27 Apr 2012 10:21:02 -0000
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 > > 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