OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-985) The HTTP Specification document referenced in the OData Protocol Spec has been obsoleted


    [ https://issues.oasis-open.org/browse/ODATA-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63789#comment-63789 ] 

Martin Zurmuehl edited comment on ODATA-985 at 10/13/16 3:48 PM:
-----------------------------------------------------------------

RFC2616 is not mentioned in the current documents any more. We have substituted RFC2616 by [RFC7240]   [RFC7230]   [RFC7231]   [RFC7232] already in the past.

But we still use the also obsolete RFC2617 (“HTTP Authentication: Basic and Digest Access Authentication) in the protocol spec. 
Documents updating RFC 2617 are 
"Hypertext Transfer Protocol  (HTTP/1.1): Authentication" ([RFC7235], defining the authentication  framework), 
"The 'Basic' HTTP Authentication Scheme" ([RFC7617] updating the definition of the   
   "Basic" authentication scheme),
"HTTP Digest Access Authentication" ([RFC7616], updating
   the definition of the "Digest" authentication scheme), and
 "HTTP Authentication-Info and Proxy-Authentication-Info Response Header
   Fields" ([RFC7615]).  
Taken together, these four documents obsolete RFC2617.

We have 3 references to RFC2617 in the document; all 3 are pointing to the "basic authentication".
--> We should substitute RFC2617 by [RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme", RFC 7617, September 2015. http://www.ietf.org/rfc/rfc7617.txt

There are no substantive changes from our perspective; the RFC7617 states:
"Changes from RFC 2617

   The scheme definition has been rewritten to be consistent with newer
   specifications such as [RFC7235].

   The new authentication parameter 'charset' has been added.  It is
   purely advisory, so existing implementations do not need to change,
   unless they want to take advantage of the additional information that
   previously wasn't available.
"

I updated the proposal accordingly.


was (Author: martinzurmuehl):
RFC2616 is not mentioned in the current documents any more. We have substituted RFC2616 by [RFC7240]   [RFC7230]   [RFC7231]   [RFC7232] already in the past.

But we still use the also obsolete RFC2617 (“HTTP Authentication: Basic and Digest Access Authentication) in the protocol spec. 
Documents updating RFC 2617 are 
"Hypertext Transfer Protocol  (HTTP/1.1): Authentication" ([RFC7235], defining the authentication  framework), 
"The 'Basic' HTTP Authentication Scheme" ([RFC7617] updating the definition of the   
   "Basic" authentication scheme),
"HTTP Digest Access Authentication" ([RFC7616], updating
   the definition of the "Digest" authentication scheme), and
 "HTTP Authentication-Info and Proxy-Authentication-Info Response Header
   Fields" ([RFC7615]).  
Taken together, these four documents obsolete RFC2617.

We have 3 references to RFC2617 in the document; all 3 are pointing to the "basic authentication".
--> We should substitute RFC2617 by [RFC7617] Reschke, J., "The 'Basic' HTTP Authentication Scheme", RFC 7617, September 2015. http://www.ietf.org/rfc/rfc7617.txt

There are no substantive changes from our perspective; the RFC7617 states:
"Changes from RFC 2617

   The scheme definition has been rewritten to be consistent with newer
   specifications such as [RFC7235].

   The new authentication parameter 'charset' has been added.  It is
   purely advisory, so existing implementations do not need to change,
   unless they want to take advantage of the additional information that
   previously wasn't available.
"



> The HTTP Specification document referenced in the OData Protocol Spec has been obsoleted
> ----------------------------------------------------------------------------------------
>
>                 Key: ODATA-985
>                 URL: https://issues.oasis-open.org/browse/ODATA-985
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.01_WD01
>            Reporter: Mark Biamonte
>            Assignee: Martin Zurmuehl
>             Fix For: V4.01_WD01
>
>
> The Normative References section in the OData Protocol spec  (http://docs.oasis-open.org/odata/odata/v4.0/os/part1-protocol/odata-v4.0-os-part1-protocol.html#_Toc372793589) includes the following reference
> [RFC2616]                  Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1”, RFC 2616, June 1999. http://www.ietf.org/rfc/rfc2616.txt.
> The page https://www.rfc-editor.org/info/rfc2616 shows that RFC2616 has been obsoleted by the following six RFCs
> RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing, JUNE 2014
> RFC 7231 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, JUNE 2014
> RFC 7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests, JUNE 2014
> RFC 7233 - Hypertext Transfer Protocol (HTTP/1.1): Range Requests, JUNE 2014
> RFC7234 - Hypertext Transfer Protocol (HTTP/1.1): Caching, JUNE 2014
> RFC7235 - Hypertext Transfer Protocol (HTTP/1.1): Authentication, JUNE 2014
> Additionally the following items are also referenced in the Normative References section of the Protocol spec
> [HTTP-Prefer]            Snell, J., "Prefer Header for HTTP", draft-snell-http-prefer-18, January 2013. https://datatracker.ietf.org/doc/draft-snell-http-prefer/.
> [HTTP-Message]        Fielding, R., Ed. and J. Reschke, Ed., “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing” draft-ietf-httpbis-p1-messaging-22, 23 February 2013. https://datatracker.ietf.org/doc/draft-ietf-httpbis-p1-messaging/.
> [HTTP-Semantics]     Fielding, R., Ed. and J. Reschke, Ed., “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content” draft-ietf-httpbis-p2-semantics-22, 23 February 2013 https://datatracker.ietf.org/doc/draft-ietf-httpbis-p2-semantics/.
> [HTTP-Conditional]    Fielding, R., Ed. and J. Reschke, Ed., “Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests” draft-ietf-httpbis-p4-conditional-22, 23 February 2013 https://datatracker.ietf.org/doc/draft-ietf-httpbis-p4-conditional/.
> These have been replaced as follows
> "Prefer Header for HTTP", draft-snell-http-prefer is now RFC 7240.
> Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing” draft-ietf-httpbis-p1-messaging is now RFC 7230
> Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content” draft-ietf-httpbis-p2-semantics is now RFC 7231
> Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests” draft-ietf-httpbis-p4-conditional is now RFC 7232



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]