> > 1) Is the problem described/solved by draft-ymbk-rpki-grandparenting-02 > actually a problem that the WG needs to address? (Answer: yes or no. > Additional information is welcomed, but I don't want people to repeat > the whole discussion.) [WEG] yes, but I tend to agree that it's not a technical problem. > > 2) If you answered "yes" to the question #1, please also answer the > following question: > > Is draft-ymbk-rpki-grandparenting-02 a reasonable starting point to > become a WG document? Please choose one of the following: > > > a) Ready for Adoption (whether or not you have some specific issues with > it. Also, this answer is unrelated to whether this should be a separate > draft or a part of an existing draft). > > b) Needs more work BEFORE Adoption > > c) Should not be adopted. In particular this mean that you don't believe > any amount of work on the proposed draft will address your issues. So > any solution to this problem should be a new draft written from scratch. > > d) Abstain/don't care [WEG] b. The text itself is ok, but we need to resolve #3 before adoption. > > > 3) If you answered "a" or "b" above, please also answer the following > question: > > Does this need to be in a standalone draft, or can it be incorporated > into another existing WG draft? When answering this question please only > base your answer on technical reasons, in particular please leave the > decision on who is going to edit the document (if it is standalone) to > WG chairs. [WEG] It needs to be incorporated into an existing draft. This text is covering a very specific gotcha with some helpful recommendations and no actual requirements. It currently reads like an orphaned section of another draft, probably the operational considerations (origin-ops) draft.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
