Re: [hybi] RFC 6455 - conflicting statements

[Alexey Melnikov <[e-mail]>]

On 27 Apr 2012, at 10:05, "Nataraju A.B" <[e-mail]> 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?

> Otherwise, Am I missing something here ???
> 
> Thanks,
> Nataraju A.B.