Hi Alexey & WG, On 13/12/2012, at 5:56 AM, Alexey Melnikov <[email protected]> wrote:
> 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.) No (with a 'but' under q.2). The draft itself points out why the problem does not need to be addressed by the WG: "Managing RPKI data in such relationships is simple, but should be done carefully." RPKI reflects records of current INR holdings. If a CA recognises that INR holdings have changed, they may issue certificates to reflect that. If they do not recognise changed INR holdings, they may not issue certificates (RFC 6484 4.2.2.) Thus, if there is a business practice to recognise grandchildrens' rights to use resources, the RPKI can already match that practice. IOW, there IS a problem, but it's not one for a technical working group to resolve, it's one for bilateral business relationships to resolve. Hopefully that falls under 'additional information' rather than 'repeating the whole discussion'. :-) > 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 (c) While I answered 'No' for (1), recognising the "carefully" part above may allow for a draft describing where in their CPS a CA can provide assurance to both children and grandchildren that they will act responsibly around these relationships, such as grace periods on revocation. It would be possible to convert the current draft to do that, but the amount of change would make that effectively a new draft, I think. > 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. n/a Thanks, Byron
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
