1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
Experimental RFC
|
3.
|
Justification for the specific reference:
|
|
The PATCH method will be used to define an UPDATE operation in a REST interface. IETF 5789 specifies the semantics of the PATCH method in HTTP.
|
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=5789
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
Supersedes none.
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[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./
/
[RFC3864] Klyne, G., Nottingham, M., and J. Mogul, "Registration/
Procedures for Message Header Fields", BCP 90, RFC 3864,/
September 2004./
[RFC4918] Dusseault, L., "HTTP Extensions for Web Distributed/
Authoring and Versioning (WebDAV)", RFC 4918, June 2007.
|
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
|
|