An updated version taking into account the various comments
received during Last Call is now available as
Most Last Call comments were editorial in nature, but one commenter
strongly, and in the end convincingly, argued that the spec was too
As a consequence, we have removed two features:
1) Regular expressions
2) The possibility to list several scheme parts
in a single fragment identifier.
As a result of this, fragments for text/plain can no longer
consist of disconnected pieces.
While we do not want to exclude bringing the removed functionality
back in a future version of the spec if there is clear demand for it,
we feel that the reduced set of features is best suited for speedy
implementation and deployment, and also matches the fact that
text/plain by itself is very simple and straightforward.
The area directors in charge (first Ted Hardie, now Chris Newman)
have advised us that they don't expect another Last Call for this
feature reduction, but that we should announce this change to this
list. If you have concerns about this feature reduction, in
particular if you already have implemented some of the features
we removed, please notify this list.
With kind regards, Martin.
At 09:40 07/02/15, The IESG wrote:
The IESG has received a request from an individual submitter to consider
the following document:
- 'URI Fragment Identifiers for the text/plain Media Type '
<draft-wilde-text-fragment-06.txt> as a 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
ietf(_at_)ietf(_dot_)org mailing lists by 2007-03-14. Exceptionally,
comments may be sent to iesg(_at_)ietf(_dot_)org instead. In either case,
retain the beginning of the Subject line to allow automated sorting.
The file can be obtained via
IESG discussion can be tracked via
IETF-Announce mailing list
#-#-# Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
Ietf mailing list