Melinda et al.,
As an ordinary participant who doesn't have anywhere near a photographic
memory and who's often swamped just like most everyone else, I find
it's hard to keep track of the discussions, especially when they stop
and start over several months. So I'd like to distinguish between 2
parts of the problem. First, I'd be most grateful if the person
addressing an issue wrote a description of the proposed final
resolution. If the I-D text is being changed, this would just need to
be the new text. For example, the email that Eran sent on 3/2 re:
Errata for RFC6962 made it really easy for me to quickly review it. And
this work, e.g., the new text, has to be written in any case -- so
hopefully this doesn't require more work than would otherwise be done.
Second, it would be slightly easier (one fewer steps) and therefore I'm
more likely to find the time, if the proposed resolution were
distributed to the list in email, rather than in a link. But since the
proposed resolution should be documented in the issue tracker, it would
be fine to do this via the ticket system. But in any case, please put
the proposed resolution (new text, etc.) at the top of the ticket for WG
review. That way when I receive the ticket, the thing to be reviewed is
right there.
Thank you,
Karen
-------- Forwarded Message --------
Subject: Re: [Trans] [trans] #59 (rfc6962-bis): Clarify STH versioning
Resent-Date: Mon, 2 Mar 2015 07:14:39 -0800 (PST)
Resent-From: [email protected]
Resent-To: [email protected]
Date: Mon, 02 Mar 2015 15:14:38 -0000
From: trans issue tracker <[email protected]>
To: [email protected], [email protected],
[email protected]
CC: [email protected]
#59: Clarify STH versioning
Comment (by [email protected]):
Ben sent this out for review in https://github.com/google/certificate-
transparency-rfcs/pull/34
--
-------------------------------------+-------------------------------------
Reporter: | Owner: draft-ietf-trans-
[email protected] | [email protected]
Type: defect | Status: new
Priority: major | Milestone:
Component: rfc6962-bis | Version:
Severity: - | Resolution:
Keywords: |
-------------------------------------+-------------------------------------
Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/59#comment:2>
trans <http://tools.ietf.org/trans/>
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
