|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 can HTTP State Management Mechanism techniques as a mean of keeping its state information.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2965
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[DMK95] Kristol, D.M., "Proposed HTTP State-Info Mechanism",/
available at http://portal.research.bell-/
labs.com/~dmk/state-info.html, September, 1995./
/
[Netscape] "Persistent Client State -- HTTP Cookies", available at/
http://www.netscape.com/newsref/std/cookie_spec.html,/
undated./
/
[RFC2109] Kristol, D. and L. Montulli, "HTTP State Management/
Mechanism", RFC 2109, February 1997./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2279] Yergeau, F., "UTF-8, a transformation format of Unicode/
and ISO-10646", RFC 2279, January 1998./
/
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform/
Resource Identifiers (URI): Generic Syntax", RFC 2396,/
August 1998./
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T./
Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",/
RFC 2616, June 1999./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
