Last Call: draft-ietf-repute-model-08.txt (A Model for Reputation Reporting) to Proposed Standard
The IESG has received a request from the Reputation Services WG (repute) to consider the following document: - 'A Model for Reputation Reporting' draft-ietf-repute-model-08.txt as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2013-09-10. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. This is a new Last Call on this document. It was previously in Last Call for Informational, but after some Last Call comments, the WG decided that it would be more appropriate on the standards track. The due date has been extended accordingly. Abstract This document describes a general architecture for a reputation-based service and a model for requesting reputation-related data over the Internet, where reputation refers to predictions or expectations about an entity or an identifier such as a domain name. The document roughly follows the recommendations of RFC4101 for describing a protocol model. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-repute-model/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-repute-model/ballot/ No IPR declarations have been submitted directly on this I-D.
Protocol Action: 'WebFinger' to Proposed Standard (draft-ietf-appsawg-webfinger-18.txt)
The IESG has approved the following document: - 'WebFinger' (draft-ietf-appsawg-webfinger-18.txt) as Proposed Standard This document is the product of the Applications Area Working Group. The IESG contact persons are Barry Leiba and Pete Resnick. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-appsawg-webfinger/ Technical Summary This specification defines the WebFinger protocol, which can be used to discover information about people or other entities on the Internet using standard HTTP methods. WebFinger discovers information for a URI that might not be usable as a locator otherwise, such as account or email URIs. Review and Consensus The WebFinger draft has been discussed extensively within the APPSAwg during the last year, it become a wg item in August 2012. Actually at some point the mail traffic generated by the discussion was so high that it was agreed to move the discussion to a dedicated mailing list (webfin...@ietf.org). The only significant point difficult to agree on has been about whether WebFinger MUST support HTTPS only or instead it should be allowed for WebFinger fallback from HTTPS to HTTP. That was resolved with a consensus call that generated a strong rough consensus for HTTPS only. The draft has been also extensively reviewed during the APPSAwg Last Call. A lot of editorial issues, text clarifications have been raised; all of them are now addressed in the current version of the draft. During the wglc process it has been also agreed to define a new media type for WebFinger. There are several open source WebFinger implementations already updated to the last version of the draft, a not exhaustive list of them can be found here: http://www.packetizer.com/webfinger/software.html Personnel Salvatore Loreto is the document shepherd. Barry Leiba is the responsible Area Director.
Last Call: draft-cotton-rfc4020bis-01.txt (Early IANA Allocation of Standards Track Code Points) to Best Current Practice
The IESG has received a request from an individual submitter to consider the following document: - 'Early IANA Allocation of Standards Track Code Points' draft-cotton-rfc4020bis-01.txt as Best Current Practice The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2013-09-24. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This memo describes the process for early allocation of code points by IANA from registries for which Specification Required, RFC Required, IETF Review, or Standards Action policies apply. This process can be used to alleviate the problem where code point allocation is needed to facilitate desired or required implementation and deployment experience prior to publication of an RFC that would normally trigger code point allocation. This document obsoletes RFC 4020. The file can be obtained via http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ballot/ No IPR declarations have been submitted directly on this I-D.
